Obsidian for academic research

Plain files, for one. Your vault is a folder of markdown on your own disk, readable in any editor, still openable in twenty years. After a decade of watching note apps get acquired and shut down, that matters more to academics than almost anyone.

Then the links. Zettelkasten as a method predates the software by fifty years, but Obsidian made the mechanics cheap enough that people actually kept it up. Type double brackets, get an edge, watch the graph fill in. For sustained thinking across hundreds of notes it genuinely works.

Search for an Obsidian literature review workflow and you will find the same recipe written up a dozen times. Inside Zotero you install Better BibTeX so your citation keys stay stable. Inside Obsidian you install either Zotero Integration or ZotLit to pull items and annotations across. You install Templater to shape the literature note that gets created on import. Most guides add Citations, or Highlightr for the annotation colours, and by then the dataview crowd has talked you into one more.

Four to six pieces of software, written by five different people, each on its own release cadence, held together by a template you wrote at 1am in March and will not understand in June. It works. Right up until Obsidian ships a breaking API change and one plugin lags a fortnight behind, which is precisely when you are three days from a submission deadline.

Is that a dealbreaker? For plenty of people, no. Tinkering is part of the pleasure, and a vault tuned over two years fits its owner better than anything off the shelf ever could. But it is a cost, and the guides tend to present it as a one-time setup rather than the maintenance it turns into.

The deeper issue is that the reading never happens in Obsidian. You read in Zotero or Preview, highlight there, then import a flattened copy of your annotations into a note. What arrives is text. The link back to the page, the position on it, the thing you were thinking when you highlighted it, all of that either gets templated into a string or lost.

So the citation in your draft says the paper. It rarely says where in the paper. That distinction costs you nothing while you are writing and a great deal when a reviewer asks you to justify a sentence you wrote eight months ago.

One app where the reading, the highlighting, the citing and the writing are the same activity. The four or five plugins a researcher installs first are the things note.md ships as core, so there is no configuration step and nothing to repair after an update. Files stay as markdown on disk, same as a vault, so the portability argument that brought you to Obsidian still holds.

The AI is where the two diverge most. Obsidian’s AI plugins mostly call a cloud API, which means your unpublished chapter goes to someone else’s server. note.md indexes and searches on your Mac. It finds the passage you read in March. It does not write the paragraph for you, which is a deliberate line rather than a missing feature.

The reference-manager half of the same stack is covered in a Zotero alternative for Mac. For how the linking works without plugins, see building a knowledge graph, and for the local-AI internals there is the architecture write-up.