Get AI summaries of any video or article — Sign up free
Logseq: Your FREE Second Brain? Honest Review & Rating! thumbnail

Logseq: Your FREE Second Brain? Honest Review & Rating!

Tiago Forte·
5 min read

Based on Tiago Forte's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Logseq’s local-first design stores notes as plain-text files on the user’s device, supporting ownership and privacy.

Briefing

Logseq earns a strong overall score by leaning on a “local-first” model: all notes live as plain-text files on a user’s device, and the system’s power comes from block-level linking, reusable structures, and highly targeted search. The result is a second-brain workflow that feels flexible enough for both casual note-takers and power users—while also prioritizing data ownership and privacy.

Search is one of Logseq’s standout capabilities. It includes a search bar that can match both pages and individual blocks (down to paragraphs), and it supports more advanced “simple queries” built on links and tags—effectively Boolean-style filtering. Examples include showing blocks that contain links A, B, and C while excluding link D. For advanced users, an “Advanced Data script” option adds further depth, though it requires more technical knowledge. The rating for search lands at 7/10 overall, with the caveat that power users may rate it closer to 9 or 10. The main gap: the search experience still needs improvements such as fuzzy matching and synonym handling.

Where Logseq really differentiates itself is reusability and knowledge performance. Notes are block-based, so content can be copied, embedded, and reused across pages and even entire branches of blocks. Crucially, Logseq supports bi-directional linking, letting users see where a block or page is used—turning “write once, reuse everywhere” into a practical system rather than a theoretical feature. Reusability is rated 8/10, with the reviewer staying slightly self-critical.

Access and multi-device use also reflect the product’s philosophy. Logseq is free and open source, and it’s designed so users select a local folder where notes are stored. Sync is possible across devices, including via third-party services like iCloud, Google Drive, Dropbox, and OneDrive, but that introduces trust concerns. To address this, Logseq is building encrypted sync surface so notes and uploaded files are encrypted in the cloud.

Collaboration and sharing perform well because the underlying data format is plain text. Sharing can be as simple as sending the file location or exporting content as HTML. For teams, collaboration uses GitHub and a private repository, with real-time collaboration described as “live” and close to Google Docs—rated around 9.5/10, though not identical.

Ease of use is high for anyone comfortable with outlines: creating blocks, indenting with Tab, and adding Markdown can be learned quickly (within minutes for basic Markdown). Formatting and structuring beyond pages has a learning curve, but the overall ease rating is 9/10.

Long-term growth and upgradeability score even higher (9/10). The workflow naturally evolves from indentation and linking to queries, task management, plugins, and an expanding API—plus integrations such as Hugo for publishing notes to the web.

Data portability is strong but not perfect. Notes can be exported and opened in many tools because they’re plain text, yet advanced features like block references may not transfer cleanly, costing 2 points and resulting in an 8/10.

Organization is rated 9/10 thanks to paragraph-level structure, indentation, and properties (metadata like tags and authors) that can be queried. Capture is 7/10, with mobile limitations—especially around PDF features—called out as a key improvement area. Security is rated 9/10: local-first storage, encryption, and plugin warnings help, though more granular permission settings are still desired.

Across 10 criteria plus a security bonus, the total score reaches 89 points, positioning Logseq as a serious contender for a free second-brain system built around ownership, granular structure, and powerful retrieval.

Cornell Notes

Logseq’s core strength is a local-first second-brain workflow: notes are stored as plain-text files on the user’s device, enabling ownership and privacy while still supporting powerful linking and retrieval. Search stands out with block-level matching and Boolean-style filtering using links and tags, though fuzzy search and synonym support are still needed. Reusability is a major differentiator—blocks and even branches can be embedded and reused, with bi-directional links showing where content is referenced. Collaboration is strong via GitHub-based shared graphs and near real-time editing, while ease of use remains high for anyone familiar with outlines and Markdown. The system scores well on long-term upgradeability and organization, with portability and mobile capture features identified as the main weaknesses.

How does Logseq’s search work, and why does it matter for “second brain” retrieval?

