Open a note you wrote in some app fifteen years ago. If it opens at all, half its formatting is probably broken. Now open a plain-text file from the same era. It reads exactly as written. That gap is the whole case for Markdown: it's the format most likely to still be readable when the app you wrote it in is long gone.
What Markdown actually is
Markdown is plain text with a handful of lightweight conventions for formatting. # Heading, **bold**, - list item, [link](url). That's most of it. The syntax stays readable as text (you don't need the app to render it to understand it), which is the quiet trick that makes everything else work.
Because it's just text, a Markdown note is a .md file you can open in any editor on any operating system, today or in twenty years. No proprietary database, no export step, no format that only one company understands.
Why it lasts
The durability isn't nostalgia. It's structural. Plain text is the lowest common denominator every tool agrees on.
| Property | What it means for your notes |
|---|---|
| Portable | Move between apps freely; the file is the note, not a row in someone's cloud |
| Future-proof | Text has been readable for 60 years and isn't going anywhere |
| Tool-independent | Not hostage to one app's survival, pricing, or acquisition |
| Diff-able & versionable | Works with Git, syncs cleanly, shows exactly what changed |
| Fast & light | A folder of .md files loads instantly; no bloat, no lock-in |
This is also why Markdown pairs so naturally with a linked-notes practice. When each note is a small, plain file, it's trivial to keep them one idea per note and link them into the kind of durable web a Zettelkasten is built on, the same reasoning behind writing evergreen notes that survive across projects and years.
The honest trade-offs
Markdown is not free of friction, and pretending otherwise would be dishonest.
- It's text-first. Great for writing and structure; awkward for tables, drawings, dense databases, or heavy media. If your notes are mostly diagrams or spreadsheets, Markdown fights you.
- The syntax is a small tax. You're typing
*and#symbols. Most people stop noticing within a day, but it is a learning bump. - "Standard" is loose. Core Markdown is universal; extensions (tables, footnotes, wiki-links, callouts) vary by app, so a note that renders perfectly in one tool can look slightly off in another.
- Handwriting and rich layout aren't its game. For those, a canvas tool beats a text file.
Who it's for, and when to skip it
Reach for Markdown if you write (notes, drafts, documentation, research) and you care about owning your words long-term. It's the format of choice for local-first tools precisely because it hands you control instead of renting it back to you.
Skip it if your notes are collaborative documents with rich formatting, or if you'd rather never see a syntax character. The clean split between a cloud workspace and a local plain-text tool is exactly what our Notion vs Obsidian comparison walks through.
And a fair disclosure: we make a notes app, Clair Mind, and it isn't built around Markdown editing. It's built around one-tap capture on your phone with connections made for you. But it takes the part of the Markdown philosophy that matters most: your notes stay yours, offline, and export to Markdown any time, so nothing you write is ever trapped. The format is the insurance policy; capturing the thought before it fades is still the game.
The wider map of formats and systems lives in note-taking methods, and the practical side, in organizing notes you'll actually use.