Building a Second Brain in Plain Text

A second brain is an external store of your knowledge that you can trust, search, and reuse. It holds the notes, ideas, references, and decisions you'd otherwise forget, in a place outside your head that you actually return to. The most durable way to build a second brain is also the plainest: Markdown text files in a folder you own. They are portable, searchable, readable by both humans and AI, and they don't depend on any single app staying alive.

This post explains the idea, credits where it comes from, and shows a starter structure you can set up today. It also stays honest about what dedicated apps add on top of plain files.

What is a second brain?

The term was popularized by Tiago Forte, whose book Building a Second Brain frames it as a system for capturing what resonates and organizing it so your past thinking is available when you need it. Forte's method is often summarized by PARA: four top-level buckets for Projects (active efforts with a deadline), Areas (ongoing responsibilities), Resources (topics and references), and Archive (anything inactive).

At its core, a second brain is a simple promise: when you have a thought worth keeping, you put it somewhere reliable, and later you can find it again. The value isn't in any one note. It's in the accumulation, and in trusting the store enough to offload your memory to it.

That trust is the catch. A second brain only works if you believe it will still be there, still readable, and still searchable years from now. Which is exactly where the file format matters more than most people expect.

Why plain text for a second brain?

Most knowledge tools store your notes in a database or a proprietary format you can't open without that specific app. That's fine until the app shuts down, changes its pricing, drops a feature you relied on, or locks your export behind a paywall. Your second brain is supposed to outlast all of that, and a format that depends on one company's survival is a fragile foundation.

Plain Markdown files solve this directly. A Markdown note is just text with light, readable markup: # for headings, **bold**, - for lists, | for tables. Any text editor on any major operating system can open it, and that has been true for decades. There is no lock-in, because the file itself is the note, with nothing wrapped around it that you'd need a specific program to unpack.

Here's how plain text compares to the usual alternatives for a knowledge store:

Property	Plain Markdown files	Proprietary app database	Cloud-only docs
You own the source files	Yes	No	Usually not
Readable without the app	Yes, any text editor	No	No
Survives the app shutting down	Yes	No	No
Full-text search across everything	Yes, any tool	App-dependent	App-dependent
Works with AI tools and scripts	Directly	Needs export	Needs export
Plays well with version control (Git)	Yes	Rarely	No

The pattern across that table: plain text removes single points of failure. For a deeper version of this argument, see why plain Markdown files.

Why does plain text matter in the AI era?

A second brain used to be read by exactly one person: you. Now it's also read by machines. Large language models and AI assistants consume text, so when your notes are plain Markdown, you can drop a file (or a whole folder) into an AI tool and ask it to summarize, connect, or draft from your own material. No export step, no format conversion, no scraping a database.

Markdown is one of the formats these tools handle most naturally. They emit it, they parse it cleanly, and its structure (headings, lists, tables) gives a model the same hierarchy a human reads. Models work with plenty of plain prose, JSON, and code too, but Markdown is both human-readable and machine-friendly at once. If you keep your knowledge in a closed app, you're one missing export button away from your AI workflow breaking. If you keep it in files, the tool reads the folder as it stands.

The files stay yours, plain text outlasts the apps that read it, and AI is one more reader that works with the same material. More on that in Markdown as AI context.

How do you structure a plain-text second brain?

Start small. A second brain doesn't need a perfect taxonomy on day one; it needs a folder you'll actually use. Here's a starter layout based loosely on PARA, simplified so you can begin in five minutes:

• inbox/: everything new lands here first, unsorted, as one file or a few quick-capture notes. The point is to never lose a thought because you didn't know where to file it.
• projects/: one folder or file per active project with a real end date, such as projects/website-redesign.md or projects/q3-report.md.
• areas/: ongoing responsibilities with no end date, like areas/health.md, areas/finances.md, or areas/team-1on1s.md.
• resources/: reference material and topics you're learning, such as resources/typescript.md or resources/coffee-brewing.md.
• archive/: finished or dormant material. Don't delete it; move it here, and search still reaches it.

A few habits that keep it healthy:

1. Capture to the inbox without thinking. Sorting is a separate, later step. Friction at capture time is what kills note systems.
2. Use the filename as the title. Descriptive names make files findable in any tool, and they double as the note's title.
3. Link between notes with relative links so related ideas connect: [brewing notes](../resources/coffee-brewing.md).
4. Review weekly. Empty the inbox into the right folders. Move finished projects to the archive. Ten minutes is enough.
5. Keep one note per idea. Many small files beat a few giant ones. They're easier to link, search, and feed to an AI tool.

The layout matters less than the habit. Pick names you'll recognize in six months, and adjust the structure as your collection grows.

What about syncing and search?

Two reasonable worries: how do these files follow me across devices, and how do I search them once there are hundreds?

Syncing is solved by the folder. Because your second brain is just files, you can drop the folder into iCloud, Dropbox, OneDrive, Syncthing, or a Git repository and it syncs like anything else. You're not waiting on a notes app to build sync; you're using infrastructure that already runs on your machine. One trade-off to be honest about: file-sync tools can produce conflict copies if you edit the same note on two devices at once. In practice this is rare and easy to resolve, but it's a real difference from a database app that merges edits for you.

Search is solved by the format. Plain text is about as easy to search as anything on a computer: every operating system's search, every editor's find, command-line tools like grep and ripgrep, and AI tools all read it natively. There's no index to corrupt and no app that has to be open.

What do dedicated apps add, honestly?

Plain files are the foundation, not the whole house. It's fair to name what purpose-built knowledge apps give you that a bare folder doesn't:

• Backlinks and graph views that show how notes connect without you maintaining the links by hand.
• Live preview so your Markdown renders headings, tables, and diagrams as you type instead of showing raw # and |.
• Fast fuzzy search and quick-switch tuned for large note collections.
• Plugins and templates for spaced repetition, daily notes, task tracking, and the like.

The important question isn't "files or an app?" It's whether the app keeps your notes as plain files underneath. The good ones do. They give you backlinks, live preview, and fast fuzzy search over a folder of .md files, so you gain those conveniences today without giving up portability tomorrow. If the app disappears, your second brain doesn't. For comparisons, see best local-first Markdown apps.

The takeaway

A second brain is only as trustworthy as the format it's built on. Apps come and go; plain text stays readable as long as text editors exist. By keeping your notes as Markdown files in a folder you own, you get a knowledge store that's portable across every device, searchable with any tool, readable by both you and AI models, and independent of any company's roadmap. Start with five folders and an inbox. Add an app later when you want backlinks and live preview.

Noteline is one way to do this: a live-preview Markdown editor that keeps every note as a plain .md file in a folder you choose, with offline Word and PDF export and no account required. But the real point holds no matter which tool you pick. Build your second brain in plain text, and it stays yours for as long as the files do.