Obsidian — Markdown Notes You Own Forever

Obsidian stores notes as plain Markdown files on your own disk and links them into a knowledge graph. Free, offline, and durable — with no real collaboration.

Official Site https://obsidian.md
Category Writing
Pricing Free
Rating ★★★★★ (5/5)

What Obsidian is

Obsidian is a note-taking application that operates directly on a folder of Markdown files — a “vault” — on your own disk. Notes link to each other with [[wiki-style]] brackets, and the app builds a navigable graph of those connections. Everything beyond the basics comes from a large community plugin ecosystem.

The architectural fact that everything else follows from: there is no database and no proprietary format. Your notes are .md files in an ordinary folder, readable in any text editor, greppable from a terminal, and versionable in Git. If Obsidian disappeared tomorrow you would lose an interface and nothing else — which, for a body of notes you intend to keep across a career, is a materially different proposition from every hosted alternative. Local files also mean it works offline: on a plane, in a field station, on a machine with no network at all.

Why researchers use it

  • Your notes are files — no export step, no lock-in, no format that stops being readable when a company changes strategy.
  • Linking surfaces connections — the paper you read in year one turns out to bear on the chapter you write in year three, and the backlink is how you find out.
  • Zotero integration — the Citations plugin pulls paper metadata directly into literature notes, so citing from your notes is a keystroke rather than a lookup.
  • Dataview — query your vault like a database: every paper tagged #to-read, every note mentioning a method, assembled automatically and kept current.
  • It works offline and syncs how you choose — Git, a cloud folder, or Obsidian’s own paid sync, and none of them are mandatory.

Where it fits in a research workflow

Obsidian is the thinking layer between reading and writing — where papers become ideas and ideas become arguments. It is not a reference manager and not a manuscript tool, and treating it as either produces frustration.

The pipeline that works: capture papers in Zotero, write literature notes in Obsidian with metadata pulled in by the Citations plugin, develop your own synthesis in permanent notes, and when a chapter takes shape, export the Markdown through Pandoc to PDF or Word — or move to Overleaf if the venue wants LaTeX. The complete PhD setup walks through the whole arrangement. It even presents: Advanced Slides turns a note into a deck without opening PowerPoint.

Getting started

An hour to a working vault, and resist the temptation to build a system first.

  1. Create a vault as an ordinary folder and start writing notes. Do not spend the first week configuring plugins and folder hierarchies — the structure that works emerges from the notes, and the one you design in advance never survives contact with them.
  2. Install three plugins and no more: Citations for Zotero, Dataview for querying, Templater for note templates. Add others only when you hit a specific problem you can name.
  3. Write one literature note per paper you read, in your own words. This is the habit that makes the vault valuable; the software is incidental to it.
  4. The step people skip: put the vault in Git. Plain Markdown versions beautifully, you get a full history for free, and you get an off-machine backup — which is the actual disaster you are guarding against.

Obsidian vs the alternatives

AlternativeDoes it betterPick it if
LogseqOutliner-first structure, block references, daily journalingYou think in bullets rather than documents
NotionReal-time collaboration and structured databasesThe notes are shared lab infrastructure
ZettlrAcademic writing with citations and Pandoc export built inYou want to write papers, not maintain a vault
ZoteroEverything about managing the papers themselvesYou need references, not notes about them

Obsidian wins on ownership, longevity, and flexibility. It loses badly on collaboration, which is genuinely single-user territory.

Cost, licensing, and your data

Free for personal and academic use, including all core features and the entire community plugin ecosystem — the free tier is the product, not a trial. Paid add-ons are optional: an end-to-end encrypted sync service and a publishing service. A commercial licence applies to company use, which does not affect academic work.

Data governance is as clean as it gets: notes are files on your disk, nothing is uploaded unless you choose a sync method, and the vault can live on an encrypted volume or an institutional drive. That makes Obsidian appropriate for notes containing participant quotes or unpublished results in a way hosted note apps are not. The caution is plugins — they are community-written code with access to your entire vault, so install deliberately and prefer widely used ones. The same judgement you would apply to a browser extension applies here.

The honest review

Strengths. Ownership is the feature, and it compounds over a career. Plain Markdown means the notes you write during a PhD are still readable and searchable in twenty years regardless of what happened to the company — a claim no hosted competitor can make. The linking model genuinely does surface connections you would otherwise lose, and combined with Zotero and Dataview it becomes a research system rather than a note app.

Limitations. Collaboration is effectively absent. A shared folder is not co-editing, and any workflow needing two people in one note at once is the wrong workflow for this tool. The plugin ecosystem is both its greatest strength and a real fragility — plugins break on updates, get abandoned, and occasionally conflict, so a vault depending on five community plugins carries five maintenance risks. It invites procrastination through configuration: an entire subculture exists around building note systems instead of writing. And mobile editing, while functional, is not pleasant.

Verdict. Adopt it if you read a lot and want the notes to still be there in ten years. Skip it if your notes need to be shared and co-edited, or if you suspect you will spend more time configuring it than writing in it. The condition that flips the answer is honesty about that second point — for some people the tool becomes the project.

When NOT to use this Do not build the system before you have the notes. The most common failure with Obsidian is not data loss but displacement activity: weeks spent designing folder hierarchies, tag taxonomies, and plugin stacks for a vault containing eleven notes. The structure that works is the one that emerges from a hundred real notes, and no amount of upfront design substitutes for having written them. Start with a folder and plain notes; add structure when its absence starts hurting.

Common questions

Is Obsidian free?

Yes, for personal and academic use — all core features and the full community plugin ecosystem, with no time limit. Optional paid services add encrypted sync and web publishing, and a commercial licence applies to company use.

Can I use Obsidian with Zotero?

Yes, and it is one of the strongest reasons to choose it. The Citations community plugin reads a .bib file exported from Zotero — kept current by Better BibTeX — and pulls paper metadata directly into your notes, so literature notes carry live citation data.

Is Obsidian good for collaborative note-taking?

No. It is designed for a single user on local files, and a shared cloud folder produces sync conflicts rather than collaboration. For shared lab notes, Notion is the appropriate tool.