Notion vs Obsidian: How Each App Stores and Exports Your Notes

While comparing Notion and Obsidian, it becomes clear that the most significant difference isn’t in how they work but how they store your notes. Notion stores your notes in a cloud-based workspace and will only create a physical copy of your notes if you specifically request it to do so. On the other hand, Obsidian automatically saves your notes as regular files in a folder on your computer. This means that when you leave Notion, you will need to request a download before moving to another note-taking app; however, leaving Obsidian simply involves copying a folder containing your notes.

The difference between these two applications comes down to what an export actually represents. An export should never be relied upon as a restore point, and the format that appears to be the easiest way to export your notes is likely the format that the destination app advises against using. Therefore, before trusting either exported copy, it would be prudent to review where the actual storage location of the notes exists before continuing with either option.

Where your notes actually live in Notion and Obsidian

Note storage in Obsidian is a folder that is accessible to you when you open up Obsidian. Every note is a plain text file written in Markdown format. Vaults are not unique storage containers created by Obsidian; they are actually referred to as “folder/subfolder” combinations in Obsidian’s own help. You can edit your note files with other text editors, rename your note files, and Obsidian automatically refreshes and keeps track of your vault’s folder and any changes that occur outside the application.

Since your note files are essentially your note files (i.e., you own the note files), there will never be a need to “export your note files.”

What sits next to those files is not the notes. Obsidian creates a hidden .obsidian folder in the vault root for that vault’s hotkeys, themes, and community plugins. Most operating systems hide folders that start with a period, so you may need to show hidden files before you see it. Copy the vault and you copy the notes. Copy only the .md files and you leave the app setup behind — which is fine if you want the writing, and a surprise if you expected the plugins to travel.

The folder structure for note storage in Obsidian has two limitations that are easily overlooked.

Internal Links – Links created within your vault are not accessible outside of your vault. For this reason, Obsidian recommends against storing multiple vaults within a vault, as internal links may not update properly when doing so. However, you may store your notes in nested folders. It is not advisable to create an additional vault within an existing vault.

The app also keeps some state outside the notes. Global settings live in a system folder (on Windows that is %APPDATA%Obsidian; on macOS it is under Application Support). Obsidian warns you not to create a vault there. A metadata cache inside the app speeds up search and the graph; if that cache drifts from the files on disk, you rebuild it from Settings → Files & Links. The notes were never in that cache. They were on disk the whole time.

Notion’s storage model is more likely what most people picture when considering how notes and other content are stored. All content created in Notion is stored on Notion’s servers and Notion provides backup options to restore your pages if needed. You will not open a note as a file on your computer using Notion unless you specifically choose to export it.

Thus, offline functionality relies on stored data rather than having a separate list of features to refer to. Files that contain notes saved to disk are accessible when Internet access is unavailable, whereas notes that are saved in a workspace managed by the Notion app will only show you cached versions of the notes, unless you specifically request a full copy of that folder.

You can confirm the Obsidian side in about a minute with no extra tools: open the vault folder and look. A .md file you can open in Notepad or TextEdit is the note. A .base file is a Bases view sitting on top of those notes. A .canvas file is canvas data. Images, audio, video, and PDFs can live in the same folder — Obsidian lists those among its accepted file formats. None of that requires a zip from the vendor.

Notion does not have a similar option as “open the folder” like many traditional file systems do (e.g. Mac OSX, Windows, etc.). In Notion’s case, your workspace serves this purpose; the only way to view or inspect your workspace is through an export of that workspace, not the actual content inside it.

What actually arrives when you export

An Obsidian “export” is an exact copy of your vault folder, while Notion creates a zip file when you request one. Therefore, they are completely different operations, and you do not end up with the same files in either case.

Notion offers three formats from a page’s ••• menu, or from Settings → General → Export all workspace content: PDF, HTML, and Markdown & CSV. Notion’s export help is specific about what Markdown & CSV actually contains. A non-database page becomes a Markdown file. A full-page database becomes a CSV, with Markdown files for each subpage. Callout blocks come out as HTML, because Notion states there is no Markdown equivalent.

The last line is an artifact, not a problem. Opening the zip with a text editor will reveal that it contains HTML inside the markdown version wherever you used a callout. Your board, calendar, and table databases will arrive as a single CSV file and also page files; this means that there is not one file that corresponds to each of the three views.

