What Is a Second Brain App and How Do You Choose One?
Updated
A second brain app is software that keeps your notes, ideas, and research in one searchable, linkable personal knowledge base, so you can find and reuse what you've already learned instead of losing it across scattered documents. It suits anyone who reads, researches, or writes regularly and wants their accumulated material to compound over time. It is not a task manager or a team wiki, and it won't organize itself — the tool only works as well as the habits you build around it.
What a second brain app actually does
The core job is capture, connect, and retrieve. You put material in (notes, quotes, meeting thoughts, article excerpts), you link related notes to each other, and later you search or browse those connections to resurface ideas.
Three features do most of that work:
- Markdown and plain-text storage. Notes stay readable and portable. If the app disappears, your files don't.
- Wiki links and backlinks. Typing a link to another note creates a two-way connection, so a note shows what references it. This is how a flat pile of notes becomes a network.
- Graph view. A visual map of how notes connect, useful for spotting clusters and gaps rather than for daily navigation.
Some tools go further. Lokus, for example, describes itself as a "personal knowledge OS" for macOS, Windows, and Linux, combining Markdown, wiki links, graph view, and an infinite canvas — the canvas being a free-form space for arranging notes spatially rather than in a list.
Second brain app vs. note-taking app vs. PKM vs. Knowledge OS
These terms overlap heavily, and vendors use them loosely. The practical differences:
| Term | Typical scope | What distinguishes it |
|---|---|---|
| Note-taking app | Capture and store notes | May be list- or folder-based; linking optional |
| Second brain app | Personal knowledge base you build over time | Emphasis on retrieval and reuse, not just storage |
| PKM app | Tooling for personal knowledge management | Broad category; includes second brain apps |
| Knowledge OS | A PKM tool positioned as a full workspace | Often adds canvas, plugins, or multi-view workflows |
In practice, a modern note-taking app with backlinks is a second brain app. The label matters less than whether the features you need are present. If a tool stores notes in a locked format with no export, it will struggle to serve as a long-term second brain regardless of what it's called.
How to choose one: the decision points that matter
Judge candidates on the same dimensions, in roughly this order:
- Data ownership and export. Can you get your notes out as plain Markdown or text? Lokus states "Your data, your control" as a principle; verify this for any tool by checking its export options before committing.
- Linking model. Wiki links plus backlinks are the minimum. Without backlinks, links are one-directional and you lose the "what points here?" view.
- Platform support. If you work across devices, confirm native support for each OS you use. Lokus lists macOS, Windows, and Linux.
- Views beyond lists. Graph view helps with review; an infinite canvas helps if you think spatially. Neither is essential on day one.
- Cost and sustainability. Check the pricing page directly rather than assuming. Lokus links to Open Collective contribution tiers (for example, a $5/month "Knowledge Seeker" and a $15/month "Archivist" option) — treat these as support tiers whose exact entitlements you should confirm on the site, not as a confirmed free-or-paid verdict.
- Extensibility. Plugins and a changelog signal active development; a public roadmap or GitHub discussions signal a responsive maintainer.
A quick test: import ten of your real notes into two candidates, link them, and try to find a specific idea a week later. Whichever tool makes that retrieval feel natural is the better fit — feature lists rarely predict this.
Starting from zero without overbuilding
The most common failure is designing an elaborate folder hierarchy before you have any notes. A simpler sequence:
- Pick one or two input sources. For example, a daily note for stray thoughts and a single "inbox" note for clipped material.
- Create a handful of topic notes — five to ten areas you actually think about, not a taxonomy of everything.
- Link instead of filing. When a new note relates to a topic, link it. Let structure emerge from links rather than pre-built folders.
- Review weekly. Open the graph or your backlinks and move inbox items into linked notes. This review step is what separates a second brain from an archive.
- Verify retrieval. Once a month, search for something you wrote weeks ago. If you can't find it, your linking is too sparse.
Why second brains stall
- Collecting without processing. Saved articles that are never linked or summarized add noise. Cap your inbox and clear it on a schedule.
- Switching tools too often. Every migration costs links and momentum. Choose on exportability and linking first, then stay put for a few months.
- Over-engineered structure. Deep folder trees and dozens of tags create maintenance work with little retrieval benefit. Fewer topics, more links.
- Treating the graph as the goal. The graph is a diagnostic view; the notes and their connections are the product.
If you're evaluating Lokus specifically, start with its documentation and quick-start guide, confirm the export format and platform builds, and check the contribution tiers on the linked checkout pages before deciding whether the model fits how you want to support a tool. For any alternative, apply the same six checks above — the comparison holds regardless of vendor.