Obsidian vs Logseq: same files, opposite brains

Updated August 2026

We build a local-first notes app that competes with both, so we have no horse in this race — and the honest summary is that these two agree on everything except the most important thing: the shape of a note.

On paper the two apps are siblings: local Markdown files, backlinks and graph views, free for personal use, communities that care about data ownership. The split is the writing surface. Obsidian edits pages — a file is a document, and structure is whatever headings you give it. Logseq edits bullets— a file is an outline, every thought nests under another, and the day's journal is where everything starts. People who love one usually bounce hard off the other, and it has nothing to do with features.

Side by side

ObsidianLogseq
Where notes liveMarkdown files in a vault you ownMarkdown/Org files in a graph folder
Writing modelDocuments — free-form Markdown pagesOutliner — every line is a bullet
Daily notesOptional plugin-style featureThe default front door
Block referencesPossible, with syntax and careNative and first-class
Plugins & themesThousands, very activeSmaller catalogue
Open sourceNo — free but closed sourceYes
Mobile appsYes, solidYes
Development paceFast and steadySlower lately, mid-rebuild
SyncPaid add-on, iCloud, or DIYPaid sync or DIY
PriceFree; paid sync/publishFree, open source

Choose Obsidian if…

…your notes read like writing. Drafts, essays, meeting notes that become documents, a personal wiki of reference pages — Obsidian treats each file as a page and gets out of the way. It also wins on ecosystem: thousands of plugins, constant releases, and answers to any question one search away. The cost is the workshop problem — vaults, themes, and plugin curation are a hobby in themselves — and the fact that, unlike Logseq, the code is closed.

Choose Logseq if…

…your notes arrive as fragments. Logseq's journal-first, bullet-everything model is superb for interstitial thoughts, tasks threaded through the day, and ideas that grow by indentation. Block references — citing one bullet inside another page — remain its killer feature, and it's genuinely open source. The honest caveats: prose fights the outliner, and development has been quieter while the team rebuilds the app's foundations.

The third answer

Some people try both and want neither raw Markdown nor an outliner — they want structured pages without the machinery: blocks you can drag, tables that hold their shape, and nothing to configure first. That's the gap we built Locus for: a native Mac app where the workspace is plain files, the editor thinks in blocks, and setup is opening the app. We compare ourselves honestly against each — see Locus vs. Obsidian and Locus vs. Logseq — including what each does better. For the wider field, start with the best Obsidian alternatives.

Questions people ask

Is Obsidian or Logseq better?+

Neither is better in the abstract — they store notes the same honest way (local Markdown files) and differ in the shape of thought they assume. Obsidian assumes documents: pages of prose you structure with headings. Logseq assumes outlines: nested bullets that accumulate in a daily journal. Pick by how your notes actually come out of your hands, not by feature lists.

Can Logseq open an Obsidian vault?+

Mostly, yes — both read Markdown, and many people point both apps at the same folder. It works better in the Obsidian→Logseq direction than the reverse: Logseq rewrites files in outline form (every line a bullet), which Obsidian then displays as literal dashes. If you try dual-running, keep a backup of the vault first.

Is Logseq still actively developed?+

Yes, but the cadence has been slower while the team rebuilds the app around a database engine — a long-running transition that has left the classic file-based version quieter than Obsidian's release train. Nothing about your files is at risk (they're plain Markdown either way), but if you want the tool that ships improvements every month, Obsidian currently has the momentum.

Which one is easier for a beginner?+

Logseq is arguably simpler on day one — open it and type into today's journal, no vault decisions. Obsidian asks for more setup but behaves more like a normal notes app once configured: pages with names, folders if you want them, prose that reads as prose. If neither shape fits — you want structure without an outliner, and zero setup — that's the gap a block editor like Locus fills.