Join usDocsSign in

Getting started

Deepnote documentation



Notebooks are a top level entity, building on top of and extending the .ipynb standard. They allow teams to explore, analyze and present data from start to finish.

We started Deepnote to help data teams solve the most difficult problems. To do that, we don’t just need better algorithms, bigger datasets and more computing power. We need powerful tools that inspire us to explore, reason and collaborate. These tools do not exist yet. We need to invent them first.

Notebooks are the heart of Deepnote. They are a rich computational medium which combines blocks of:

  • Code
  • Text
  • Charts
  • SQL queries
  • Inputs

They also pack a number of other features – you can explore them in the next section.

Imports and exports

You can import an existing .ipynb file as a Deepnote notebook, or export a notebook into an .ipynb file.

Importing an ipynb

You can drag-and-drop an ipynb from your computer to Files in a Deepnote project, or use the Upload file option in the plus-menu next to Files. Then right-click the file and select Move to notebooks.

Exporting notebooks

You can right-click a notebook, and select Export as .ipynb.

While we try our best to preserve compatibility with Jupyter, some of Deepnote's features (such as SQL blocks) will require you to write additional code before you can run the notebooks outside of Deepnote.

Working directories

By default, the working directory of the notebook is the same as the root of the filesystem in the right sidebar. Its absolute path is /work

When you import an .ipynb file from a nested folder, Deepnote will preserve its working directory. You can examine and change it in the right-click menu of the notebook.

Version history

To keep track of code changes to notebooks, use history. It is a native, user-friendly way to preview and restore older versions of your work.

Pushing notebooks to git

Deepnote implements a native solution for the primary uses of git: collaboration and version history, so we hope you won't need to do this very often.

If you need to push your notebooks to git despite that, select Download the project in the three-dot menu in the top-right corner, extract the archive, then:

  • Option 1: Organize the notebooks the way you need on your local machine, and push to a git repository from there.
  • Option 2: Upload the notebooks (.ipynb files) back to Deepnote's file system, and use the terminal to push to git.

Is this an important feature for you? Please tell us more on Portal.

Transition period (July-September 2022)

Starting July 18 2022 and continuing in the following 4-8 weeks, Deepnote will be rolling out a new version. Notebooks which were previously in Files will move to a separate Notebooks section.

This move unlocks a number of new features for versioning, collaboration, and text editing. It also builds the foundation for significant improvements in performance, leading to 90% decrease in project loading times.

Under the hood, Deepnote is changing its internal storage mechanism for notebooks.

Changes to old projects

When the feature gets enabled for your workspace, Deepnote will perform an upgrade of all projects created until then.

  • All .ipynb files will move to Notebooks. Their working directories will be preserved.
  • The notebooks will no longer be present as .ipynb files. To use them with other tools which require a file representation, such as git or nbconvert, export them as .ipynb (and optionally upload back to project files).

Editing and executing .ipynb files

During the transition period, Deepnote will support editing and execution of both its native notebooks, as well as .ipynb files on disk.

At the end of the transition period, the .ipynb files on disk will become read-only, and you will need to move them to notebooks to edit and execute them.

© 2022 Deepnote. All rights reserved.