Additionally, Notion explicitly says that forms cannot be exported as such and instead, you are instructed to export the responses and questions from the table view. When you are exporting a database, the option you have is to either select the view you have currently open or the default view. Notion does not currently support exporting all views at one time.

HTML allows for retention of more content on each page than Notion allows. Notion allows for comments at the page and block level inside of the HTML export, including resolved comments. PDF is not meant as a working copy but instead as an image of what you would like to have printed or read. As of September 2026, according to Notion’s backup help, the PDF export option for workspace has been removed and is scheduled to be rolled out through 31 August 2026, however, individual pages can still be exported as PDFs.

The export feature does not work in real-time and cannot be accessed from every application type (e.g., mobile app). The export can only be downloaded from the desktop version or web version of Notion. The email Notion sends contains a link to the exported workspace, which will expire after 7 days. The email also mentions that it may take up to 30 hours before you receive your export based on the size of your workspace, which is simply what Notion provided as a time frame, not a guaranteed delivery time. If your email notifications are turned off, Notion sends the link to your Notion inbox. Pages that the exporter does not have access to (i.e., other users’ private pages) are excluded from the export.

Obsidian does not create a duplicate of your notes in a different format because the notes are already files. Simply copy your vault and you will have your notes. If you only copied the Markdown version of your notes, you would be missing the functionality of the plugins you are using, the graph view of your notes, and the Base view over those notes. The writing component of your notes is independent of Obsidian.

This table is a capability-and-outcome grid from the two vendors’ current help pages, not a feature scorecard:

The most surprising row for new users is the database row. In Notion, the database is how you visualize your content through filter, relation, and view. The Markdown and CSV versions of the export are basically a spreadsheet and pages. That is realistic because a CSV file can contain rows and meta data. However, a CSV does not have the functionality of displaying live views as you did this morning.

To make this less theoretical, run your own notes through this. Use a mix that reflects how you actually use them; twenty is about right for this, and at least one of those should be a database (if you work with databases). You aren’t trying to get the best combination; you are comparing files.

A twenty-minute side-by-side check

1. In Notion, open one ordinary page and one full-page database. Use ••• → Export. Save once as Markdown & CSV and once as HTML. Turn on Include subpages if nested pages matter to you.
2. Unzip both packages. Open a .md file in a text editor and the database .csv in a spreadsheet. Find a callout if you use them, and notice whether it is still Markdown.
3. Open your Obsidian vault in the system file manager. Confirm the notes are .md files you can open without launching Obsidian.
4. If you are testing a move into Obsidian, keep the HTML zip for the importer. Do not treat the Markdown zip as the migration package — the next section is why.

The way other note applications handle plain Markdown on their way out isn’t as relevant to comparing these two; what is important here is that you now have the actual files in front of you, and the files themselves are the only evidence that really matters when comparing these two applications.

An export is not a backup: what the format choice decides

A backup can be restored back to the same space. An export means you will be taking the data somewhere else. Notion uses both of these terms and they are not the same.

Notion does say that, while you can export workspace data, you cannot instantly recreate your workspace by uploading and re-importing that exported workspace data. The exported zip file is a copy of your pages and files in a different format; it does not give you a duplicate of your workspace. There has been some discussion on Reddit about this topic. In particular, a user who was periodically exporting his Markdown and CSV files wanted to know if he could re-import those files to be able to restore his emoji, formulas and templates. The commenter, who operates a backup service for Notion users, responded, “no, you’re not going to be able to re-import your data back into Notion.” He also indicated that they had already encountered this issue while trying to create a restore function.

What Notion does allow for as a safeguard may not be the same as a zip file but is still a useful feature. Deleted pages are kept in the Trash for 30 days, unless the Enterprise member has changed the Trash duration. Notion states that, if you reach out to them, they can restore any page that has been deleted or put into Trash for the past 30 days. Server backups are the company’s copies and are performed every minute; however, these types of backups are not under your control like a folder of files would be, and are also not similar to what Notion provides via the export feature.

So, the format menu is more of a goal list than a quality level.

If you want an ongoing portable copy of prose and tables — files you can open in other tools, without a plan to rebuild Notion — Markdown & CSV is the format aimed at that job. You get pages as .md and databases as CSV. You should expect callouts as HTML and databases as spreadsheets.

