Notion Free Plan vs Obsidian Local Vault for Research Notes

If you are collecting research notes across devices and want to know which free tier will cost you less time when you eventually outgrow it, this comparison focuses on three things: block limits, offline behaviour, and export friction. This piece is built from published specifications and reported failure patterns. It is not based on a multi-week single-unit test.

Where the free tier starts to pinch

Notion’s free plan is not limited by note count but by block count and file upload size. A block is roughly a paragraph, heading, list item, image, or database row. The current free tier allows up to 1,000 blocks per workspace before you must either delete content or pay. For a researcher, that can arrive faster than expected: a literature review with 30 sources, each with a summary, citation, and a few quotes, will burn several hundred blocks before you add tables or linked databases.

Obsidian has no block cap. It is a local-first application that reads and writes markdown files in a folder on your device. You can store as many files as your disk allows. The free tier does not include Obsidian Sync, but you are not forced to stop writing when you hit an arbitrary number. The trade-off is that you handle your own backups and syncing, often through a third-party service or a folder synced by something like a cloud drive.

The free-tier difference is not about generosity. It is about the business model: Notion charges for hosted infrastructure, so the limit is on hosted objects. Obsidian charges for convenience, so the limit is on sync and publish features, not local files.

If you have already been through a messy migration, the friction of leaving a notes app is covered in more detail in /reviews/leaving-a-notes-app-export/.

Offline access under a deadline

A researcher without reliable Wi-Fi, whether in an archive, on a train, or at a conference venue with overloaded networks, needs notes that open instantly. Obsidian stores everything locally by default. Every note is a markdown file on your machine. You can search, edit, and link notes with no connection. This is not a “recently cached” subset; it is the whole vault.

Notion’s desktop and mobile apps cache previously opened pages, but the cache is not guaranteed to be complete. If you have not opened a page recently, or if the app decides to refresh from the server, you may see a loading state instead of your notes. This matters when you are trying to find one quote from a source you last opened three months ago. Notion’s offline support has improved, but it remains a hosted service with local caching, not a local-first tool.

For anyone keeping large reference libraries, the difference compounds. A local vault can be searched with system tools, scripted, and backed up without an internet connection. A hosted workspace depends on the provider’s export API, rate limits, and app stability.

Export friction when you outgrow the free tier

The more important comparison is not what you can do inside the app, but what happens when you leave. Notion allows export to HTML, markdown and CSV, and PDF. Markdown export exists, but the conversion is not always clean. Database properties, linked views, and inline formatting can come through as extra files, duplicated content, or broken structure. You will likely spend time cleaning the result before another tool can use it.

Obsidian is already a folder of markdown files. Leaving Obsidian means pointing another editor at the same folder. There is no export step because the files were never trapped in a proprietary format. Attachments and images sit in the vault as normal files. Frontmatter, tags, and wiki-links are plain text. That does not make Obsidian perfect for everyone, but it lowers the cost of switching tools later.

Factor	Notion free plan	Obsidian local vault
Free-tier ceiling	1,000 blocks per workspace	No block or file cap
Offline behaviour	Cached, variable coverage	Full local access
Export format	HTML, markdown, CSV, PDF	Native markdown, no export needed
Sync included	Yes, hosted	No, third-party or paid Obsidian Sync
Learning curve	Lower for databases	Higher for linking and plugins

For broader context on cloud storage limits, /reviews/cloud-backup-free-tiers/ covers how hosted free plans behave across categories.

Who should choose which

Choose Obsidian if your research notes are long-form, text-heavy, and need to survive without internet access. The lack of a block cap means you can keep every draft, every marginal note, and every source summary without deciding what to delete. The cost is setup: you will configure sync, decide on a backup routine, and learn markdown syntax. If you are not willing to do that, the local vault becomes a liability rather than a strength.

Choose Notion if you need structured databases, shared workspaces, and a polished interface without maintaining your own files. The free tier works for a bounded project: a thesis chapter, a course reading list, or a short-term fieldwork log. But you should plan for the block cap from the start, because moving a large research database out of Notion is more work than staying under a limit.

Neither tool is wrong. The decision hinges on whether you value hosted convenience or long-term portability more. If you have been burned by a free tier that looked generous until the cancellation flow arrived, the mechanics are discussed in /reviews/free-trial-cancellation-mechanics/.

Limits of the evidence

The block limit, file format behaviour, and offline design described here come from published product documentation and widely reported user experiences. They can change without notice, especially Notion’s free-tier caps, which have shifted over time. Export quality varies by workspace complexity, and no public dataset measures conversion accuracy across database types. This comparison does not cover mobile app performance, plugin ecosystems, or long-term sync reliability, all of which could matter more than the three factors above for a specific research workflow.