DEV Community: Guido Diforti

Notion vs Obsidian for a PhD Thesis: The Real Test

Guido Diforti — Fri, 28 Aug 2026 16:10:25 +0000

Notion vs Obsidian for a PhD Thesis: The Real Test

Most comparisons of these two apps answer a question you have already outgrown. You are not choosing a note-taking app. You are choosing the thing that must survive four to seven years, dozens of supervisor feedback cycles, an ethics approval, and a submission process run by a graduate school that has never heard of either app.

Here is the verdict up front.

Obsidian should own your manuscript. One file per section, plain Markdown, version-controlled, compiled to Word or LaTeX with one repeatable command. A thesis is a long document that gets restructured for years, and only Obsidian treats it that way.

Notion should own your project, if you want a project layer at all. Supervision log, ethics milestones, fieldwork tracker, participant database, co-author coordination. That is genuine database work and Obsidian is worse at it.

Neither one is where you submit from. That fact reframes the whole comparison, and the rest of this article follows from it.

If you want the general research-notes decision rather than the thesis-specific one, it is a different shape and I covered it in Notion vs Obsidian for research notes. This article assumes the thesis is the deliverable.

The three jobs a thesis tool has to do

A thesis is not one artifact. It is three, and they have almost nothing in common.

The corpus. Everything you read, annotated, and will need to defend in a viva. It grows for years and is never finished.

The manuscript. Six to nine chapters that get split, merged, renumbered and moved, under a structure imposed by someone else and a hard deadline.

The project. Supervision meetings, upgrade review, ethics submission, fieldwork schedule, conference deadlines, teaching load.

The mistake almost everyone makes is picking one tool for all three. The corpus needs retrieval and linking, the manuscript needs restructuring and diffing, the project needs structured records. Judge each app per layer and the answer stops being close.

The supervisor loop is the real constraint

Your supervisor will not install Obsidian. They may also decline to join your Notion workspace, and if they do join they will probably still ask for "the chapter" as a file.

That single fact decides more than any feature list. Supervisor feedback in most disciplines arrives as tracked changes in Word or annotations on a PDF, which means you are exporting either way. What matters is not collaboration features but export cost per cycle.

Notion can do the in-place version. Share a page, get block-anchored comments, resolve them in a thread — with the caveat that guest access is limited on the free plan, and a supervisor who is not already a Notion user is being asked to learn your tool for your convenience.

Obsidian offers nothing here. No comment layer, no private share link, and Publish produces a public website rather than a review copy.

But run the loop forward. Your supervisor returns fifty tracked changes and eight marginal comments, and you have to get those decisions back into your source of truth. From Obsidian that is an export step you scripted once — Pandoc, a reference template, one command — and a merge you do by reading the marked-up file beside your Markdown. From Notion, the export needs cleanup every cycle, and the return leg is worse: there is no path from a tracked-changes Word file back into blocks that avoids retyping.

Do that thirty or forty times across a doctorate and the friction is not a detail — it is the difference between a chapter revision taking an afternoon and taking two days.

Chapter management over four years

Notes accumulate; manuscripts get restructured, and late. The section that moves from Chapter 3 to Chapter 5 in your third year is the normal case, and so is discovering during writing-up that one chapter is really two.

In Obsidian this is cheap because the manuscript is files. One note per section, an index note per chapter pulling sections in with embeds like ![[03-02-sampling-strategy]], and reordering becomes editing a list. Renaming a note updates every link to it. The Longform plugin exists for exactly this: an ordered manuscript that compiles to a single document.

The larger advantage is version control. A vault is a folder of text files, so it can live in a git repository — a diff of what changed in Chapter 4 since your supervisor last saw it, recovery of a paragraph you cut in year two, and a history that survives the laptop you will replace. For a document you are answerable for across years, that is worth more than it sounds.

Notion reorders beautifully: drag pages in the sidebar, use synced blocks to keep a definition consistent in two places. What it does not do is comparison. Page history exists, but retention depends on your plan tier and it works page by page rather than as a diff across the manuscript. "Show me every change to the thesis since March" is not a question Notion answers.

What your university accepts at submission

Nobody deposits a Notion workspace or a Markdown vault. Graduate schools want a formatted PDF, often in an archival flavour, produced from a Word or LaTeX template they supply, with mandated title page, declaration, margins and bibliography style.

