Logseq vs Obsidian is not a feature fight. Both are free, both keep your notes as files on your own disk, and both have a plugin scene. They disagree about one thing: what a note is. Logseq says a note is a bullet, nested inside other bullets, addressable on its own. Obsidian says a note is a file with a name, and links are text pointing between files.
Pick the outliner if you think in fragments and want yesterday's journal page to be the front door. Pick the file tree if you write in paragraphs and want the folder to still make sense to somebody who has never heard of either app.
Logseq vs Obsidian: the differences that actually bind
| Logseq | Obsidian | |
|---|---|---|
| unit of thought | a block — one bullet, with its own id | a page — one file, with a name |
| default entry point | today's journal, already open | whatever you last had open |
| storage | Markdown or Org-mode files, or a SQLite graph in the newer build | Markdown files in a folder |
| licence | AGPL-3.0, source on GitHub | proprietary app, free to use |
| what you pay | nothing | nothing for the app; Sync is $4 a month billed annually |
| linking style | block references and embeds as a daily habit | page links, with block links available |
| structure you get for free | the journal and the linked-references pane | folders, and nothing else |
Logseq's licence and file formats are stated on the project's GitHub repository; the Obsidian price is from Obsidian's pricing page and is in USD.
Read the release status before you commit
This is the part a feature comparison will not tell you, and it changes the decision.
Logseq is mid-rewrite. The 2.0 line is the database version, released as a beta — 2.0.1 is the tagged desktop build — while the older file-based line sits at 0.10.15. Nightly builds ship alongside both and are labelled unstable. The project's own README is blunt about the state of the new version: it says the DB version is in beta while the new mobile app and RTC are in alpha, that data loss is possible, and that automated backups or regular SQLite backups are advised, with a dedicated test graph rather than anything you depend on.
That is a project being honest, not a project in trouble, and reading a version date as a death notice is how people end up wrong about open-source software. But it does mean that "should I use Logseq" has two answers depending on which build you install, and you should check the releases page yourself before starting a graph you intend to keep.
Obsidian has no equivalent split. One app, one storage model, and updates that do not ask you to pick a track.
What the outliner actually changes
Every line in Logseq is a block, so every line can be referenced, embedded and queried without becoming a page first. In practice that means you stop naming things. You type into today's journal, tag a couple of words, and the linked-references pane on the tag page assembles the note for you later.
For meeting notes, reading fragments and half-thoughts, this is faster than anything file-based. For a 2,000-word draft, it is worse, because an outliner turns prose into a bullet list and prose does not want to be a bullet list.
Obsidian's cost is the opposite one. You have to decide where a note goes and what it is called, every time, before you can write. That friction is why a lot of Obsidian vaults have an untitled-note graveyard, and why the plugins people install first are the ones that automate naming and filing.
Where Logseq is better
Capture, and it is not a close call. The journal is already open, the cursor is already in it, and nothing asks you for a filename. If most of what you write is caught rather than composed, Logseq removes a decision you were making forty times a day.
Block references beat page links for anything you want to quote in three places without copying it. Org-mode support is real, which matters to a specific and loyal group. And AGPL-3.0 means the thing cannot quietly become a subscription; the source is there.
Where Obsidian is better
Stability of the deal. One app, one format, a large plugin ecosystem with commercial backing behind the core, and a sync service you can pay for rather than assemble.
Obsidian handles long documents properly, which sounds dull until you try to write something substantial in an outliner. Its mobile app is the one people actually keep on their phone. And the folder it leaves behind is the plainest possible artifact: named Markdown files, no bullet nesting imposed on prose, readable in any editor.
If neither model fits, the wider field is covered in personal knowledge management apps, and the hosted-versus-local version of this argument is Notion vs Obsidian.
Is Logseq compatible with Obsidian, in practice
Both read a folder of Markdown, so you can point Obsidian at a Logseq graph and the text will be there. What does not survive is meaning.
- Copy the graph folder first. Never test this on the only copy.
- Open the copy in Obsidian. Every Logseq block becomes a Markdown list item, so pages read as one deep bullet list rather than prose.
- Expect
property::lines to show as literal text, because Obsidian's frontmatter is a different convention. - Expect block references to break. They point at ids Obsidian does not resolve.
- Do not run both apps against the same folder day to day. Each writes its own metadata, and you will get conflicts you cannot diagnose.
The honest summary is that the files move and the structure does not. That is true in both directions, and it is the real switching cost.
Where init.Tasks fits
init.Tasks is a keyboard-first task and project app on iOS, macOS and web that stores everything in one hierarchy instead of a graph you curate: areas, then projects, then subprojects and to-dos, with depth capped there on purpose.
That cap is the point. A graph can represent anything, which is why maintaining one is work. A tree can represent less, which is why it stays legible on a Thursday when the actual job is to finish something. Reference material — the link, the note, the file — attaches to the project rather than floating in its own layer.
Quick add takes plain language, so book the vet 12 nov #pets files itself. There is a today view with overdue rolling in, a someday shelf, saved filters and a logbook. If your list is more about doing than about thinking, the Todoist vs TickTick comparison is the closer neighbour, and the feature list states exactly what has been built and what has not.
The AI connection is coming in september. There is no store page: the way in is the waitlist, with invites in september, and the beta is free while in beta — pricing undecided.
FAQ
Why are people leaving Obsidian?
Three recurring reasons, none of them about the core app. Plugin maintenance, once a setup depends on somebody's unpaid side project. The blank-vault problem, where an app with no opinions never gets set up at all. And sync cost, for people who want notes on a phone without paying a subscription. Plenty of others leave because they wanted a task manager and built a wiki instead.
Is anything better than Obsidian?
Better at what. Logseq is better at catching thoughts you have not organised yet. Notion is better at structured tables with views. A task app is better at making you finish things. Obsidian is the best default when you want plain files, one app and a large plugin ecosystem, and "best" stops being a useful word past that point.
Is Logseq compatible with Obsidian?
Partially. Both store notes as Markdown in a folder, so text and attachments move across. Logseq's block ids, block references and property:: lines do not translate, and its outliner writes every line as a list item, so pages arrive in Obsidian as nested bullets. Copy the folder before you try it, and do not point both apps at the same directory.
What are Logseq disadvantages?
The outliner forces bullets on prose, which makes long-form writing awkward. The project is mid-rewrite, so you have to choose between the file-based line and the 2.0 database beta whose own README warns that data loss is possible. Mobile has historically lagged the desktop app. And block references, used freely, create a web that only you can navigate — the same trap described in what is a second brain.