Obsidian vs Logseq

The important question is no longer simply whether you prefer documents or outlines. Logseq now has a file-based OG edition and a newer database edition with different storage and migration behavior. Compare the exact edition you intend to install before making promises about portability or collaboration.

Editorial review 17 Sept 2026 · Based on vendor documentation · Recommendations are editorial interpretation

Customize this comparison Jump to prices & plans

The short answer

Obsidian is the clearer shortlist choice when you specifically want a vault of Markdown files. Logseq is worth evaluating when linked blocks and structured graph workflows match how you think. Treat its newer database edition as an evolving product with a separate backup and migration plan.

Based on the documented differences below. Your priorities can change the choice.

You want direct access to your notes as a folder of files

Its documented vault model remains based on local Markdown.

Check before choosing · Shared vaults

All collaborators need Sync. Shared vaults do not provide live co-editing cursors or fine-grained permissions.

Source

Linked outlines and graph properties are central to your workflow

Its node and property model supports that style of organization, with edition-specific constraints.

Check before choosing · Release status

The current main repository labels the database version beta and recommends a noncritical test graph.

Source

Prices and billing terms

Published prices keep their original currency and billing terms. Taxes, promotions and checkout prices can differ.

Obsidian

Core

Free

No account or paid license required

AvailabilityGlobal

Free for personal and commercial use.

Source

Sync Standard — monthly

USD 5.00/month

Billed monthly per user

AvailabilityUSD list price

1 vault, 1 GB storage and 5 MB maximum file.

Source

Sync Standard — annual

USD 48.00/year

Billed annually per user

AvailabilityUSD list price

Annual total calculated from the advertised $4 per month billed annually.

Source

Sync Plus — monthly

USD 10.00/month

Billed monthly per user

AvailabilityUSD list price

10 vaults, 10 GB storage and 200 MB maximum file.

Source

Publish — annual

USD 96.00/year

Billed annually per site

AvailabilityUSD list price

Annual total calculated from $8 per month billed annually; separate from Sync.

Source

Logseq

Local open-source app

Free

Open-source application

AvailabilityGlobal

File-based OG and DB edition are distinct. DB is currently described as beta.

Source 1Source 2

Sync access

Check current price

Current enrollment and edition need verification

AvailabilityNot established

Current DB documentation lists Sync access for OpenCollective Backers ($5/month) and Sponsors ($15/month). The main README still directs RTC users to an alpha signup. Enrollment and checkout were not verified, so these contribution levels are not presented as a confirmed subscription price.

Source 1Source 2Source 3
What will your offer actually cost?Compare your regional prices over 12 months.

Enter the offers you see at checkout. These are your estimates, separate from our sourced prices above. Use the same currency and region for every offer. This worksheet supports monthly bills, annual bills and purchases that cover the full year. Day-based passes and introductory rates need their actual renewal schedule checked separately.

No currency conversion. If offers use different currencies, calculate them separately. Changing a currency label does not convert an amount.

Obsidian
Enter the full bill for this interval, not an advertised monthly equivalent. Enter 0 for a free offer.
1 for a cancel-any-month offer. 12 for an annual contract paid monthly.
Seats, tax and optional extras
Use 1 if the amount above already covers the whole plan.
Total for all seats. Optional; blank means none included.
Total for all seats, paid every month. Optional; blank means none included.
Logseq
Enter the full bill for this interval, not an advertised monthly equivalent. Enter 0 for a free offer.
1 for a cancel-any-month offer. 12 for an annual contract paid monthly.
Seats, tax and optional extras
Use 1 if the amount above already covers the whole plan.
Total for all seats. Optional; blank means none included.
Total for all seats, paid every month. Optional; blank means none included.

Enter your terms then calculate. No offer prices are prefilled.

The scenario starts with a payment today and assumes 12 months of use at the same entered price, including any renewal. Monthly extras repeat 12 times; one-time extras are counted once. It excludes discounts, price changes, refunds, cancellation fees and anything you have not entered. Amounts are rounded to the currency’s usual precision. Confirm the actual charge and contract with the vendor.

Entries stay in this page while it is open. They are not saved or included in shared links.

The details, side by side

13 features

Row headings group related topics. Each answer keeps its specific scope. An unverified answer means we do not have enough evidence.

Platforms

Obsidian

Devices

Windows, macOS, Linux, iOS and Android apps are documented.

Vendor documentedSource

Logseq

Devices

Desktop, mobile and browser options exist; DB mobile readiness differs from the OG app.

Vendor documentedSource 1Source 2

Offline use

Obsidian

Offline access