Markdown plus Pandoc is a real route to that. Your chapters compile into LaTeX or Word against your department's template, with cross-references, figure numbering, and a bibliography in whatever CSL style is mandated. Change the style and you recompile rather than re-edit. It is the same chain much of your field already uses, so when it breaks someone can help you.

Notion has no equivalent. Toggles, callouts, database views and synced blocks have no counterpart in a thesis template, and export drops the structural relationships entirely. People who draft a thesis in Notion rebuild it manually in Word or Overleaf in the final months — the worst possible time to be doing formatting work.

A third answer is right for a lot of people: draft in whichever app you like and write the manuscript in Word or Overleaf from day one. Neither app is a typesetting system; Obsidian merely sits one clean step away from one.

Whichever route you take, test the full compile in your first year on a throwaway chapter. Discovering your template does not build is survivable in month eight and close to catastrophic in month forty-six.

Where Notion is genuinely the better thesis tool

The project layer is not a consolation prize. It is the part of a doctorate that most often goes wrong quietly.

A supervision log — date, attendees, decisions, agreed actions, deadline — is worth building in week one. At your upgrade review you can produce a complete record of what was agreed and when. If your supervisor changes mid-degree, which happens more than prospective students expect, that log is the only continuity anyone has.

The same applies to an ethics tracker with approval dates and expiry, a participant database with per-item status and a rollup counting what is complete, a calendar of abstract deadlines against your writing plan. Each is a typed, filterable, multi-view structure — what Notion databases are for, and what a folder of Markdown files is not.

Two further cases. A thesis by publication means coordinating live documents with co-authors, where multiplayer editing beats mailing files around. And if you answer a blank vault by building the perfect system for a term, Notion's smaller decision space is a real advantage — losing a term to tool configuration is a genuine doctoral failure mode, not a joke.

If that project layer describes your situation, the free plan is enough to build a supervision log and an ethics tracker and find out within a month whether you will actually maintain them: {{AFFILIATE_LINK_SOFTWARE}}

What Notion will not solve is citations, because it has no native citation engine and a thesis is a citation machine. The workarounds and their honest limits are covered in the Notion and Zotero integration guide.

Year three to the viva: retrieval, durability and ethics

The long middle of a doctorate tests what a two-week trial cannot.

Retrieval under pressure. In your viva you will be asked why you excluded a paper you skimmed in year one. Obsidian searches the full text of everything locally, instantly, offline, and its backlinks pane shows where you referred to that source and why. Notion's search runs against the cloud and slows as a multi-year workspace grows.

Durability. Over a doctorate you will change machines, possibly institutions, possibly take a leave of absence, and quite possibly hit a period where a subscription is not affordable on a stipend. A folder of Markdown files is unaffected by all of that. A Notion workspace whose paid plan lapses reverts to free-plan limits — confirm the current terms rather than trusting any article, including this one, but plan for access terms changing while your thesis cannot.

Ethics and data governance. This is the one people discover too late. If you hold interview transcripts, clinical data or anything identifiable, your ethics approval likely specifies where that data may live, and many approvals name institutional storage or restrict transfer to third-party clouds. A local vault inside an institutionally managed folder is usually straightforward to approve; a commercial SaaS workspace may require an amendment, or may not be permitted at all. Check your conditions before you put a single transcript anywhere.

Named limitations of both, for a thesis specifically

Obsidian's real failures. There is no supervisor-facing collaboration whatsoever, so if your supervisor insists on commenting in place you will export forever with no return path. The setup cost is a genuine trap for a first-year with unstructured time. Community plugins break after app updates, and you will discover this the week you need to compile — pin your plugin set once you start writing. The Pandoc pipeline has a real learning cost, and debugging a template days before deposit is a well-documented way to lose sleep. Syncing a vault through a generic file-sync service produces conflict files, and finding one in your methods chapter a fortnight before submission is as alarming as it sounds. Mobile capture during fieldwork is less pleasant than Notion's.

Notion's real failures. No native citations, in a document defined by citations. Export loses the relational structure the project layer was built on, so that work does not leave with you. Offline support is not dependable, and archives, field sites and trains are where doctoral work happens. Large workspaces slow measurably as years accumulate. History retention is bounded by plan tier, a poor fit for a document you must roll back across years. Ethics constraints may rule it out for participant data outright. And it bills per seat for a degree funded, if at all, at stipend level.

