Import & export
Security and privacy
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:
- SQL queries
They also pack a number of other features – you can explore them in the next section.
You can import an existing
.ipynb file as a Deepnote notebook, or export a notebook into an
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.
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.
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
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.
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.
In order to edit or execute
.ipynb files, move them to Notebooks. Editing or executing
.ipynb files will not work after November 2022.