If you’re planning on moving from Notion to Obsidian, make sure not to start with the zip file you got from Notion. The Obsidian import instructions indicate that you should export your Notion workspace as HTML, instead of using the Markdown option, because “it leaves out important information.” While the instructions do provide some missing information, treat them as definite instructions from the target app; don’t try to interpret them yourself.

Obsidian provides two different options for importing, and one is not as good as the other.

The account route (Notion API) is the one Obsidian marks as recommended. It connects to the workspace, can preserve databases and formulas by converting them to Bases, and needs a Notion integration token plus a network connection. Databases arrive as a folder named after the database, with a .base file inside.

Only the primary view of each database is imported, because Notion’s API does not support linked data sources. Some formula functions do not convert (name() and email() on People; style() and unstyle() on Text). Obsidian also notes that this importer is new, that Notion’s rate limits can make large workspaces slow, and that some edge cases may still be missing.

The file route uses the .zip you exported. It does not preserve databases. It does not need a token or the internet. You point the official Importer plugin at the HTML zip and, if you can, import the whole workspace at once so internal links can be reconciled.

The fidelity dial of the import options means that none of the import options can carry every view of every database within Notion. The default Notion export will limit you to whatever your current/default view was, and the Obsidian API import will limit you to the primary view. If your work is a network of linked databases, you will be exporting the individual rows and pages rather than recreating the environment you created for those databases.

Stay in Notion if that machine is the product. The vault model is a poor home for a workspace whose value is live relations other people are still editing. The honest cost of leaving is not “some formatting.” It is that a database becomes a CSV or, at best, a folder with a .base file.

Please do not delete or archive your Notion source after you’ve completed an export. You cannot re-create your Notion workspace from the zip file you exported; the verification step must be completed before deleting the source.

What to check after the move — and what can stop it before it starts

Not all attempts will succeed. Some will succeed but will still appear to be wrong. Confirm that the blockers are resolved first and treat the vault as unfinished until files have passed all operational inspections.

In an Enterprise workspace (or teamspace), an owner can disable exports. Instructions for disabling exports are found in Notion’s export FAQ under Settings → Security (or the security screen for a teamspace). If you are a guest, you will need Full access to a page or database to export it. Can-edit is not a permission that allows for Export. Additionally, a work-managed account could potentially restrict any use of the export, and this is a policy defined at the workspace level—not a missing button that works only on your phone.

Workspace-level export is desktop or web only. The mobile app can export a single page from ••• → Export and will offer the share sheet plus an emailed link. It will not export the whole workspace. If you only have a phone, you’re not looking at a bug. You’re on the wrong surface.

An export’s download link will expire after seven days. If it has expired, you must request another copy of the export.

In Windows, nested exports may not open even when the zip file itself is acceptable because Notion places subpages in their own folders while Windows has a maximum path length of two hundred sixty characters by default. Notion suggests two ways to manage this difference: (1) while exporting, uncheck Create folders for subpages; or (2) when unzipping, use 7-Zip. If Windows’ Explorer reports that an archive is invalid, please try one of these two options before concluding that Notion was responsible for providing a corrupted file.

Large HTML exports can also arrive as a zip that contains more zips. Obsidian’s importer troubleshooting describes an error that looks like Import failed {id}.zip/{id}-Part-1.zip undefined. The fix it documents is to unzip the outer file and import the nested Export-{id}-Part-1.zip parts separately.

If the importer starts and then treats HTML as Markdown, look inside the package before you blame the plugin. On Reddit, a migration into Obsidian failed until the poster found the error was a “hidden md file in one notion page.” Removing that file was enough. Another commenter asked whether the exported pages actually ended in .html. Both checks take seconds and they are checks on your zip, not on a known defect in the apps.

When the pages do arrive, the vault root may look wrecked. A thread on the Obsidian Forum describes pages landing as Markdown while “the root is also full of the 500+ images” pulled off those pages. That can be mess without being damage. A community reply there draws the line at link syntax: if images use a basic wikilink such as ![[image.jpg]], you can move them into a subfolder in the file manager and the links still resolve. If they use a path or a Markdown link with a path, moving them will likely break the notes. Set Settings → Files & Links → Default location for new attachments before the next import. That setting doesn’t tidy files that already landed.