Conclusion

This comparison feels hard because people ask which app to use for a thesis, when the useful question is which layer each app owns.

Use this rule: the manuscript belongs wherever restructuring is cheap and history is recoverable; the project belongs wherever structured records are cheap. That is Obsidian and Notion respectively, and running both is less overhead than it appears because they never touch the same content. If you want one tool only, pick Obsidian and keep the project layer in a spreadsheet — the manuscript is what you cannot afford to migrate in year four.

Then do the thing almost nobody does at the start: build a fake chapter with three citations and a figure, and compile it all the way to a PDF against your graduate school's template. If that pipeline runs in your first term, the next four years get materially easier.

The project layer is the faster experiment. Build a supervision log with one row per meeting and an actions rollup, keep it a month, then check whether it is still current — that answers the question better than any comparison can: {{AFFILIATE_LINK_TOOL}}

Before you go: our AI prompt pack

We should be straight about this one, because the fit is partial.

This article is for people writing a doctorate, and we sell a business product: The Ultimate AI Prompt Pack for Entrepreneurs — 100 tested prompts for ChatGPT and Claude covering positioning, offers, cold outreach, pricing and customer research. $17, one-time, no subscription.

It is genuinely useful if you are one of the doctoral researchers who is also building something on the side, planning a spin-out, or looking past submission at work that is not a postdoc. It contains nothing on thesis writing, citations or supervision, and we are not going to pretend otherwise. If you are heads-down on chapter four, close this tab and go build that fake chapter and compile it — that advice is free and worth more to you today.

Notion Zotero Integration: An Honest Setup Guide

Guido Diforti — Fri, 28 Aug 2026 16:05:10 +0000

Notion Zotero Integration: An Honest Setup Guide

You picked Notion. Maybe you read a comparison — possibly our own — decided your research is collaborative and structured enough to justify a database over a folder of Markdown, and committed. Now you have four hundred items in Zotero and a Notion workspace, and no obvious way to make them talk to each other.

Here is the verdict up front.

Use Notero. It is a community Zotero plugin that pushes items from a Zotero collection into a Notion database, and for the overwhelming majority of researchers it is the entire answer. Setup is under thirty minutes, it costs nothing, and it survives years of new sources.

Do not expect it to solve citations. This is the part most guides skip, so read it twice: Notion has no citation engine. No CSL styles, no Insert Citation button, no bibliography generator, no Word-plugin equivalent. Notero moves metadata into Notion. It does not make Notion capable of producing a formatted reference list, and nothing else will either. If your project ends in a bibliography, your final draft is leaving Notion regardless of what you set up today.

Everything below assumes you accept that trade. If you do not, that is a legitimate reason to revisit the tool choice, and the thesis-specific comparison in this cluster is the better read.

The honest baseline: what "integration" can and cannot mean here

Zotero and Notion were built for different jobs, and the gap between them is not a missing feature — it is a structural difference.

Zotero is a reference manager. Its data model is bibliographic: item types, creators, container titles, DOIs, page ranges. It owns a citation processor that renders that data in thousands of styles, and connectors that drive Word, LibreOffice and Google Docs directly.

Notion is a block-and-database editor. Its data model is generic: pages with typed properties. It has no concept of an item type, no CSL processor, and no word-processor connector.

So an integration between them can only ever do one of two things. It can copy Zotero's structured metadata into Notion properties, so your reading notes live next to the source details. Or it can copy your Notion writing back out into something that does understand citations. Both are useful. Neither makes Notion a reference manager, and any guide that implies otherwise is selling you a setup you will abandon in month four.

With that established, there are three real routes.

Route 1: Notero, the plugin that does the boring part

Notero is an open-source Zotero plugin. You install it into Zotero, connect it to Notion once, and designate a Zotero collection as the sync source. From then on, items you add to that collection appear as pages in a Notion database, with their metadata mapped onto database properties.

The setup has four steps, and the order matters:

Create a Notion internal integration in your workspace settings. Notion issues it a secret token. No external service or account is involved.
Build the destination database in Notion, with properties matching the Zotero fields you care about — title, authors, year, item type, DOI, abstract, tags.
Share that database with the integration. This is the step everyone misses. An integration cannot see a database until you explicitly connect it from the database's own menu, and Notero will fail with a permissions error until you do.
Install Notero in Zotero, paste the token, point it at the database, and map fields to properties in the plugin's preferences.

