Why Plain-Text Notes Outlive Every Notes App

Every notes app promises to remember everything. Then it gets acquired, pivots to AI, sunsets the free tier, or just slowly rots — and your notes turn out to have been rows in someone else’s database all along. Plain-text notes survive this cycle for a boring reason: nothing has to agree to keep working. A text editor from 1996 opens a file from 2026.

The ten-year test

Ask of any notes system: with no account, no subscription, and no app installed, can I read everything? Cloud apps fail at “no account.” Proprietary desktop apps fail at “no app installed.” A folder of Markdown files passes all three, on hardware that doesn’t exist yet, with software nobody has written yet — because plain text is the one format the whole industry accidentally standardized on.

What “folder as database” actually means

It doesn’t mean giving up structure. It means the structure lives in open formats next to the content:

• One file per note (cards/*.md), with a small frontmatter header — id, title, dates, tags — and Markdown below. Any editor reads it; grep searches it; Git versions it.
• Layout as data, not decoration. In Toxvas, a board is a JSON file describing positions, connectors, and section frames. The canvas you see is a view over files, not a place files go to disappear into.
• A spec, written down. Our workspaces ship a TOXVAS_SPEC.md that documents the format in the folder itself — card schema, board schema, sync rules (last-writer-wins by file mtime). Future software, including software we haven’t written, can read the folder without asking us anything.

That last point is the one most “export” features miss. An export is a snapshot you have to remember to take. A documented folder is a database that happens to be legible.

What you give up (honestly)

Full-text search across ten thousand files is slower than a purpose-built index — though a local FTS5 index over the folder closes most of that gap. Real-time collaboration needs a server somewhere, full stop; plain text gives you Git-grade merging, not Google-Docs cursors. And a folder won’t remind you of anything — no notifications, no “smart” resurfacing. If those are the job, pick the tool built for the job (see our Mac roundup) and keep the archive in text anyway.

Agents want files too

A side effect we didn’t plan for: AI agents are dramatically better with folders than with APIs. No keys, no rate limits, no schema negotiation — an agent with shell access can read and write Markdown directly, and the canvas follows within seconds. The same property that frees you from vendors frees your tools from integration work. Your notes become the API.

Start in five minutes

1. Make a folder. Call it notes.
2. Write one file per thought, in Markdown, named whatever you like.
3. Put the folder in Git (or don’t — the files are already the backup of every app that can read text).
4. Point any plain-text tool at it — including, if you want the canvas view, Toxvas’s free trial. The folder stays yours either way.

Apps will keep promising to remember everything. Believe the folder instead.