The local vault remains available without a connection; Sync merges changes when connectivity returns.

Vendor documentedSource

Logseq

Local data

OG uses local file graphs. DB graph directories hold db.sqlite and a separate assets folder.

Vendor documentedSource 1Source 2

Edition distinction

Obsidian

Storage format

Notes are Markdown text in a local folder and can be edited with other text editors.

Vendor documentedSource

Logseq

Edition distinction

OG supports Markdown and Org-mode. DB graphs use SQLite rather than the same file graph layout.

Vendor documentedSource 1Source 2

Collaboration

Obsidian

Shared vaults

All collaborators need Sync. Shared vaults do not provide live co-editing cursors or fine-grained permissions.

Vendor documentedSource

Logseq

Collaboration maturity

The current repository describes DB real-time collaboration as alpha. The older file-sync guide explicitly excludes multi-person collaboration.

Vendor documentedSource 1Source 2

Export

Obsidian

Portability

Markdown files are directly accessible. Vault settings and extensions live separately in the .obsidian folder.

Vendor documentedSource

Logseq

DB export

DB offers SQLite with assets, EDN and standard Markdown exports. Markdown does not preserve every graph property.

Vendor documentedSource

Privacy and storage

Obsidian

Sync privacy

Official Sync documents end-to-end encryption; local-only use does not send notes to Obsidian.

Vendor documentedSource 1Source 2

Logseq

Not yet verified for this product.

Project portability

Obsidian

Notion migration

API import converts databases and formulas to Bases with limitations. ZIP import does not preserve databases.

Vendor documentedSource

Logseq

File to DB migration

The importer has documented limits where multiple queries or embeds share one old block.

Vendor documentedSource

Free plan limits

Obsidian

Core app cost

Core use is free without a mandatory account. Sync and Publish are optional services.

Vendor documentedSource

Logseq

Local app

Open-source local applications are available; hosted sync enrollment is separate.

Vendor documentedSource 1Source 2

Use at work

Obsidian

Use at work

Commercial use is free; the paid commercial license is optional support.

Vendor documentedSource

Logseq

Not yet verified for this product.

Team limit

Obsidian

Team limit

A shared vault supports at most 20 collaborators according to the current help page.

Vendor documentedSource

Logseq

Not yet verified for this product.

Linked structure

Obsidian

Not yet verified for this product.

Logseq

Linked structure

DB nodes combine page and block behavior with properties, tags and linked references.

Vendor documentedSource

Release status

Obsidian

Not yet verified for this product.

Logseq

Release status

The current main repository labels the database version beta and recommends a noncritical test graph.

Vendor documentedSource

DB backup format

Obsidian

Not yet verified for this product.

Logseq

DB backup format

A graph directory contains db.sqlite plus assets. A database-only backup does not include the separate assets folder.

Vendor documentedSource 1Source 2
Feature comparison
FeatureObsidianLogseq
Platforms

Devices

Windows, macOS, Linux, iOS and Android apps are documented.

Vendor documentedSource

Devices

Desktop, mobile and browser options exist; DB mobile readiness differs from the OG app.

Vendor documentedSource 1Source 2
Offline use

Offline access

The local vault remains available without a connection; Sync merges changes when connectivity returns.

Vendor documentedSource

Local data

OG uses local file graphs. DB graph directories hold db.sqlite and a separate assets folder.

Vendor documentedSource 1Source 2
Edition distinction

Storage format

Notes are Markdown text in a local folder and can be edited with other text editors.

Vendor documentedSource

Edition distinction

OG supports Markdown and Org-mode. DB graphs use SQLite rather than the same file graph layout.

Vendor documentedSource 1Source 2
Collaboration

Shared vaults

All collaborators need Sync. Shared vaults do not provide live co-editing cursors or fine-grained permissions.

Vendor documentedSource

Collaboration maturity

The current repository describes DB real-time collaboration as alpha. The older file-sync guide explicitly excludes multi-person collaboration.

Vendor documentedSource 1Source 2
Export

Portability

Markdown files are directly accessible. Vault settings and extensions live separately in the .obsidian folder.

Vendor documentedSource

DB export

DB offers SQLite with assets, EDN and standard Markdown exports. Markdown does not preserve every graph property.

Vendor documentedSource
Privacy and storage

Sync privacy

Official Sync documents end-to-end encryption; local-only use does not send notes to Obsidian.

Vendor documentedSource 1Source 2

Not yet verified for this product.

Project portability

Notion migration

API import converts databases and formulas to Bases with limitations. ZIP import does not preserve databases.

Vendor documentedSource

File to DB migration