What Notero handles well: it maps a useful set of Zotero fields, pushes item notes into the Notion page body, updates existing pages when you edit the Zotero item rather than creating duplicates, and keeps working in the background as you add sources through the Zotero browser connector.

What it does not do: it is one-way. Zotero is the source of truth, Notion is the mirror. Edit a title in Notion and your next sync will overwrite it. In practice this is the right design — you want one authoritative copy of bibliographic data — but it means your Notion database is a reading dashboard, not a place to correct metadata. Fix things in Zotero.

Route 2: the Notion API, when you need what Notero will not do

Notero is opinionated. If your requirement falls outside its mapping — you want PDF annotations broken out into individual Notion pages, or a Claims database populated from your highlights, or a nightly reconciliation against a shared team library — you write against the Notion API yourself.

The shape of the work is straightforward. Create the same kind of internal integration, share the same database with it, then have a script read from Zotero — the local SQLite database, the Zotero web API, or an exported CSL JSON file — and create or update Notion pages through the API's page and database endpoints.

Three constraints will shape whatever you build, and it is better to know them now than at item 300:

The API is rate-limited to a small number of requests per second. A library of a few hundred items is fine; a first-time bulk import needs throttling and retry handling or it will fail partway through and leave you with a half-populated database.
There are caps on how much content one request can carry — limits on blocks appended per call and on the length of a single rich-text chunk. Long PDF annotations and full abstracts need chunking.
Updates require you to find the existing page first. There is no upsert. Store the Zotero item key in a Notion property and query on it, or you will create duplicates on every run.

It is a good route for a team with an unusual workflow, and a bad one for a solo researcher who wants to start reading this week. The maintenance cost is real: a personal script is a thing you now own forever.

Route 3: the export route everyone falls back to

The unglamorous option: export from Zotero as CSV and import it into a Notion database.

This is worth naming honestly, because a lot of researchers end up here. It is a snapshot, not a sync — no live updates, no deduplication, and re-importing later creates a second set of rows you merge by hand. But if your literature set is closed (a systematic review with a frozen search, a course reading list, a book with a fixed corpus), a snapshot is all you needed, and you are done in ten minutes with nothing to maintain.

The version that ages badly is doing it repeatedly: if you export a third time, stop and install Notero.

Designing the database that receives your library

The integration is the easy half. The schema is where people actually go wrong, and no plugin saves you from a bad one.

Two rules cover most of it.

Keep bibliographic fields dumb and your own thinking separate. Title, authors, year, DOI, item type, publication — these come from Zotero, get overwritten on sync, and should never be edited in Notion. Add a clearly separate group of properties that Notero does not write to: your screening decision, your relevance rating, a read status, your one-line takeaway. Those are yours, and they survive syncs precisely because nothing upstream owns them.

Use a second database for claims, not more columns. The pattern that makes Notion worth the trouble is relational. One database of Sources, fed by Zotero. A second database of Claims or Findings, written entirely by you, with a relation to the sources supporting each one. A rollup on the source counts how many claims cite it. Now you can filter for claims resting on a single source and see the weak points in your own argument — an audit that is genuinely hard to run in a plain-text vault, and the strongest reason a researcher picks Notion in the first place.

If you build only the Sources database, you have made an expensive bookmarks list. The relation is the point.

Named limitations: where each side actually breaks

Notero's real problems. One-way sync means Notion edits to synced fields are silently lost — new users lose work to this before they understand the model. It syncs items from designated collections, so anything you file elsewhere in Zotero never appears, and the failure is quiet. It is a community plugin maintained by volunteers: Zotero's move to its version 7 plugin architecture forced authors to update, and any plugin can lag behind a future Zotero or Notion change. Attachment handling is limited — your PDFs largely stay in Zotero, which is arguably correct but means Notion is not a complete archive. And a first bulk sync of a large library is slow enough that you should start it and go do something else.

Notion's real problems in this workflow. No citation engine, which is the whole story and worth repeating. Databases with many relations and rollups get visibly sluggish as they grow, and a literature database is one that only grows. Export fidelity is poor — the relations and rollups that justified the setup do not survive Markdown or CSV export in usable form, so the structure you are building is only rentable, not ownable. Offline access is unreliable, which matters in archives and on planes. Free-tier file upload caps bite quickly if you try to store PDFs. And the workspace lives in someone else's cloud, which some ethics boards will not accept for interview or clinical material.

