What Logseq is
Logseq is an open-source, local-first note application. Notes are Markdown or Org files in a folder you control, but the editing model is an outliner: everything is a bullet, bullets nest, and each individual bullet — a block — can be referenced from anywhere else.
Two design decisions distinguish it from Obsidian, which is otherwise its closest relative. The first is that the daily journal is the home screen: you open Logseq and you are writing today’s entry, with structure emerging from links rather than from filing. The second is block-level referencing: you can cite a single bullet — one claim, one observation, one quotation — in another note, and the reference stays live. Between them, those two choices make Logseq unusually good at capturing a research day as it happens, which is a different activity from writing a document about it afterwards.
Why researchers use it
- Block references — quote a single observation from Tuesday’s journal inside a chapter draft, and it remains linked to its original context.
- Journal-first capture — a dated research log accumulates from ordinary use rather than requiring you to maintain one.
- PDF annotation built in — highlight a paper inside the app and each highlight becomes a referenceable block, which is a genuinely smooth path from reading to notes.
- Local Markdown files — the same ownership guarantee as Obsidian: your notes are plain text on your disk, versionable in Git.
- Open source throughout — including the sync question, which you solve with your own storage rather than a vendor’s service.
Where it fits in a research workflow
Logseq covers capture and connection: the running record of what you did, read, and thought, linked into something navigable. It is not a manuscript tool and it is not a reference manager.
The arrangement that suits it: papers in Zotero, read and annotated in Logseq’s PDF viewer so highlights become blocks, daily observations in the journal, and when a chapter takes shape, blocks pulled together and exported through Pandoc — or the argument rewritten properly in a document tool. That last handoff matters, because the outliner that makes capture fast makes long-form prose awkward. For a lab’s shared operational knowledge, Notion is the right tool; for a citation-native writing environment, Zettlr.
Getting started
An hour, and give the journal a fair trial.
- Install Logseq and point it at a folder — one that is already in Git or a backed-up location, since it coexists with version control happily.
- Live in the daily journal for a week before creating any pages. Structure in Logseq emerges from links and tags rather than from a hierarchy you design, and the journal is where those links get made.
- Open a paper’s PDF in the app, highlight as you read, and see the highlights appear as blocks. This is the workflow most likely to convince you.
- The step people skip: learn block references properly — the
((syntax and the difference between embedding and linking. They are the feature Logseq has and Obsidian does not, and using it as a plain Markdown editor means paying the outliner cost for no benefit.
Logseq vs the alternatives
| Alternative | Does it better | Pick it if |
|---|---|---|
| Obsidian | Free-form pages, a far larger plugin ecosystem, faster development | You write in paragraphs rather than bullets |
| Notion | Real-time collaboration and structured databases | The notes are shared lab infrastructure |
| Zettlr | Citations and Pandoc export for academic writing | You want to draft papers, not maintain a graph |
| Anki | Making facts stick | The problem is recall, not organisation |
Logseq and Obsidian are close enough that the honest advice is to try both for a week. The outliner question decides it, and it is a question about how you think rather than about features.
Cost, licensing, and your data
Free and open source under AGPL, with a paid optional sync service. Notes are Markdown or Org files in a local folder, so ownership and portability are as good as this category gets — you can walk away with everything readable.
That local-first design means nothing is uploaded unless you choose a sync method, which makes it appropriate for notes containing unpublished findings or participant quotes. Two practical cautions. Logseq writes its own metadata into the Markdown files — block IDs and properties — so a note read in a plain text editor is slightly noisier than an Obsidian equivalent, and full portability is a little less clean than “just Markdown” suggests. And development pace has been uneven, with a long-running database-backend rewrite; the files remain yours regardless, but plan on the basis that the app may change more than most.
The honest review
Strengths. The journal-plus-block-reference combination fits how research thinking actually arrives: fragmented, dated, and only later connected. Being able to reference a single observation rather than a whole note is a genuine expressive advantage over page-level linking, and the built-in PDF annotation closes the reading-to-notes gap more smoothly than most plugin-based equivalents.
Limitations. Everything is a bullet, and long-form prose fights that constantly — writing a paragraph in an outliner is possible and permanently slightly wrong. The plugin ecosystem is a fraction of Obsidian’s and development has been slower and less predictable, with a major architectural rewrite in progress for a long time. Performance degrades on large graphs. And the metadata written into your Markdown files makes the “plain text you own” claim a little less pure than it first appears.
Verdict. Adopt it if you think in bullets and want a research log that builds itself. Skip it if you draft prose in your notes app, where Obsidian is a better fit, or if you need collaboration, where neither applies. The condition that flips the answer is genuinely the outliner — try both for a week and notice which one you stop fighting.
Common questions
Is Logseq free?
Yes — free and open source under the AGPL, with an optional paid sync service. You can also sync with Git, a cloud folder, or any method you prefer, since notes are ordinary files.
Logseq or Obsidian?
They are close. Logseq if you think in bullets and want a journal-first workflow with block-level references. Obsidian if you write in paragraphs, want a much larger plugin ecosystem, or value faster and more predictable development. Trying both for a week is genuinely the right way to decide.
Does Logseq work with Zotero?
There is community integration, though it is less mature than Obsidian’s Citations plugin. Logseq’s own PDF annotation is the stronger feature here — highlights made in the app become referenceable blocks, which covers much of what a Zotero bridge would give you.