You spent a weekend organizing your notes into a beautiful app: color-coded notebooks, collapsible sections, links between ideas. Two years later the company folds, and the export function hands you a zip file nothing else can read. Meanwhile, the plain text file your colleague saved in 2004 opens instantly on any machine you touch.
That asymmetry is the argument for Markdown, a way of formatting text with ordinary keyboard characters so the file stays readable everywhere, forever. It looks like a programmer's tool. It was built for writers, and it is the closest thing prose has to a universal file format.
What Markdown actually is
John Gruber released Markdown in 2004 with one premise: formatting should be visible in the file. Instead of clicking Bold and storing an invisible instruction inside a binary document, you type two asterisks around a word, and anyone can see it is emphasized. The file stays plain text. Open it in Notepad and you get readable prose with light punctuation. Open it in any Markdown app and you get proper headings, italics, and lists.
The symbols were chosen because writers already typed them. Wrapping a word in asterisks for emphasis in a quick email is exactly the instinct Markdown formalized.
The eight elements you actually need
The full specification contains more, but prose writers live on eight. In the order you will reach for them:
Headings. A hash and a space: # Chapter One is a top-level heading, ## The Long Way Round sits one level down. Three levels handle nearly any document, and most apps turn headings into automatic navigation.
Emphasis. One asterisk for italics, two for bold. Tildes give strikethrough, which is handy for visible self-edits.
Lists. A dash and a space make a bullet. Numbers make ordered steps. Indent two spaces to nest a list inside a list.
Links. Text in square brackets, address in parentheses: [the style guide](https://example.com/guide). The anchor text stays readable even if the link dies, which beats a raw URL pasted mid-paragraph.
Blockquotes. A greater-than sign marks quoted material, rendered indented. Use it for sources, or in drafts, for the voice you are arguing against.
Code spans. A backtick wraps text that must appear exactly as typed: preserve my spacing. Writers use these for usernames, foreign transliterations, and anything an editor should not "fix".
Tables. Pipes separate columns, and a row of pipes and dashes declares the header. Tables are an extension (see the dialect note below), but nearly everywhere you publish supports them.
Horizontal rules. Three hyphens alone on a line become a scene break. Fiction writers use them for point-of-view switches; essayists use them to pivot topics without a subheading.
Why plain text wins the long game
Word processor documents are small databases with a fragile reputation. WordStar ruled the early 1980s; its .ws files are museum pieces now. Microsoft Word has changed its native format twice in living memory, and features drift between versions. Note apps are worse, because your writing lives on their servers. When the startup dies, the highlight collection dies with it.
A Markdown file makes no demands. No program version, no schema, no account. If every Markdown app vanished tomorrow, the files would degrade gracefully into text with occasional asterisks, still readable by every human and machine. This is why archives and journals increasingly accept plain-text formats: when retention is measured in decades, the simplest container wins.
You already live inside Markdown
GitHub renders every README as Markdown, which is why open-source documentation looks consistent across a million projects. Obsidian and Notion both speak it, which is why migrating between them hurts less than migrating between anything else. Reddit's post editor, Discord's chat formatting, and Stack Overflow all run Markdown or a close cousin. When you type asterisks around a word in Slack and it italicizes, that is Markdown's fingerprint.
The dialects differ at the edges:
| Where | Flavor | Quirk to know |
|---|---|---|
| GitHub | GitHub Flavored Markdown | Tables, task lists, strikethrough |
| Markdown-ish | Tables only in the new editor | |
| Discord | Markdown-ish | Headings arrived late; no tables |
| Obsidian | Markdown plus extensions | [[double brackets]] link notes internally |
| Notion | Markdown on import | Toggle blocks stay Notion-only |
The core syntax travels nearly everywhere. Learn it once and the skill carries you from novel drafts to bug reports.
The conversion moment
Sooner or later raw Markdown must become something else: a web page, a formatted email, a PDF for a client. That is the job of a markdown to HTML converter. Paste your file in and get clean HTML that respects your headings, lists, and tables, ready for a blog or newsletter without fighting a visual editor.
Conversion only works when the input is clean. Text pasted from Word or the web can carry curly quotes, doubled spaces, and invisible formatting characters that confuse a parser, so run it through a text cleaner first. If the output shows é where your é belongs, that is not Markdown's fault; see character encoding explained. Punctuation choices also survive conversion exactly as typed, which is a good reason to settle the hyphen versus dash question before you convert.
Frequently Asked Questions
Do I need to learn all of Markdown?
No. The eight elements above cover almost every prose job, from shopping lists to book drafts. Footnotes, images, and embedded HTML exist, but you can ignore them for years and pick them up when a document asks.
Is Markdown the same everywhere?
The core is. Tables, strikethrough, and footnotes are extensions, mostly from GitHub Flavored Markdown, and support varies by platform. Before publishing anywhere important, test one small file there.
Can I use Markdown with Word or Google Docs?
Google Docs converts some Markdown shortcuts as you type, and the free command-line tool Pandoc converts Markdown files to .docx and back with structure intact. For client work that must arrive in Word, write in Markdown and convert at the end.
What if my notes are trapped in a proprietary app?
Look for an export to Markdown, HTML, or plain text; most serious note apps offer one because the demand never stops. An app that cannot export to a portable format is a warning sign worth heeding before you commit years of writing to it.
Does Markdown change how I write, not just how I format?
Slightly, and usually for the better. Because you cannot fuss with fonts mid-sentence, the temptation disappears and editing energy returns to the words. We see it in switched-over writers' drafts: fewer formatting experiments, more actual revision.
Convert one file today
The way to learn Markdown is not to read about it. Pick one old note or draft chapter and retype its headings and emphasis in Markdown, ten minutes of work, then open the result in a plain text editor to confirm it still reads. Run it through a converter afterward to see the other side. After that round trip the syntax is in your hands, and the file you just made will outlive every app currently installed on your computer.