What Is Markdown? Plain Text That Already Looks Like What It Means

Markdown is a way of writing formatted text in a plain text file. There is no application that owns it, no binary format, no version compatibility to worry about. You write symbols that already resemble the formatting they produce, and something else turns them into headings and bold text later.

It was invented in 2004 for writing web posts without typing HTML. Two decades later it is the input format for most note apps, nearly all developer documentation, chat tools, static website generators, and the way people write prompts and documents for AI tools. Nobody standardised it into that position; it spread because it is readable before it is rendered.

Nearly the Whole Syntax

• # Heading — one hash for the biggest, more hashes for smaller ones.
• **bold** and *italic*.
• - item at the start of a line for a bullet; 1. item for a numbered list.
• [text](https://example.com) for a link.
• ![description](image.jpg) for an image — the same thing with an exclamation mark.
• > quoted text for a block quote.
• Backticks around code.
• A blank line between paragraphs.

That is most of it. You can learn the whole thing in the time it takes to read this section, which is the second reason it spread.

Why It Won Over HTML

Both describe structured text, and both are plain text files. The difference is what happens when a human looks at the source.

HTML wraps everything in tags. A paragraph with one bold word carries more punctuation than language. It is unambiguous and machines love it, but reading it is work, and writing it by hand is slow.

Markdown’s symbols were chosen to look like what they mean. A list looks like a list before anything renders it. A heading stands out. Emphasis marked with asterisks reads as emphasis. The unrendered source is itself readable, which means a Markdown file is useful even opened in the plainest text editor on a machine with nothing installed.

The Real Argument: It Is Just a Text File

This matters more than the syntax, and it is the part people come to appreciate years later.

• Nothing can take it hostage. There is no application whose subscription lapsing locks your notes. Any text editor ever written opens it.
• It will still open in decades. Plain text is the one format with a genuine track record of surviving.
• It is searchable with ordinary tools — no index, no database, no export step.
• Changes are visible. Two versions can be compared line by line, and version control works on it properly, which is why documentation lives in Markdown.
• It converts outward easily to HTML, PDF, Word or slides, while the original stays the source of truth.

The cost of a note taken in a proprietary app is invisible until the day you want everything out of it. Markdown has no such day.

The Weakness: There Is No Single Markdown

This is the honest complaint, and it is real.

The original 2004 description was loose, and different tools filled the gaps differently. Today you will meet:

• CommonMark — the careful specification that pinned down the ambiguities.
• GitHub Flavored Markdown — CommonMark plus tables, strikethrough, task lists and automatic links. The most widely assumed variant.
• Various app dialects — footnotes, highlighting, internal links, maths, each written slightly differently.

The basics are identical everywhere. The divergence starts with tables and anything beyond them, which is why a document can look right in one app and subtly wrong in another. Keep to the core syntax if the file will travel.

What It Deliberately Cannot Do

Markdown has no control over page size, margins, fonts, columns, exact spacing or where a page breaks. This is not an oversight — it is the design. Markdown describes what a thing is (a heading, a quote, a list), not what it looks like. Appearance is decided later by whatever renders it.

So Markdown is wrong for a designed document: a brochure, a poster, a form, a contract whose layout is part of its meaning. It is right for text whose structure matters and whose appearance can be decided downstream.

Getting It Out

Because Markdown is a source format, delivery usually means converting it. To HTML for the web, to PDF when someone needs a fixed page to print or sign, to Word when a reviewer will track changes, to slides for presentation tools.

The discipline worth keeping: convert outward, never edit the output and call it the master. The moment corrections start living in the exported PDF, the Markdown file becomes a stale copy and the advantage is gone.

Who Should Use It

Anyone keeping notes they expect to still have in ten years, anyone writing documentation, anyone drafting text that will end up in several places. It costs an afternoon to learn and removes an entire category of future problem.

It is the wrong tool for a document that must look exactly like something, and for collaborators who need a familiar word processor. Those are real constraints, not reasons to dismiss it.

Quick Reference

• # heading, **bold**, *italic*, - list, [text](url)
• Plain text — opens anywhere, searchable, diffable, outlives applications
• Readable before it is rendered; that is the whole idea
• Flavours differ beyond the basics — tables onward is where they split
• No control over layout, by design
• Convert outward to PDF or Word; keep the Markdown as the master