Before choosing a note-taking system, compare where your notes are stored, what works offline, how notes connect and what you can share or take with you. This reference covers 14 tool families and 15 product versions or configurations. Logseq OG and the newer Logseq database app are listed separately because their storage and capabilities differ.
Use this table to compare how the systems work, not to find an overall winner. It covers documented storage, note structure, links, export and collaboration; check current pricing, privacy and security separately.
How to read the fields
- Primary data location: the documented working source of truth, not an export or a sync copy.
- Local operation model: whether the native model works locally, offline-first, through selected offline content, or primarily through a hosted workspace.
- Primary content model: what you mainly create and organise, such as pages, blocks, objects, cards or decks.
- Native relationship model: documented built-in ways of connecting or containing information.
- Export and access outside the app: what you can keep or export, and how you can use it elsewhere. Export is not a promise of lossless migration.
- Collaboration model: whether people work in a shared workspace, use an optional sharing service, or mainly keep notes locally.
- Service and deployment dependency: whether everyday use depends on the vendor’s service, and whether the reviewed documentation describes a self-hosted option.
Scroll the table horizontally to compare every field.
| Tool | Primary data location | Local operation model | Primary content model | Native relationship model | Export and access outside the app | Collaboration model | Service and deployment dependency |
|---|---|---|---|---|---|---|---|
| Notion | Vendor-hosted workspace | Hosted workspace with downloaded-page offline use | Pages and databases | Page hierarchy and links | Hosted model; documented HTML, Markdown and CSV export | Hosted collaboration is central | Vendor service is central; no official self-hosting path identified in reviewed documentation |
| Craft | Vendor-hosted documents | Unclear from reviewed official documentation | Documents | Document hierarchy | Hosted model; documented document export | Official sharing and collaboration option | Vendor service is central; no official self-hosting path identified in reviewed documentation |
| Evernote | Vendor-hosted notebooks | Hosted-primary account model | Notes in notebooks | Notebook containment | Hosted model; documented ENEX or HTML export | Official notebook-sharing option | Vendor service is central; no official self-hosting path identified in reviewed documentation |
| Obsidian | Local Markdown files | Local native operation | Markdown files and notes | Folders plus note links/backlinks | Readable local files; files remain usable outside the app | Official shared-vault collaboration option | Core local work needs no vendor service; no official self-hosting path identified in reviewed documentation |
| Logseq OG | Local Markdown file graph | Local native file-graph operation | Blocks and graph pages | Page links and block references | Working notes are ordinary Markdown files; back up and test any migration | Local-file workflow; do not assume database RTC collaboration applies | Core file work does not require a vendor service; OG receives maintenance but no new features |
| Logseq (database) | Local SQLite database graph, not ordinary Markdown source files | Local native database operation; beta | Blocks and graph pages with properties | Page links, block references and structured properties | SQLite and EDN export; standard Markdown export omits some graph data | RTC collaboration is alpha and access may be limited | Core graph is local; check optional Sync and service access. Migration from OG is not required |
| Joplin | Local app-managed note collection | Offline-first local operation | Notes in notebooks | Notebook containment | App-managed data; documented export/import path | Official sharing option through Joplin Cloud | Vendor service is optional; official self-hosted server path documented |
| Roam Research | Vendor-hosted graph | Hosted-primary graph model | Nested blocks | Page links and block references | Hosted graph model; documented graph export | Hosted collaboration is central | Vendor service is central; no official self-hosting path identified in reviewed documentation |
| Workflowy | Vendor-hosted account document | Hosted-primary account model | One nested outline | Outline hierarchy | Hosted model; documented text, Markdown and OPML export | Official node-level sharing option | Vendor service is central; no official self-hosting path identified in reviewed documentation |
| Tana | Vendor-hosted workspace | Hosted-primary workspace model | Nodes and nested outline | References plus fields | Hosted model; documented Markdown/JSON export with an asset caveat | Hosted collaboration is central | Vendor service is central; no official self-hosting path identified in reviewed documentation |
| Capacities | Unclear from reviewed official documentation | Unclear from reviewed official documentation | Typed objects and content types | Object properties and relations | Hosted object model; documented export | Official sharing option | Vendor service is central; no official self-hosting path identified in reviewed documentation |
| Anytype | Local-first, peer-synced data | Offline-first local operation | Typed objects | Object relations and properties | Networked local data; documented data export | Official shared-space and peer collaboration path | Core local work needs no vendor service; official self-hosting path documented |
| Heptabase | Unclear from reviewed official documentation | Unclear from reviewed official documentation | Cards and visual whiteboards | Spatial card/whiteboard relationships | Unclear from reviewed official documentation | Unclear from reviewed official documentation | Unclear from reviewed official documentation |
| RemNote | Hosted knowledge base with documented local knowledge-base scope | Hosted knowledge base with documented offline use | Outlined notes with native flashcards | Hierarchy plus linked ideas | Hosted model; documented export with native-media caveat | Official sharing and collaboration option | Vendor service is central; no official self-hosting path identified in reviewed documentation |
| Anki | Local app-managed collection | Local native operation | Flashcards and decks | Deck and collection structure | App-managed collection; documented package and text export | Local, single-user primary model | Core local work needs no vendor service; no official self-hosting path identified in reviewed documentation |
What the table can and cannot tell you
A folder of readable files, data managed by a local app and a hosted workspace give you different ways to keep and recover your notes. The same applies to note structures: a block, a typed object and a flashcard do different jobs. Use the table to identify the requirement you need to check in a particular app.
“Unclear from reviewed official documentation” is deliberately not a product negative. It means the official documentation reviewed did not provide enough detail to make a reliable claim. Likewise, “no official self-hosting path identified in reviewed documentation” describes the reviewed documentation scope; it does not say self-hosting is impossible.
Seven checks before choosing a note-taking system
See how seven structural fields reveal what to verify in a note-taking system without turning the reference into a ranking.
Official source notes
These links lead to official documentation for the features compared above. Check the vendor’s latest information before relying on a particular feature.
- Notion: backup and data location; export your content; offline pages; sharing and permissions.
- Craft: export options; official sharing and export documentation.
- Evernote: export notes and notebooks; share a notebook.
- Obsidian: data storage; sync notes across devices; Syncing for teams.
- Logseq OG and Logseq (database): official product split and OG maintenance plan; database beta and RTC alpha status; database graph and export details.
- Joplin: offline-first sync architecture; sync targets; Joplin Cloud and Server Business.
- Roam Research: blocks and references; graph export; current in-product help.
- Workflowy: getting started; sharing, collaboration and export; apps and devices.
- Tana: knowledge graph concepts; relationships in a workspace; copy, paste and export; collaboration and sharing.
- Capacities: content types; export documentation.
- Anytype: official FAQ; objects documentation; local-first, peer sync and Business deployment scope.
- Heptabase: official product model; current support documentation.
- RemNote: flashcard basics; exporting notes; current help centre.
- Anki: official manual; exporting; syncing.
What this comparison covers
This comparison draws on official product documentation. It highlights practical differences in how tools store, organise, connect and share notes; it is not a hands-on test, a security assessment or a list of every note-taking app.
Last reviewed: 9 September 2026. Product capabilities can change. Check the linked documentation for current storage, offline access, export and collaboration details before making a long-term choice.
Choose the next question
The PKM Tool Decision Map helps you compare different ways to work with notes and ideas; this table lets you check practical requirements across tools. If the key question is where the primary working copy should live, compare local-first and cloud note-taking. If it is about the job of a folder, tag/property or link, read folders, tags and backlinks. To compare four note-taking tools against your own priorities, continue to the Note-taking Apps Picker.