Second brain apps compared for someone who reads a lot
We may earn a commission if you buy through these links — at no cost to you.
Heavy readers have a specific failure mode, and it is not note-taking. It is that highlights accumulate in five places, none of which is the place you write. The app you need is decided by where your highlights come from, not by which tool has the nicest graph view.
The three approaches compared:
| Option | What it is | Best for | The costs / trade-off |
|---|---|---|---|
| Local-first, plain files | Markdown files in a folder you own, with an app on top for links and search | People who will still be using it in five years and want the files to outlive the vendor | You build the system; every plugin is a decision and the tinkering can substitute for reading |
| All-in-one database | Blocks, databases and views, hosted and collaborative | People whose reading feeds shared projects rather than private thinking | Your notes are rows in someone’s database; export is lossy in practice; slower to open |
| Read-it-later plus highlights | The queue and the highlighter as one product, notes app downstream | Someone reading a lot of long web pieces and newsletters | Subscription, and another silo unless its export into your notes tool is genuinely automatic |
First, sort yourself into one of three readers
The Kindle reader. Highlights live in Amazon’s system and need syncing out. Any tool you pick must have a working import path, and the reliable ones charge for it.
The papers reader. PDFs, DOIs, citations. Your requirements are a reference manager’s, not a notes app’s, and the two categories only partly overlap.
The web reader. Articles, newsletters, threads. You need a read-later queue with a highlighter attached, and the queue is where the value is.
Buying the wrong category is the mistake. A beautiful notes app will not fix a missing Kindle import.
The local-first, plain-files option
Markdown files in a folder you own, with an app on top for links and search. No lock-in, works offline, still readable in ten years, and free at the core with paid sync.
Costs: you build the system. Every plugin is a decision, and the tinkering is genuinely addictive in a way that substitutes for reading.
Best for: people who will still be using this in five years and want the files to outlive the vendor.
The all-in-one database option
Blocks, databases, and views, hosted, collaborative, excellent for structure.
Costs: your notes are rows in someone’s database, export is lossy in practice, and it is slower to open than a text file, which matters when the whole point is capturing a thought before it evaporates.
Best for: people whose reading feeds shared projects rather than private thinking.
The read-it-later plus highlights option
The queue and the highlighter as one product, with the notes app downstream. For someone reading a lot of long web pieces and newsletters, this is the category that actually reduces the mess, because it captures at the point of reading.
Costs: subscription, and it is another silo unless its export into your notes tool is genuinely automatic. Test that on the trial, on day one, before the queue fills up.
The five questions that decide it
- Where do 80% of my highlights originate? Buy for that source.
- Does it import Kindle highlights without me copying anything?
- Can I export everything to plain text in one action, today, on the trial?
- How many seconds from thought to captured note on my phone? Over five and you will stop.
- Is search fast on ten thousand notes, not on the fifty in the demo?
Frequently asked questions
What is the best second brain app for heavy readers?
It depends on where 80% of your highlights originate. Kindle readers need an app with reliable import. Paper readers need a reference manager. Web readers need a read-later queue with a highlighter. The category you pick matters more than which specific tool.
Can I use markdown files as a second brain?
Yes. Plain files in a folder you own work offline, outlive any vendor, and are free. The trade is you build the system. Every plugin is a decision, and the tinkering can substitute for reading.
Is Obsidian or Notion better for note-taking?
Different approaches. Obsidian is local-first, fast to open, and your files outlive the vendor. Notion is hosted, collaborative, and excellent for structure. Obsidian is better for private thinking; Notion is better for shared projects.
Should my read-it-later app also be my notes app?
Not necessarily. The queue and the highlighter are one product; the notes tool is downstream. What matters is whether the export from the queue into your notes tool is automatic. Test that on day one of the trial, before the queue fills up.
What is the most important feature in a second brain app?
Speed from thought to captured note. Over five seconds on your phone and you will stop capturing. The second most important is fast search on ten thousand notes, not on the fifty in the demo. Everything else is decoration.
What no app fixes
Capturing is not reading and organising is not thinking. The measurable output of a second brain is what you write from it. If nothing has come out in a month, the tool is not the problem, and a simpler tool is more likely to be the fix than a richer one.
Pair whichever you pick with a deliberate weekly review, and with a reading setup that does not fight you: our guide on e-ink tablets for papers covers the capture end of the same workflow.