Obsidian and Roam Research are the two tools most frequently debated among serious knowledge workers and researchers who want a networked note-taking system built for longevity. They share a commitment to bidirectional links and non-linear thinking but differ fundamentally in their storage model (Obsidian keeps notes as local files you own; Roam stores them in the cloud), their structural approach (Obsidian is file-based while Roam is block-based), their cost (Obsidian is free to use locally while Roam charges $15/month), and their extensibility (Obsidian has over 1,000 community plugins; Roam is intentionally minimal).
Obsidian vs Roam Research: Key Differences at a Glance
| Obsidian | Roam Research | |
|---|---|---|
| Storage | Local Markdown files | Cloud (Roam servers) |
| Cost | Free (local); $10/mo sync | $15/mo ($180/yr) |
| Open source | ❌ Proprietary | ❌ Proprietary |
| Core model | File-based Markdown | Block-based outliner |
| Block transclusion | Via plugin | ✅ Native live portals |
| Plugin ecosystem | ✅ 1,000+ plugins | Minimal, power-user |
| Daily notes | Via plugin | ✅ Primary interface |
| Mobile app | ✅ iOS + Android | ✅ iOS only |
For Local-First Data Ownership and Privacy
Obsidian stores your notes as plain Markdown files on your local device. You can open them in any text editor, sync them with any service you choose (iCloud, Dropbox, Syncthing, or Obsidian's own paid sync), and they remain fully accessible offline and without an active subscription. Your notes belong to you in the most literal sense: they are files on your filesystem that no company can revoke access to. For researchers at institutions with data governance requirements — clinical notes, embargoed research, confidential interview data — the ability to keep notes entirely local is essential.
Roam Research stores your notes on Roam's servers. You can export to JSON or Markdown, but the live database requires a paid subscription to access. If you stop paying, your ability to use the interface disappears even though your data can be exported. For users with strict data sovereignty requirements, Roam's cloud-only model introduces a dependency on a third-party service that Obsidian's local-file approach eliminates. Neither Obsidian nor Roam is open-source, but Obsidian's local storage means you can verify what is leaving your device; Roam requires trusting that your notes are handled appropriately on their servers.
Obsidian wins for: Complete data ownership — your notes are local files that no subscription can lock away. For researchers handling sensitive data or working in regulated environments, Obsidian's local-first model is the only viable option.
For Block-Level Transclusion and Deep References
Roam's block-referencing primitives are among the most powerful of any PKM tool. Roam's "portals" allow you to embed a block into a new context where both the original block and the embed are live — editing either location updates both simultaneously. Block references maintain a full count of all linked occurrences across the graph, the right sidebar allows side-by-side work with referenced material, and Roam's Datalog-based query system allows precise structured retrieval: find all blocks with specific tags that also reference specific pages, filtered by date ranges and excluding specific terms. For researchers building complex linked frameworks — theoretical arguments that need to reference evidence from multiple papers simultaneously, or systematic literature maps — Roam's native block model provides referencing depth that Obsidian's file-based architecture cannot match natively.
Obsidian can replicate some of this with plugins (block references exist; Dataview provides database-style queries), but the underlying model is different: Obsidian embeds from files rather than blocks, and the referencing feels layered on top of a file system rather than native to a block-level graph. For users who have deeply internalised Roam's block-reference-first workflow, Obsidian's implementation feels like a workaround.
Roam wins for: Users who need live block transclusion and deep Datalog queries across their graph. Roam's block-reference primitives are native; Obsidian's equivalents are plugin-based and architecturally secondary.
For Plugin Ecosystem and Customisation
Obsidian's 1,000+ community plugins cover nearly every workflow extension a researcher could need: Zotero integration (ZotLit), database views with spreadsheet-style tables (Dataview), automation (Templater), AI assistance (Smart Connections, Copilot), canvas whiteboards (Canvas), task management (Tasks), citation management, spaced repetition, and complete visual redesigns via custom CSS. This ecosystem means almost any niche requirement — a specific academic database integration, a proprietary calendar connection, a custom publishing workflow — has a maintained plugin. Obsidian's plugin ecosystem is one of the richest of any note-taking tool.
Roam's extensibility is deep but narrow. Roam supports Clojure-based extensions and JavaScript injected via its API — extremely powerful for developers but inaccessible for most researchers. The most capable Roam customisations are built by programmers for their own use and documented in community posts rather than installable from a marketplace. Non-developers find Obsidian significantly more extensible in practice, while power-user developers find Roam's Clojure integration more expressive.
Obsidian wins for: Non-developers who need rich customisation and workflow integrations. Obsidian's plugin marketplace replaces the need for programming knowledge that Roam requires for meaningful extensibility.
For Long-Form Writing and Document-Based Research
Obsidian's file-based model naturally supports researchers who think and write in longer documents. Each Markdown file is an independent document that can be opened, read, and formatted as a complete piece. Literature review sections, chapter drafts, extended case study notes, and methodology write-ups are all natural Obsidian documents. The writing experience in a single Obsidian note — with standard Markdown headings, prose paragraphs, and reading mode — is cleaner than Roam's outliner interface, where everything is a bulleted block and the hierarchy of an argument is represented through indentation rather than document structure.
Roam's outliner model is optimised for non-linear capture and connection rather than linear reading and writing. Reading a Roam page as a document is harder than reading an Obsidian note, because the block-bullet structure interrupts flow. For researchers who need to produce readable documents from their notes — turning research notes into drafts, sharing notes with collaborators who are not also Roam users — Obsidian's Markdown files are significantly more portable and readable.
Obsidian wins for: Researchers who write in longer documents and need notes that read as prose rather than outlines. Obsidian's Markdown files move naturally to actual writing; Roam's block structure is optimised for capture rather than linear reading.
For Daily Notes and Networked Capture
Both tools support daily notes-first capture, but the experience differs in emphasis. Roam makes the daily journal page the literal primary interface — opening Roam takes you directly to today's page, and the entire philosophy encourages logging everything into the daily note before connecting it later. This makes Roam feel more like a stream-of-consciousness capture tool. Obsidian has a Daily Notes plugin and periodic notes plugins, but because Obsidian is file-first rather than journal-first, the daily note is one file among many rather than the mandatory starting point.
Users who journal heavily, take meeting notes across multiple daily pages, and rely on retroactive connection through backlinks will likely find Roam's daily-notes-first design more natural. Users who occasionally use daily notes alongside more structured project notes and reference documents will find Obsidian's flexible model more accommodating.
Roam wins for: Pure daily-journal-first workflows where every capture starts in today's page. Roam's interface makes this the natural default; Obsidian accommodates daily notes but doesn't enforce them as the entry point.
What Neither Obsidian nor Roam Research Addresses
Both Obsidian and Roam are excellent at organising and connecting what you have already read and written. Neither synthesises across a collection of research papers to help you understand what the literature collectively argues before you begin writing. Ponder addresses this pre-writing stage: import the papers you have collected — PDFs, DOIs from OpenAlex's 250M+ academic index — ask AI questions across the full set, and get answers that cite specific passages from specific papers. The synthesis works from the source material directly rather than from your notes about the source material.
A complementary workflow: Ponder for synthesis of your paper collection before drafting, then Obsidian or Roam for the networked notes and active writing that follow. Ponder handles the pre-writing stage that neither Obsidian nor Roam was designed for.
Try Ponder for academic research →
Frequently asked questions
Should I migrate from Roam Research to Obsidian?
Migrate if the $180/year subscription cost has become difficult to justify, you want your notes as local files rather than dependent on cloud access, you need a richer plugin ecosystem for integrations like Zotero or Dataview, or you write in longer prose documents that feel awkward in Roam's outliner. Stay with Roam if you rely deeply on live block portals and Datalog queries, or if you have built years of interconnected Roam notes that would lose fidelity in a plain Markdown import — Roam's block IDs and live embeds do not transfer seamlessly to Obsidian. The export-import is technically possible but rebuilding workflows takes significant time.
Which is better for PhD research?
Obsidian is the better default for most PhD students: it is free (no subscription over a 4-6 year PhD), stores notes as portable Markdown files, supports Zotero integration via ZotLit for citation management, and has plugins for PDF annotation, spaced repetition, and canvas whiteboards. Roam's deeper block references are valuable for researchers who build highly connected theoretical frameworks and are willing to pay for and invest in Roam's distinctive model. If you are starting fresh, Obsidian's free access and plugin ecosystem reduce risk. If you are already a Roam user with an established graph, the switching cost typically outweighs the financial saving.
Can you use Obsidian and Roam Research together?
Using both simultaneously is unusual and creates friction — notes in one are not accessible in the other, and maintaining two interconnected databases is overhead without clear benefit. A common approach for users transitioning is to archive old Roam notes in an Obsidian vault imported via Roam's Markdown export, then continue new notes in Obsidian. Some researchers use Roam specifically as a daily-journal capture tool and Obsidian as their structured reference database, keeping the two separate by purpose rather than integrated. The tools are not designed to interoperate.
See also: | Obsidian Alternatives | Roam Research Alternatives | Logseq vs Obsidian | Logseq vs Roam Research | Notion vs Obsidian | Tana Alternatives