Markdown notes: a clean way to write, and what to watch for
By Gerald · 6 June 2026
Once you write notes in markdown, plain formatting starts to feel obvious. A hash for a heading, asterisks for emphasis, a dash for a list item, and the structure appears as you type without ever reaching for a toolbar. Your hands stay on the keyboard and your attention stays on the words. It is a genuinely nice way to write, and it is no surprise that so many note tools are built on it. But "markdown notes" can mean two quite different things, and the difference matters more than people expect when they are choosing a tool. This is a clear look at why markdown feels so good, the real tradeoff hiding under the term, and how to get the writing feel whichever route you take.
Why markdown feels good to write
The appeal of markdown comes down to flow. Formatting a document the traditional way means interrupting your thought to move the mouse, find a button, click it, and return, and each of those tiny interruptions is a small tax on concentration. Markdown removes the tax. You signal structure with a few characters as you type, and the formatting either appears live or renders when you are done, so you never leave the writing posture. Headings, lists, quotes, bold, and links all flow from simple syntax you quickly stop thinking about consciously.
There is also a calmness to it. Plain text with light syntax is uncluttered; there are no floating toolbars, no style menus, no temptation to fiddle with fonts. It keeps you focused on what you are saying rather than how it looks, which is exactly what most note-taking wants. For a lot of people, switching to markdown is the moment note-taking started to feel fast instead of fussy.
The two meanings of "markdown notes"

Here is the distinction that trips people up, and getting it clear will save you from picking the wrong tool.
The first meaning is raw markdown files. Tools like Obsidian and Joplin store each note as an actual .md file on your disk. The upside is maximum portability and the strongest possible ownership at the file level: your notes are plain text you can open in any editor, on any system, essentially forever, with no company in between. If you care about your notes outliving any particular app, raw files are the gold standard. The downside is that you are now managing files, and richer content like images, tables, and embeds tends to be more fiddly, because the plain-text format was designed for text first.
The second meaning is markdown-style writing inside a rich editor. Many modern note apps let you type markdown shortcuts that instantly become formatted rich text, without ever storing a raw .md file. You get the keyboard-driven writing feel that makes markdown pleasant, plus easy handling of images, tables, checklists, and embeds, because the underlying note is structured content rather than a plain-text file. The tradeoff is the mirror image of the first: you gain a smoother all-in-one editing experience and lose file-level portability, since the note lives in the app's format rather than as a .md file on disk.
Neither of these is wrong. They are different priorities. One optimizes for the permanence and portability of plain files; the other optimizes for a richer, smoother editor. Knowing which you care about is most of the decision.
How to choose between them
Decide what you are really optimizing for. If your top priority is that your notes remain plain, portable files you could open in any text editor decades from now, choose a raw-markdown tool and accept that images and tables will be a little more hands-on. If your top priority is a smooth writing experience that also handles images, tables, and embeds gracefully, choose a rich editor with markdown shortcuts and accept that the storage is the app's format rather than loose .md files. A useful test: imagine the app you use today disappearing tomorrow. If the thought of your notes being anything other than plain files on your own disk genuinely worries you, you are a raw-files person. If an easy export would satisfy you, a rich editor with markdown input will serve you better day to day.
Getting the writing feel either way
The encouraging news is that the part most people actually love, the keyboard-driven, toolbar-free writing flow, is available on both routes. Plenty of rich editors support the full set of markdown shortcuts, so you can write exactly as you would in a raw-markdown tool and still get clean images and tables. So you do not have to give up the writing feel to get convenience, nor give up convenience to get the writing feel. The only thing the two routes genuinely differ on is the storage format underneath, and therefore the kind of portability you end up with. Separate those two questions, the writing experience and the storage format, and the choice gets much clearer, because you can have the good writing feel regardless and decide the storage question on its own merits.
Where this leaves you
For most people who simply want notes that are fast and pleasant to write, a rich editor with markdown shortcuts is the path of least resistance, and they never miss the raw files. For people with a specific, considered need for plain-text permanence, raw markdown files are worth the small extra friction, and tools like Obsidian and Joplin are built precisely for them; the honest comparisons are Flow vs Obsidian and Flow vs Joplin. The wrong move is to choose a tool on the word "markdown" alone without noticing which of the two meanings it delivers, and then be surprised later when it turns out to be the other kind.
Why markdown won, and what that means for you
It is worth understanding why markdown became so dominant in note-taking, because it explains both its strengths and its limits. Markdown was created to be an easy-to-write, easy-to-read way of formatting plain text that could then be converted to other formats. The key design decision was that the raw text should look clean and readable even before it is rendered, unlike older markup where the source is cluttered with tags. That readability-of-the-source is why writing in markdown feels natural: the formatting characters are minimal and unobtrusive, so the text stays legible while you work.
That origin also explains the limits. Markdown was designed for text, with formatting as a light layer on top, which is why it handles headings, emphasis, lists, and links so gracefully and why richer content like complex tables, embedded media, and resizable images has always been more awkward. Different tools have extended markdown in their own ways to cope, which is partly why "markdown" can behave slightly differently from one app to the next. None of this undermines markdown; it just means the format is brilliant at its core job and stretched at the edges, which is exactly the tradeoff you are weighing when you choose between raw files and a rich editor.
For you, the practical takeaway is that markdown's enduring popularity is a feature in itself. Because so many tools support it, learning markdown is a portable skill: the muscle memory you build in one app carries to the next, and your habit of typing a hash for a heading or a dash for a list works almost everywhere. Whichever route you choose, raw files or a rich editor with markdown shortcuts, you are investing in a writing style that is unusually likely to outlast any single app, which is a quietly reassuring thing in a category where tools come and go.
Frequently asked questions
What are markdown notes? Notes written using markdown, a lightweight syntax where simple characters create formatting: a hash for headings, asterisks for emphasis, dashes for lists. It lets you format as you type without leaving the keyboard.
Should I use a raw markdown app or a rich editor? Choose raw markdown files if plain-text portability and permanence matter most to you. Choose a rich editor with markdown shortcuts if you want a smoother experience with easy images and tables. Both can give you the keyboard-driven writing feel.
Do all note apps store markdown as files?
No. Some store actual .md files on disk, like Obsidian and Joplin. Others let you write in markdown style but store the note in their own format. Check which, because it determines how portable your notes are.
Is markdown good for beginners? Yes. The core syntax takes minutes to learn and quickly becomes second nature, and many apps render it live so you see the result as you type. It is one of the lowest-effort ways to write clean, structured notes.
Related reading
- How to organize your notes: a simple system that survives real life
- Flow vs Obsidian: when simple beats infinitely customizable
- How to take notes on a computer (that you can find later)
The point of markdown is the writing feel. Decide separately whether you need the files.
If you want the markdown writing feel in a clean editor that also handles images and tables, with your notes owned on your own cloud, that is how Flow works, and it is free to try. If raw .md files are your priority, a file-based tool is the better fit, and that is an honest call.
Do you need raw markdown files, or just the clean writing feel? The answer makes the choice easy.