Why your notes should be plain Markdown files
Plain Markdown files outlast the apps that open them. Here is what that buys you — portability, real backups, and no lock-in — and the honest trade-offs.
A note you can open in any text editor, on any computer, in ten years, is worth more than a note trapped in an app. That is the whole argument for keeping your notes as plain Markdown files: the file is the thing you own, and it will outlive whatever software you use to edit it today.
Most note apps store your writing in a database or a proprietary format. It feels the same while the app is alive. The difference only shows up at the worst possible moment — when the app shuts down, raises its price, changes its sync, or simply stops being the tool you want. Plain files never have that moment.
What does "plain Markdown files" actually mean?
It means each note is an ordinary .md text file sitting in a folder on your disk. Markdown is just text with a few light conventions: # for headings, - for lists, **bold**, [links](https://example.com). Open the file in Notepad, TextEdit, VS Code, or your phone, and you can read every word without the original app installed.
Two properties make this powerful:
- It is plain text. No binary blob, no database to corrupt, no export step. The content is right there.
- It is structured enough. Markdown carries headings, lists, tables, and code without locking you into one renderer. The same file looks right in a hundred tools.
That combination — human-readable and machine-friendly — is why Markdown has quietly become the default for notes, documentation, and the answers your AI assistant gives you.
Why does the file format matter so much?
Because the format decides who is in control. When your notes are files in your folder, the answers to every important question are boring, which is exactly what you want:
| Question | Plain .md files |
App database / proprietary format |
|---|---|---|
| Open without the app? | Yes, any text editor | No, or "export" only |
| Sync with iCloud/Dropbox/Git? | Yes, it's just files | Only the app's own sync |
| Back up? | Copy the folder | Trust the vendor |
| Search outside the app? | Spotlight, grep, ripgrep |
The app's search only |
| Survive the app shutting down? | Yes | Maybe, if export still works |
| Feed to scripts or AI? | Pipe the text | Export, then hope |
None of this matters on a normal Tuesday. All of it matters the day you want to leave, migrate, or just make sure your decade of notes is safe.
What you lose when notes aren't files
Call it the lock-in tax. You don't pay it up front. You pay it later, with interest:
- Migration pain. Moving thousands of notes out of a proprietary app means an export that flattens formatting, breaks links, and loses metadata. Files just move.
- Backup blind spots. If only the app can read your notes, your "backup" is really a bet on the vendor's servers and business model.
- No interoperability. You can't easily run your own search, sync with Git, or pipe a note into another tool when the data lives behind an API.
- Format risk. Proprietary formats are only guaranteed to be readable by software that is still maintained. Plain text has been readable since the 1960s and will be for the rest of your life.
This is why the local-first movement treats the file, not the app, as the unit of ownership. The app is a lens; the files are the library.
"But isn't a database more powerful?"
Sometimes, yes — and it's worth being honest about it. Apps like Notion build real value on top of a database: relational tables, shared workspaces, permissions, dashboards. If your work is fundamentally a database — a CRM, a project tracker, a team wiki with fine-grained access — a plain folder of files is the wrong tool.
But most note-taking isn't that. It's thinking, drafting, journaling, capturing, and turning rough ideas into documents. For that, a database is a heavy answer to a light question. You trade ownership and portability for features you rarely use, and you inherit the lock-in for free.
A good rule of thumb: if the relationships between records are the point, use a database. If the writing is the point, use files.
How plain files actually work, day to day
The fear is that "just files" means giving up modern conveniences. It doesn't. Because the notes are ordinary files, you can layer on exactly the tools you already trust:
- Sync by putting the folder in iCloud Drive, Dropbox, OneDrive, or Syncthing. Every device sees the same files. No app-specific sync to pay for or wait on.
- Version history with Git, if you want it — every edit, forever, diff-able.
- Backup by copying the folder anywhere. Time Machine and any cloud backup already cover it.
- Search with your OS search, or
grep/ripgrep for instant full-text across thousands of notes. - AI and automation by piping the raw text into any tool. Plain Markdown is the format models read and write natively, so there's no conversion friction.
You get a fast, focused editor on top, and an open folder underneath. Nothing is hidden from you.
What to look for in a plain-text note app
If you're sold on the idea, the editor still matters — a folder of files with a clumsy editor is no fun. Look for:
- Real files, real folders. The app should read and write the
.mdfiles directly, not import them into a hidden store. You should be able to edit a note in another app and have it just appear. - A clean writing surface. Live preview so
**bold**looks bold, tables render, code blocks are readable — without hiding the fact that it's still Markdown underneath. - Honest export. When you need a Word doc or a PDF, you want a faithful conversion, ideally one that works offline, not a print-to-PDF screenshot.
- No required account. Local-first means it should work with no sign-in and no cloud dependency. Sync is something you add, not something you're forced into.
- A price that respects ownership. If your notes are files you own, paying rent forever to read them is a contradiction. A one-time purchase fits the philosophy better than a subscription.
This is the bar we set for Noteline: your notes are plain .md files in a folder you choose, the editor stays out of the way, and Word/PDF export runs offline. You can open the web editor without installing anything, or keep everything local on the desktop.
The one-sentence version
Apps are temporary; files are forever. Keep your notes as plain Markdown files and you keep the one thing that actually matters — the words — no matter what happens to the software around them.
If you want to see the other half of this story, read how to turn ChatGPT and Claude answers into clean Word and PDF documents — the export side of owning your text.