The gap neither side fixes. Zotero's Word, LibreOffice and Google Docs connectors do not work in Notion. There is no supported path from a Notion draft to a formatted bibliography. Your options are to draft in Notion and rewrite in a word processor at the end, or to export the draft to Markdown and run it through Pandoc with a BibTeX file from Zotero — which works, and is what Better BibTeX's stable citekeys exist to support, but requires you to have typed [@citekey] markers by hand as you drafted. Decide which of those two you are doing now, not in your final month.

Which route fits which researcher

Solo researcher, growing library, wants to start reading this week. Notero. Nothing else is close on effort-to-value.

Team with a shared Zotero group library and a screening workflow. Notero for the sync, plus real thought spent on the Sources-to-Claims schema. Add the API only if a specific need survives a month of actual use.

Anyone whose output has a formatted reference list. Notero for reading and organizing, plus a decided-in-advance exit route for writing. Draft in Notion only if you prefer it, knowing the last mile is Word or Pandoc.

Anyone with a closed, finite source list. CSV export. Do not install anything.

If you are in the first two groups and still need to set up the Notion side properly, the free plan is enough to build both databases and test the relation before you pay for anything: {{AFFILIATE_LINK_SOFTWARE}}

Conclusion

A Notion Zotero integration is a solved problem in exactly one direction and an unsolved problem in the other. Metadata flows in cleanly — Notero handles it, for free, in half an hour. Citations never flow out, because Notion has nothing to flow them out with, and no plugin can add a citation processor to an app that was not built around one.

That is not a reason to avoid Notion. It is a reason to be deliberate: let Zotero own your bibliography, let Notion own your thinking about it, and pick your final-draft tool on day one instead of discovering the problem in week fifty.

Set up the Sources database with the four Zotero-owned properties and a relation to a Claims database, sync twenty real papers into it, and write three claims against them. One evening tells you whether this workflow is yours: {{AFFILIATE_LINK_TOOL}}

Before you go: our AI prompt pack

One disclosure in the other direction. Everything above points at tools we do not own; this section points at the one thing we do.

If the reason you are wiring Zotero into Notion is that your research feeds something commercial — a consultancy, a newsletter, a spin-out, a product you are validating — we make The Ultimate AI Prompt Pack for Entrepreneurs: 100 tested prompts for ChatGPT and Claude across positioning, offers, outreach, pricing and customer research. $17, one-time.

The honest limitation: it contains nothing about citations, literature reviews or academic writing, because that is not what it is for. If your Notion workspace exists purely to finish a degree, the Notero setup above is where your time should go instead.

Notion vs Obsidian for Research Notes: Which Wins?

Guido Diforti — Fri, 28 Aug 2026 16:05:01 +0000

Notion vs Obsidian for Research Notes: Which Wins?

If you are a graduate student, an independent researcher, or an analyst who has to turn a pile of papers, interviews and web clippings into something citable, this comparison is for you. You have probably already tried both apps for a weekend, liked something about each, and stalled.

Here is the verdict up front, so you do not have to read 1,800 words to get it.

Choose Obsidian if your research output is a document you write yourself — a thesis, a literature review, a paper — and you rely on a reference manager like Zotero. Its plain-text files and citation plugins fit that workflow better than anything Notion offers.

Choose Notion if your research output is a shared, structured dataset — a competitive landscape, a screening table, an interview log your team also reads. Its databases and real-time collaboration are genuinely hard to replicate in Obsidian.

Most people who pick wrong pick Notion for a solo thesis, then spend a year fighting export, or pick Obsidian for a five-person research team, then spend a year fighting sync conflicts. The rest of this article explains exactly where each one breaks.

How each tool stores your notes, and why that decides everything

This is not a boring technical detail. It is the single fact that determines everything downstream: portability, offline access, collaboration, and what happens if you stop paying.

Obsidian stores notes as ordinary Markdown files in a folder on your disk, which it calls a vault. You can open that folder in Finder, in VS Code, in a terminal, or in any other Markdown editor. Metadata lives in YAML frontmatter at the top of each file. If Obsidian disappeared tomorrow, your notes would still be there, readable in a text editor.

