Logseq
Linked outlines with distinct file and database editions
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
- Linked outlines
- Journal-based research
- People willing to evaluate evolving workflows
Know the limits
- OG and DB editions have different storage models
- DB and collaboration maturity need attention
- Current paid sync price was not independently resolved
Prices & plans
Published prices keep their original currency and billing terms. Taxes, promotions and checkout prices can differ.
Features and practical details
10 features
Documented differences. An unverified answer means we do not have enough evidence.
Platforms
Offline use
Edition distinction
Collaboration
Export
Logseq
DB offers SQLite with assets, EDN and standard Markdown exports. Markdown does not preserve every graph property.
Vendor documentedSource
Project portability
Logseq
The importer has documented limits where multiple queries or embeds share one old block.
Vendor documentedSource
Free plan limits
Linked structure
Logseq
DB nodes combine page and block behavior with properties, tags and linked references.
Vendor documentedSource
Release status
Logseq
The current main repository labels the database version beta and recommends a noncritical test graph.
Vendor documentedSource
DB backup format
| Feature | Logseq |
|---|---|
| Platforms | Desktop, mobile and browser options exist; DB mobile readiness differs from the OG app. |
| Offline use | OG uses local file graphs. DB graph directories hold db.sqlite and a separate assets folder. |
| Edition distinction | OG supports Markdown and Org-mode. DB graphs use SQLite rather than the same file graph layout. |
| Collaboration | The current repository describes DB real-time collaboration as alpha. The older file-sync guide explicitly excludes multi-person collaboration. |
| Export | DB offers SQLite with assets, EDN and standard Markdown exports. Markdown does not preserve every graph property. Vendor documentedSource |
| Project portability | The importer has documented limits where multiple queries or embeds share one old block. Vendor documentedSource |
| Free plan limits | Open-source local applications are available; hosted sync enrollment is separate. |
| Linked structure | DB nodes combine page and block behavior with properties, tags and linked references. Vendor documentedSource |
| Release status | The current main repository labels the database version beta and recommends a noncritical test graph. Vendor documentedSource |
| DB backup format | A graph directory contains db.sqlite plus assets. A database-only backup does not include the separate assets folder. |
Compare the alternatives
Sources for this profile
- Logseq DB documentation (opens in a new tab)
github.com · Document describes functionality as of 28 April 2026. Live read on 17 September.
- Logseq main repository (opens in a new tab)
github.com · Current README describes DB beta and mobile/RTC alpha.
- File-based Logseq Sync guide (opens in a new tab)
blog.logseq.com · Published 31 August 2024. Its price and collaboration details are explicitly scoped to the older file-sync beta.