Search can match both pages and individual blocks, down to paragraph-level hits. It also supports “simple queries” that behave like Boolean search using links and tags—for example, retrieving blocks that include links A, B, and C while excluding link D. For more advanced users, “Advanced Data script” adds additional power but requires more technical knowledge. The reviewer rates search 7/10 overall: powerful for power users (possibly 9–10), but the average experience needs improvements like fuzzy search and synonym handling to reduce missed matches.

What makes Logseq’s reusability different from typical note-taking copy/paste?

Logseq is block-based, so content can be copied and reused as blocks, not just whole pages. Users can embed entire branches of blocks (collections of blocks/pages) and then see where the source block or page is used. This bi-directional linking turns reuse into a traceable system: every time a block is reused, Logseq maintains references back to the origin, improving knowledge consistency and maintenance.

How does Logseq handle multi-device access without undermining data ownership?

Logseq stores all data locally on the device by default; users choose a folder where notes live. Multi-device use is possible with sync, including third-party services such as iCloud, Google Drive, Dropbox, and OneDrive. Because some users distrust third-party sync, Logseq is building an encrypted sync surface that encrypts notes and uploaded files in the cloud, aiming to preserve ownership and privacy while still enabling cross-device access.

What tradeoffs appear when moving data out of Logseq?

Portability is strong because notes are plain text and can be opened with many tools. However, advanced Logseq features—especially queries and block/page embeds and block references—may not transfer with full fidelity. For example, a block reference might appear as a hash or paragraph ID rather than the actual content in another tool. That complexity costs 2 points in the portability rating, resulting in 8/10.

How does Logseq support collaboration, and how close is it to real-time editing tools?

Collaboration is described as using GitHub under the hood for shared graphs. Non-technical users may need GitHub Desktop to pull and push changes to a private repository. Real-time collaboration is described as “live,” with a rating around 9.5/10—close to Google Docs but not identical, reflecting remaining differences in collaborative behavior and polish.

Where does Logseq fall short for capturing content, especially on mobile?

Capture is rated 7/10. Desktop supports richer features like a built-in PDF reader with highlighting, plus YouTube timestamp capture via keyboard shortcuts. But mobile limitations are called out: opening PDFs on mobile triggers the device’s PDF reader/editor rather than Logseq’s full PDF feature set. The reviewer flags mobile as the key area needing improvement so captured content can be used consistently across devices.

Review Questions

  1. Which Logseq search capabilities depend on links and tags, and what’s the practical impact of missing fuzzy/synonym search?
  2. Why does bi-directional linking make reusability more maintainable than simple copying?
  3. What specific advanced features create friction when exporting or using Logseq data in other tools?

Key Points

  1. 1

    Logseq’s local-first design stores notes as plain-text files on the user’s device, supporting ownership and privacy.

  2. 2

    Search can target individual blocks/paragraphs and uses Boolean-style filtering via links and tags, but lacks fuzzy/synonym support for smoother matching.

  3. 3

    Block-based reusability lets users embed single blocks or entire branches while bi-directional links reveal where content is used.

  4. 4

    Encrypted sync surface is intended to reduce trust concerns from third-party sync services like iCloud, Google Drive, Dropbox, and OneDrive.

  5. 5

    Collaboration relies on GitHub-based shared graphs, with real-time editing described as close to Google Docs but not identical.

  6. 6

    Portability is strong for plain text, yet advanced block references and embeds may not render as intended outside Logseq.

  7. 7

    Mobile capture—especially PDF features—lags behind desktop, lowering the capture score despite strong desktop capabilities.

Highlights

Block-level search reaches down to individual paragraphs, and “simple queries” behave like Boolean search using links and tags.
Reusability is built into the structure: embedded blocks and branches keep traceability through bi-directional linking.
Encrypted sync surface is positioned as the answer to third-party sync trust concerns.
Collaboration uses GitHub and shared graphs, with real-time editing rated around 9.5/10—near Google Docs territory.
Portability is limited mainly by advanced features like block references, which may appear as IDs/hashes in other tools.

Topics