The importer has documented limits where multiple queries or embeds share one old block.

Vendor documentedSource
Free plan limits

Core app cost

Core use is free without a mandatory account. Sync and Publish are optional services.

Vendor documentedSource

Local app

Open-source local applications are available; hosted sync enrollment is separate.

Vendor documentedSource 1Source 2
Use at work

Use at work

Commercial use is free; the paid commercial license is optional support.

Vendor documentedSource

Not yet verified for this product.

Team limit

Team limit

A shared vault supports at most 20 collaborators according to the current help page.

Vendor documentedSource

Not yet verified for this product.

Linked structure

Not yet verified for this product.

Linked structure

DB nodes combine page and block behavior with properties, tags and linked references.

Vendor documentedSource
Release status

Not yet verified for this product.

Release status

The current main repository labels the database version beta and recommends a noncritical test graph.

Vendor documentedSource
DB backup format

Not yet verified for this product.

DB backup format

A graph directory contains db.sqlite plus assets. A database-only backup does not include the separate assets folder.

Vendor documentedSource 1Source 2

Begin with the Logseq edition

A broad Logseq label hides a major decision. The OG repository describes the file-based application, including Markdown and Org-mode support. The main repository now documents database graphs and labels that edition beta. Its new mobile and real-time collaboration work are described as alpha. This is not a claim that every Logseq installation is unstable; it is a reason to identify the exact product being compared. If you are following an old tutorial, confirm which edition it uses before installing extensions or importing an existing graph.

Source 1Source 2

Compare the unit of work

Obsidian notes are files inside a vault. Logseq DB describes nodes that bring pages and blocks closer together, with properties and linked references. Those structures encourage different habits. For a writer producing finished articles, a document can be a natural unit. For someone recording a daily stream of small connected ideas, individual blocks may be more natural. This is an editorial fit judgment rather than a speed claim. Write the same short research session in each model and see whether the resulting structure still makes sense the next morning.

Source 1Source 2

Local storage does not mean identical portability

Obsidian's text files can be inspected directly with another editor. In Logseq DB, a graph directory contains db.sqlite and a separate assets folder. That does not make the database inaccessible, but it changes the backup and external-editing workflow. Logseq's standard Markdown export does not preserve every property or timestamp. Keep a native backup for restoration and a readable export for access outside the app. Do not assume one format serves both purposes equally well. The right choice depends on what you need to preserve, not simply whether a product advertises local data.

Source 1Source 2Source 3

Check sync and collaboration separately

Official Obsidian Sync is optional and its shared vaults have a different model from a live browser document. Logseq's older file-sync guide explicitly excludes multiple people editing the same graph, while the newer repository describes an alpha collaboration system for DB graphs. Those statements refer to different systems. Current DB documentation lists Sync access for OpenCollective Backers ($5/month) and Sponsors ($15/month). The main README also directs people to an RTC alpha signup. These different access descriptions do not establish the complete enrollment process or a verified checkout price for a particular account. Confirm eligibility and edition before contributing.

Source 1Source 2Source 3Source 4

Treat migration as a structural conversion

Moving between tools can change the meaning of links, properties and embedded content even when the words survive. Logseq's file-to-DB importer documents cases where several queries or embeds in one block do not all transfer. A folder of readable files also does not guarantee that another application understands every special syntax inside them. Choose a sample containing your actual complexity: a query, a reference, an attachment and a repeated daily-note pattern. Inspect the result and keep the source intact. This research has not executed that migration or verified extension compatibility.

Source 1Source 2

A practical decision rule

Choose Obsidian when direct file access is a firm requirement and you want to build around that constraint. Choose Logseq when its structure solves a specific problem well enough to justify learning the edition's current behavior. With the DB beta, use a dedicated noncritical graph first, as the repository itself recommends. Decide what would make you stop the trial before moving a permanent archive. The useful outcome is a system you can keep writing in, back up and leave if necessary. Neither popularity nor an elaborate graph visualization is a substitute for those checks.

Source 1Source 2Source 3

Our take

Obsidian is the simpler fit for a deliberate Markdown-file archive. Logseq can suit linked block workflows, but its OG and DB editions should be evaluated separately. Do not merge their sync, storage or maturity claims.

Common questions

Is Logseq still based on Markdown files?

The OG edition is file-based. The newer DB edition uses SQLite and has different export behavior. Specify the edition.

Is Obsidian open source?

Its core app is proprietary, even though the notes are ordinary files and many community extensions expose their source.

Check the sources

Evidence used for this comparison. A checked date records when we reviewed the source, not a promise that the vendor has made no changes since.

Keep comparing