Logseq vs Obsidian: Blocks, Pages and Your Markdown Files

November 11, 2026 · 11 min read

Logseq vs Obsidian: Outliner Blocks or Markdown Pages?

The Logseq vs Obsidian choice comes down to one design decision. Logseq is an open-source outliner where every bullet is a block, and the daily journal is home. Obsidian treats each note as a Markdown page you write like a document. Pick Logseq if you think in bullets, and Obsidian if you write prose and want stable .md files.

Logseq vs Obsidian at a Glance: Blocks or Pages

In Logseq, you open today's journal, type short nested points, tag them with pages, and let backlinks collect them later. Its source code is public on GitHub under the AGPL-3.0 licence.

In Obsidian, a note has headings, prose and lists in whatever order you like, inside a vault folder you choose. The app is free to use, including for work, but isn't open source, and you extend it with core and community plugins.

Logseq (file version)Obsidian
Unit of writingBlock (one bullet)Page (one file)
Home screenDaily journalWhatever note you open
Propertieskey:: value linesYAML front matter
Link to a paragraph((uuid)) block reference[[note#^id]] block link
LicenceOpen source, AGPL-3.0Proprietary, free to use

Obsidian and Logseq's file version both keep notes as Markdown on your disk, but the Markdown differs, and that decides how portable your notes are. For sync, platforms and prices across the wider field, see our roundup of eight Markdown note apps.

How Each App Writes the Same Note to Disk

The quickest way to see the difference is one meeting note saved by each app. Here's how Logseq's file version stores it in the graph's pages folder:

type:: meeting
date:: [[Nov 11th, 2026]]

- We agreed to move the launch to January.
  id:: 6731a2f4-9c1e-4b7a-8d2e-1f0a3c5b7e91
- TODO Send the Q4 draft to Priya
- Budget
	- See [[Q4 planning]] for the numbers
	- Travel costs are still open

The first two lines are page properties. Every other line is a - block, and children sit one tab deeper. The id:: line appeared when another block referenced the launch decision, and TODO is a task marker, not a checkbox.

Here's the same note as an Obsidian file, which can live in any folder of the vault:

---
type: meeting
date: 2026-11-11
---
# Weekly review

We agreed to move the launch to January. ^launch-decision

- [ ] Send the Q4 draft to Priya

## Budget

See [[Q4 planning]] for the numbers. Travel costs are still open.

Properties sit in a YAML block between --- lines. The rest is ordinary Markdown with headings and paragraphs, a GFM task, a wikilink and a ^launch-decision marker that names the paragraph so other notes can link to it.

Folder layout differs too. A Logseq graph gets journals, pages and assets folders plus a logseq folder holding config.edn. An Obsidian vault is any folder structure you like, with settings in a hidden .obsidian folder at its root.

Properties: Logseq key:: value Lines vs Obsidian YAML

Logseq stores metadata as key:: value lines. In the first block of a page they become page properties, and under any other bullet they belong to that one block. Values can hold page links and tags, so type:: [[meeting]] links to a meeting page. That block-level scope is something Obsidian doesn't have.

Obsidian keeps properties as YAML at the top of the file, one set per note. You edit them in a form with types such as Text, List, Number, Checkbox, Date and Tags, and Obsidian writes the YAML for you. Our Obsidian cheat sheet covers the property and link syntax in detail.

The practical gap shows up outside the apps. YAML front matter is understood by static site generators, Pandoc and plenty of scripts. A key:: value line is meaningful to Logseq and to Obsidian's Dataview plugin, which reads the same Key:: Value pattern as inline fields, but almost nothing else.

Block References vs Wikilinks: How Each App Links Notes

Both apps use [[Page name]] to link pages, so simple links travel well between them. The split is at the paragraph level.

In Logseq, you reference a block with its UUID in double parentheses, ((6731a2f4-...)), and Logseq shows the referenced text inline. Logseq writes an id:: property into the target file so the address stays stable. Outside Logseq, though, the reference is a string of hex characters with no hint of what it pointed to.

Obsidian links to a block with [[note#^id]], and to a heading with [[note#Heading]]. You can name the block ID yourself, as in ^launch-decision, using Latin letters, numbers and dashes. Putting ! in front, as in ![[note#^id]], embeds the content instead of linking to it. Obsidian can also write standard Markdown links if you turn off Use [[Wikilinks]] under Settings, then Files and Links.

Queries and Plugins: Logseq's Built-in Queries vs Bases and Dataview

Queries come built into Logseq. A simple query lives inside a block, and advanced queries use Datalog:

- Open tasks across the graph
	- {{query (task TODO DOING)}}

That block lists every TODO and DOING task in the graph. Logseq also includes flashcards and PDF highlighting without extra installs.

Obsidian's answer is the Bases core plugin, which turns notes into views such as tables, defined in YAML in a .base file or a base code block. Here's a minimal one.

filters:
  and:
    - file.hasTag("meeting")
views:
  - type: table
    name: Meetings

That base shows every note tagged meeting as a table you can sort and edit. For task lists, many people add the community Dataview plugin, where a dataview block containing TASK FROM #projects lists open and done tasks from those notes.

Plugins are where the Logseq vs Obsidian gap is widest. Obsidian's community directory is much larger than Logseq's marketplace, and most Obsidian workflows you read about assume a few community plugins. Logseq has plugins too, but more of its power is built in.

Can You Move Notes Between Logseq and Obsidian?

Yes, in both directions, but each move has losses. Going from Logseq to Obsidian, the Obsidian Importer has a Logseq option for file-based graphs. Per its help page, it converts page properties, block references and embeds, journals and task markers, and can optionally flatten outlines into paragraphs and headings. Queries and flashcards have no direct equivalent, so they come through as plain text or code blocks. Whiteboards aren't imported, and DB graphs aren't supported yet.

Going from Obsidian to Logseq, you can open the vault folder as a graph, and Logseq indexes the Markdown files inside it. Journals need care: Logseq expects daily pages in its own journals folder, named in its configured date format, so check that your Obsidian daily notes show up as journal days before you rely on them.

Metadata and Obsidian extras fare worse. Even if Logseq picks up your existing front matter, it writes new properties in its own key:: form. Obsidian-only syntax such as ^id markers, callouts and %%comments%% isn't part of Logseq's Markdown, so Logseq won't treat it the way Obsidian does.

Then there's the third destination: any plain Markdown editor. The note below mixes both apps' syntax. Watch what a standard CommonMark and GFM preview makes of it:

Weekly review

  • type:: meeting
  • date:: [[Nov 11th, 2026]]
  • TODO Send the Q4 draft to Priya
  • Decision from last week: ((6731a2f4-9c1e-4b7a-8d2e-1f0a3c5b7e91))
  • See [[Q4 planning#^budget]] for numbers
  • Book the venue
  • Share the agenda

Standard link that works everywhere: Q4 planning

49 words316 characters10 lines
Markdown

The bullets render, and the last two items become GFM checkboxes. Everything app-specific stays literal: the type:: property, the TODO marker, the ((uuid)) reference and both wikilinks. Our editor's preview doesn't render wikilinks or any Logseq syntax, so only the final line produces a working link.

To clean a single Obsidian note into standard Markdown, paste or upload it into our Obsidian to Markdown converter. It rewrites wikilinks, embeds, callouts, highlights, comments, tags and front matter, one note at a time. It targets Obsidian syntax only, so it doesn't convert Logseq's key:: lines, ((uuid)) references or query macros. For a Logseq graph, use the Obsidian Importer or Logseq's own export.

We prefer connecting key notes with page links rather than block references, and using standard Markdown links wherever the notes might leave both apps. Keep metadata to a few fields. Notes written that way move between apps with little cleanup.

Is Logseq Still Active? The 2026 Split and Your Markdown Files

Yes, but it's now two apps. On April 24, 2026, the team announced a split: Logseq OG keeps file-based Markdown graphs and gets maintenance, security and Electron updates but no new features. The app called Logseq is the database version and the main line going forward.

You can install both side by side, and you aren't forced to migrate. A Markdown graph import tool moves a file graph into the database version when you're ready. The announcement says Markdown support for DB graphs is planned, but the team is still researching how to do it. The 2.0 releases on GitHub, 2.0.1 in July and 2.0.2 in October 2026, are labelled beta.

For a Markdown-first reader weighing Logseq vs Obsidian, this is the honest limitation of picking Logseq today. The file version is stable but frozen, and the version getting new features no longer stores your notes as a folder of .md files. Our Logseq note taking app guide covers what the DB version changes and how its importer handles your Markdown files.

Obsidian vs Logseq: Which Should You Pick in 2026?

It comes down to how you think and how much file stability matters to you.

Pick Logseq if your notes start as bullets in a daily journal, you lean on block references, or you annotate PDFs and review flashcards in the same app. Accept that you're choosing between a maintenance-only file version and a database version still in beta.

Pick Obsidian if you write long-form notes, want stable .md files with YAML front matter that other tools understand, or want the larger plugin ecosystem. The trade-off is that the app itself is closed source and its link syntax is its own. If you're weighing its editing modes, read our review of what editing in Obsidian is like.

Some people run both apps on one folder. It works, but each app shows the other's special syntax as text. If you try it, let one app do the writing and use the other mainly for reading and linking.

In the end, Logseq vs Obsidian is a choice between blocks and pages, and between a file format in transition and one that's stable. Pick the app that matches how you write, then keep your most important notes in standard Markdown so a future move is painless. To see any note without app-specific syntax, paste it into the editor and compare the raw text with the live preview.