Don’t start moving attachments around until you’re able to access any one image link; don’t treat the Notion account as “waste” until after you’ve opened several internal links, seen several rendered images, and have access to search for your notes in the vault namespace. If the items you’ve just imported don’t show up in Obsidian, but they’re visible in your folder, please rebuild the metadata cache via Settings → Files & Links, and THEN re-import them.

Your move is complete when your files behave correctly; not when the progress bar indicates completion.

Match the two storage models to the notes you actually keep

If you are trying to decide between Notion and Obsidian, you should focus on how each product fits with your existing notes. Let your existing notes be the basis for your decision, rather than relying on a feature comparison for making this choice.

A short worksheet

Step through the differences between Notion and Obsidian and see how they each stack up against the actual method you use to take notes. Each bullet below maps to a point of difference that the two companies documented on their respective sites.

• [ ] I need to open notes in another editor without asking an app for a zip.
• [ ] A database with several views is how I think, not a side feature.
• [ ] One view of each database would be enough if I had to move.
• [ ] Other people edit the same pages with me, in real time, every week.
• [ ] I am on a work or school workspace where an owner could disable export.
• [ ] I need the same notes on several devices, and I am willing to pick a sync method.
• [ ] I can wait for an emailed download that may take hours and expires in 7 days.
• [ ] I would treat an export as my only safety copy.

If the first box is the one you cannot give up, you already want files on disk. Obsidian’s vault is that model. The app is listed as free without limits and requires no sign-up; optional Sync and Publish are add-ons, not the store. You can put the vault wherever the operating system allows, including Dropbox, iCloud, OneDrive, or Git. What you should not expect is a live Notion-style database with every view intact. File import will not preserve databases. The API import will convert them to Bases and only the primary view.

If the kind of product you are looking for has lots of views, guest access rules, and allows others to easily and quickly edit your files while being alongside you, Notion’s workspace is performing a task for you that a folder of markdown (Obsidian) cannot perform. The “cost” of that task or feature is in exporting files in the form of a zip file you can request, from either your desktop or web version, in a file format that you cannot then re-upload to rebuild your workspace. If you decide to leave Notion, you will lose everything you have built in their app and will be left with only a spreadsheet.

You may not necessarily have conflicting information if you have two distinct stacks of information, one being your thought notes (that can be stored like files) and the other being the shared database records associated with a specific project that need to stay in a workspace. Trying to process both stacks in a single export and expecting that the format menu automatically resolves the distinction is where the confusion arises.

Run the twenty-minute check from the earlier section on a sample of your notes before you move a whole workspace. Look at the CSV. Look at the .md files. Look at whether a callout is still a callout. Then decide whether that artifact is acceptable for the rest.

You cannot transport a license, list of plugins, or links belonging to an internal vault as a unit of transportable information. When you select a storage format, you are indicating how your notes will be recorded for future use. When you select a storage format for your notes, you are also indicating the manner in which your notes will remain in a repository.

What your notes look like after you leave each app

When you exit Notion, you have nothing but a zip file which contains Markdown pages, CSV files, HTML (for instances where Markdown is not used) and a download link that has a limited time period. With Obsidian, you have the folder that you were using prior to exporting your workspace. The only step that truly requires action on your part is to access these files through a text editor, spreadsheet, or vault, before considering your original workspace as non-essential. If you do not access these files before exporting your workspace from Obsidian, you will only discover how the export turned out after you can no longer access your workspace.

Frequently Asked Questions

Can I export my whole Notion workspace from the phone?

No. Notion documents full workspace export as desktop or web only. On mobile you can still export a single page from the ••• menu, then use the share sheet or the emailed link. For the whole workspace, use a computer.

The download link expired. What now?

Notion’s documentation indicates an expiration of 7 days from the original request for workspace export link; you will have to re-request the export from Notion Settings → General. Once a workspace export link expires, you cannot revive it. Depending on the size of your workspace, a re-request can take several hours to process.

I can edit a shared page. Why is Export missing?

To export data out of Notion, the guest user must have “Full Access” permission on the page or database; simply having “Can Edit” will not suffice. Enterprise account owners have the option in their Security Settings to “Disable Export of Content.” Please verify with your Enterprise account owner to confirm whether or not exporting has been disabled and seek other options, such as exporting from your own workspace.