Logseq

Logseq is a knowledge management and note-taking application built on two commitments that determine everything about it. The first is that your notes are files on your own device, stored as plain Markdown or Org-mode text in a folder you choose. The second is that the fundamental unit of writing is not the page but the block: every bullet point is an addressable object that can be linked, embedded, referenced and queried from anywhere else in your graph. Together these produce a tool that is free, open source, portable, and structurally different from a document-based notes application.

The local-first, plain-file decision has consequences worth spelling out. Your notes are not in a proprietary database held by a vendor, so there is no lock-in, no subscription required to read your own writing, and no risk that a company shutting down takes your archive with it. The files can be opened in any text editor, searched with command-line tools, backed up with any method, and versioned with Git, which is how many Logseq users synchronise between machines for free. The trade-off is that sync is your problem: Logseq offers a paid synchronisation service, and users commonly substitute iCloud, Syncthing, Dropbox or a Git repository, each with caveats around conflict handling on mobile. Because the format is plain text, editing the same file simultaneously from two devices can produce conflicts that a proprietary sync service would resolve silently.

The outliner model shapes how thinking happens in the tool. You write in nested bullets, and the hierarchy itself carries structure: a top-level bullet is a claim or a topic, its children are support, detail and qualification. Blocks can be collapsed and expanded, dragged to reorganise, and, crucially, referenced. A block reference pulls the content of a block into another location, so the same idea can appear in a project page, a daily note and a summary without being duplicated. A block embed does the same for larger chunks. Block-level addressing is what makes an outliner a knowledge tool rather than a list maker, and it is the feature most users cite as the reason they stayed.

Bidirectional linking works through page references. Mentioning a page inside double brackets creates a link, and the target page automatically lists every place that linked to it, including unlinked mentions of the same text. This inverts the usual note-taking model: instead of deciding in advance where a thought belongs and filing it there, you write it where you are and let connections accumulate. Over months this produces a graph in which related material finds itself, and the graph view makes those connections visible, though in practice the graph visualisation is more satisfying to look at than useful for navigation.

Daily notes, or journals, are the default landing surface. Opening Logseq presents today's page, and the assumption is that you capture whatever occurs to you there, tagged and linked, rather than first deciding which page it belongs on. This reduces capture friction to almost nothing, which is the single most important property of a note system that you want to actually use. Weekly and monthly journal views aggregate the period.

Queries are the retrieval mechanism. Simple queries filter blocks by page, tag, property or date, and advanced queries use a datalog-style syntax for more precise conditions, which can pull together, for example, every unfinished task on pages tagged with a project, ordered by due date. Task management is built in through todo markers, due dates, scheduling and recurrence, so Logseq can function as a lightweight task system alongside its notes. Properties are key-value metadata attached to a block or page, which turns a graph of text into something queryable like a database, and this is where more sophisticated users build genuinely useful systems.

PDF annotation is included: you can open a PDF inside Logseq, highlight passages and link each highlight to a block, so reading notes stay attached to their source. Flashcards use spaced repetition for blocks marked for review. A plugin ecosystem adds themes, integrations, visualisations and workflow extensions, and the application is available on macOS, Windows, Linux, iOS and Android, with a browser-based version for evaluation.

The project has been working on a substantial architectural change: a database version that replaces plain files with a structured store, aiming to fix performance on large graphs and to support more precise data handling. This has been in development and beta over a long period, and it creates real uncertainty for a prospective user, because the file-based version and the database version have different characteristics and the migration path matters for anyone with years of notes. Buyers should check the current status before committing.

Against competitors, Roam Research is the original networked note-taking tool and the one Logseq most resembles structurally: daily notes, bidirectional links, block references, an outliner model. Roam is proprietary, paid, hosted only by the vendor, and its development pace has slowed relative to its early momentum, while Logseq is free, open source and local. Obsidian is the largest rival and the most common alternative: also local-first and Markdown-based, but page-centric rather than block-centric, with a far larger plugin ecosystem, a more polished and faster application, and a paid sync and publish service; Obsidian's outliner support exists but is not native to the model. Notion is the mainstream choice, a hosted workspace combining documents, databases, tasks and wikis, with excellent collaboration and sharing and total vendor dependency. Anytype, Tana, Reflect, Mem and Capacities occupy adjacent positions with varying degrees of structure, AI and hosting model. Athens Research was an open-source Roam alternative that ceased active development. Logseq's position is: the strongest open-source, local-first implementation of block-based networked note-taking, with a less polished interface and a smaller ecosystem than Obsidian.

Pricing is free. The application is open source under an open licence, and there is no cost to use it on any platform. Optional paid services cover Logseq's own synchronisation between devices and related hosted features. Users who sync through their own Git repository, iCloud or Syncthing pay nothing at all. There are no seats, no tiers and no enterprise contract, which is a genuine advantage for individuals and a genuine problem for organisations that need support, administration and accountability.

The limitations should be stated plainly. Performance degrades on very large graphs, and users with tens of thousands of blocks report slowness, which is one motivation for the database rewrite. The interface is functional and somewhat austere, with a learning curve that is steeper than Notion's and less immediately rewarding than Obsidian's. Mobile apps have historically been less capable and less stable than desktop. Sync requires setup and can produce conflicts. The block-centric model is powerful but unfamiliar, and people who think in long-form prose pages rather than nested bullets may fight it. Collaboration is weak: this is a personal tool, not a team wiki, and sharing means publishing static output. Plugin availability is smaller than Obsidian's. And the ongoing architectural transition means some investment in workflows today may need revisiting.

Logseq fits researchers and academics building a literature-linked note graph, writers working on long projects with recurring ideas, developers who want plain-text notes under version control, people with strong privacy or data-ownership requirements, anyone who has used Roam and wants the same model without the subscription and vendor dependency, and users who think naturally in outlines. It does not fit teams needing shared collaborative workspaces, people who want a polished interface and a large plugin ecosystem immediately, non-technical users who will struggle with sync setup, organisations requiring support contracts, or anyone whose notes are mostly long-form prose rather than linked fragments.

In the closing comparison, choose Logseq when open source, local files and block-level linking are requirements and you accept a rougher interface. Choose Obsidian when you want the same local-first philosophy with a faster application, a huge plugin ecosystem and better polish, and you are comfortable with a page-centric model. Choose Roam when the original networked model matters more to you than cost and openness. Choose Notion when collaboration, databases and sharing are the point and vendor hosting is acceptable. Choose Tana or Capacities when you want more structured data modelling than an outliner provides. For an individual building a personal knowledge base over years who does not want to rent it, Logseq is one of the two strongest choices available, and the way to decide between it and Obsidian is to spend a week in each writing real notes rather than reading comparisons.