Notion stores everything as blocks in Notion's cloud. Every paragraph, toggle and table row is an object in their database, addressed by ID. You get an internet-native, collaborative document with relational structure that Markdown simply cannot express. The tradeoff is that the structure only exists inside Notion. Notion's Markdown and CSV export gives you readable text, but relation properties, rollups and formula columns do not survive the trip in usable form.

For a three-month project this rarely matters. For a five-year dissertation, it is the whole ballgame.

Where Notion actually wins: databases, relations and shared reviews

Notion's databases are the reason serious researchers keep coming back to it. A database is a table where each row is a full page, and each column is a typed property: select, multi-select, date, person, number, relation, rollup, formula.

That unlocks a specific research pattern that is very hard elsewhere. Build one database of Sources and another of Claims. Relate each claim to the sources that support it. Add a rollup on the source that counts how many claims cite it. Now filter for claims supported by exactly one source, and you have an instant weak-evidence audit of your own argument.

The same data renders as a table, board, calendar, timeline, gallery or list without duplicating anything — each is just a saved view with its own filters and sorts. A systematic review screening log is a natural fit: board view by screening stage while you work, table view with filters when you report.

Notion's other real advantages for research teams:

Real-time multiplayer editing, with comments anchored to specific blocks and @-mentions that notify people. Two co-authors can work on the same page at the same time.
Notion Web Clipper, a browser extension that saves an article directly into a chosen database, so a source lands with its properties already set instead of as a loose bookmark.
Notion AI, a paid add-on that answers questions across your workspace and can autofill database properties — for example, generating a one-line summary column across fifty sources at once.
The Notion API, which lets you push data in from outside. Notero, a community Zotero plugin, uses it to sync Zotero items into a Notion database.

If more than two people need to read and edit the same evolving structure, Notion is the correct answer and it is not close.

Where Obsidian actually wins: linking, offline work and plain text

Obsidian's core idea is bidirectional linking. You type [[Author 2019]] anywhere, and that note now shows the current note in its backlinks pane. You did not have to go set anything up on the other end. Over months, this produces a map of which ideas actually connect — visible in the graph view, but far more useful in the unglamorous backlinks pane at the bottom of each note.

What that means in practice: you open a note on "measurement invariance" and immediately see the eleven papers, three meeting notes and one half-formed argument that referenced it. Notion can do this with relation properties, but only if you set the relation up in advance and remember to fill it in. Obsidian gets it for free from ordinary writing.

The plugin ecosystem is the other half. A few that matter specifically for research:

Zotero Integration pulls citation metadata, PDF annotations and highlights out of Zotero into a formatted literature note, using a template you control.
Dataview queries your notes like a database — list every note tagged #to-read with a status of open, sorted by date — without moving anything out of Markdown.
Templater generates structured note skeletons so every literature note has the same sections.
Excalidraw and the built-in Canvas give you an infinite whiteboard for mapping an argument spatially.

Obsidian also runs entirely offline. On a plane, in a basement archive, on conference wifi, the app behaves identically. Newer core features such as Bases add table-style views over your notes' frontmatter, closing part of the structured-data gap that used to be Notion's exclusive territory.

Citation management: usually the deciding factor

If you write anything that needs a bibliography, this section decides the comparison for you.

Neither app has a native citation engine. The difference is what happens next.

Obsidian sits in a plain-text writing pipeline that academia already uses. Zotero exports a BibTeX file, the Zotero Integration plugin builds literature notes from it, you write in Markdown with Pandoc-style [@citekey] citations, and Pandoc renders the final document with a formatted bibliography in whatever style your journal demands. Every piece of that chain is mature and widely documented.

Notion has no equivalent. Your realistic options are to push Zotero items into a Notion database with Notero and keep citations as text, or to draft in Notion and rewrite in Word or LaTeX at the end. The second is what most people actually do, and it means the last month of a project is spent retyping. If you have already committed to Notion, our Notion Zotero integration guide walks through the Notero setup and is explicit about what it cannot fix.

If your work ends in a formatted bibliography, Obsidian wins this section outright. If it ends in a shared internal document with links instead of citations, this section does not apply to you.

Pricing: what you actually pay for

Both tools have a free tier that is genuinely usable, and both charge for something specific rather than for the editor itself.

