Software Signal
English
Start comparing

Logseq

Linked outlines with distinct file and database editions

Profile reviewed 17 Sept 2026 · Documentation comparison checked on 17 September 2026. Official product pages and help articles were read live. No hands-on app trial or speed benchmark was performed. Recommendations are editorial deductions from the documented workflow and constraints. DB Sync enrollment guidance was rechecked on 26 October 2026. The current DB guide and main README describe access differently. The listed contribution levels are documented evidence, not a verified checkout or successful enrollment.

Compare LogseqVisit official website (opens in a new tab)

Where it fits

Logseq is an open-source knowledge tool, but comparing it now requires identifying which edition you mean. The file-based OG application works with Markdown or Org-mode, while the newer database edition stores graph data in SQLite and changes parts of the workflow. Database graphs add structured properties and a different synchronization architecture. The current repository labels the DB edition beta and its new mobile and collaboration work alpha. That makes Logseq interesting for people who enjoy linked outlines and queries, but a poor choice to adopt blindly from an old feature table. Test one noncritical project before moving a permanent archive.

Consider it for

Know the limits

Prices & plans

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

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

Features and practical details

10 features

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

Platforms

Logseq

Devices

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

Vendor documentedSource 1Source 2

Offline use

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

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

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

Logseq

DB export

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

Vendor documentedSource

Project portability

Logseq

File to DB migration

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

Vendor documentedSource

Free plan limits

Logseq

Local app

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

Vendor documentedSource 1Source 2

Linked structure

Logseq

Linked structure

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

Vendor documentedSource

Release status

Logseq

Release status

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

Vendor documentedSource

DB backup format

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
FeatureLogseq
Platforms

Devices

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

Vendor documentedSource 1Source 2
Offline use

Local data

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

Vendor documentedSource 1Source 2
Edition distinction

Edition distinction

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

Vendor documentedSource 1Source 2
Collaboration

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

DB export

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

Vendor documentedSource
Project portability

File to DB migration

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

Vendor documentedSource
Free plan limits

Local app

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

Vendor documentedSource 1Source 2
Linked structure

Linked structure

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

Vendor documentedSource
Release status

Release status

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

Vendor documentedSource
DB backup format

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

Compare the alternatives

Obsidian vs Logseq: local notes with different structures

Note-taking · 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.

Sources for this profile