Obsidian is free for personal use, and since 2024 free for commercial use as well. The paid products are add-ons: Obsidian Sync, an end-to-end encrypted service that keeps vaults consistent across devices, and Obsidian Publish, which hosts a vault as a public website. You can skip both — plenty of people sync a vault with iCloud, Dropbox or git, accepting the occasional conflict file. Mobile apps are free.

Notion is priced per member per month, with a meaningful discount for annual billing. The free plan gives an individual unlimited pages and blocks with a small per-file upload cap, a short page history window, and a limited number of guests. Paid tiers unlock unlimited file uploads, longer page history, then SSO and private teamspaces at the business level, and audit logs at enterprise. Notion AI is billed separately from the base plan. Notion has repackaged and renamed these tiers more than once, so confirm the current structure before you budget rather than trusting any article, including this one.

The honest summary: a solo researcher can run Obsidian at zero cost indefinitely. A solo researcher can also run Notion free, but will likely hit the file upload cap the first time they store PDFs. A team pays for Notion, per seat, forever.

If your situation is the collaborative one and you have decided Notion is the fit, you can start on the free plan and upgrade later: {{AFFILIATE_LINK_SOFTWARE}}

Honest limitations of both

No tool review is worth reading without this section.

Notion's real problems. Offline support has improved but is still not something to depend on; if your connection drops mid-session, expect friction. Large databases with many relations and rollups get visibly slow, and this degrades over years as the workspace grows. Export fidelity is the big one — Markdown and CSV export loses the relational structure that made Notion worth using. There is no native citation support. And your notes live in someone else's cloud, which some institutions and ethics boards will not permit for interview data.

Obsidian's real problems. There is no real-time co-editing; collaboration means a shared folder or a git repository, and shared folders produce sync conflicts the moment two people edit the same note. Setup cost is high — a research vault that works well is one you spent a weekend configuring with four or five plugins. Community plugin quality varies, and plugins do break after app updates. Mobile is capable but noticeably less pleasant than Notion's mobile app for quick capture. And the freedom to structure things any way you like is a real trap for people who prefer a system handed to them.

Which one to choose: three profiles

The dissertation writer, working alone, citing hundreds of sources. Obsidian. The Zotero and Pandoc pipeline will save you weeks at the end, and your notes stay readable for the decade after you graduate. That decision has enough thesis-specific detail — supervisor feedback loops, chapter restructuring, submission templates — that I gave it its own breakdown in Notion vs Obsidian for a PhD thesis.

The three-person lab running a systematic review. Notion. Screening logs are database work, and multiplayer editing plus comment threads is worth the per-seat cost.

The analyst or writer doing fast, shallow, wide research. Notion, mostly for the Web Clipper and the mobile capture experience. You are collecting and organizing more than you are composing.

A reasonable hedge for anyone genuinely unsure: run Obsidian as the permanent, private, plain-text archive, and use Notion only for the specific artifacts other people need to read. Notion's Web Clipper feeds the shared layer; your vault holds everything else. It is more overhead than one tool, but it puts the lock-in risk only on the material you were going to rewrite anyway.

Conclusion

There is no universal winner, but there is a reliable rule: pick based on your output, not your input. If the thing you eventually hand in has a bibliography, go with Obsidian. If the thing you hand in is a living structure that other people read and edit, go with Notion.

Both have free tiers that are good enough to test properly, so do not decide from screenshots. Spend one real week putting actual sources into each — not a toy example, ten papers you genuinely need to read — and the answer will be obvious well before the week is out.

Ready to test the collaborative side properly? Start a Notion workspace on the free plan and build one Sources database with a relation to a Claims database — that single exercise tells you more than any comparison article: {{AFFILIATE_LINK_TOOL}}

Before you go: our AI prompt pack

A note on what we sell, since this article recommends tools we do not.

Plenty of readers who land on a tool comparison are not only researchers — they consult on the side, run a small practice, or are turning a body of research into something that pays. If that is you, we make The Ultimate AI Prompt Pack for Entrepreneurs: 100 written-and-tested prompts for ChatGPT and Claude, covering positioning, offers, cold outreach, pricing and customer research. $17, one-time, no subscription.

It is a business toolkit, not a research one. It will not help you write a literature review, and we would rather say so than sell you the wrong thing. If your work is purely academic, skip it — the Obsidian and Zotero setup above is the better use of your next hour.