What is Markdown? The .md Plain-Text Format Explained

What is MARKDOWN?

Markdown is a lightweight markup language created by John Gruber in 2004, with input from Aaron Swartz, designed to be easy to read and write as plain text. Its goal is to let people format text using simple, unobtrusive punctuation that can be converted to structurally valid HTML.

A Markdown document is just plain text with conventions: hash marks for headings, asterisks or underscores for emphasis, hyphens for lists, and brackets for links. A processor converts these cues into HTML (or other formats). The IETF registered the text/markdown media type in RFC 7763 (2016), and the CommonMark project provides a precise, widely adopted specification.

How Markdown Works

Markdown is a lightweight markup language whose central goal is to be readable as plain text. Instead of wrapping content in verbose tags, it uses small, unobtrusive punctuation conventions that look natural even before they are rendered. You write a heading by starting a line with #, make text bold by surrounding it with **double asterisks**, and create a bullet list simply by beginning lines with -. The result reads cleanly in a raw editor, which is the whole point.

Under the hood, Markdown is not the final output; it is a source syntax that gets converted. A Markdown processor parses the text and translates each convention into HTML: a # line becomes an <h1>, **bold** becomes <strong>, and a list becomes a <ul> with <li> items. Because the target is HTML, Markdown also lets you drop raw HTML tags directly into a document for anything the plain syntax cannot express, giving an escape hatch when you need more control.

The syntax covers the common building blocks of writing: headings at several levels, emphasis and strong emphasis, ordered and unordered lists, links written as [text](url), images with a leading exclamation mark, inline code in backticks, fenced code blocks, and blockquotes marked with >. This small vocabulary is deliberately limited, which keeps the language easy to learn and easy to read.

That deliberate minimalism is also Markdown's main constraint. The original language has no standard way to express tables, footnotes, or complex layout, so anything beyond basic prose either drops down to embedded HTML or relies on non-standard extensions. Markdown is designed for structured writing, not page design, and it trades expressive power for the readability that made it popular.

History and Standardization

Markdown was created in 2004 by John Gruber, with input from Aaron Swartz. Their goal was explicit and unusual: a markup language whose source text is readable as-is, so that a document is legible whether or not it is ever processed. Gruber released a reference implementation and an informal syntax description, and the language spread quickly because it solved a real problem, writing for the web without hand-coding HTML.

For years there was no formal specification, only Gruber's original description and reference script. Different tools interpreted ambiguous cases differently, so the same Markdown could render inconsistently across systems. To address this, a group produced CommonMark, a precise specification that pins down the ambiguous corners of the syntax, and it has become the basis for many modern implementations.

Beyond CommonMark, popular dialects extend the core language. GitHub Flavored Markdown adds tables, task lists, and strikethrough, and other flavors add footnotes or math. This means most Markdown you encounter is CommonMark plus some agreed extensions, so the language is standardized at its core while remaining flexible at the edges.

Markdown Compared to HTML and Rich Text

Against HTML, Markdown trades power for readability. HTML can express any structure a browser understands, but its tags make raw source hard to read and tedious to type. Markdown covers the common cases of prose with far less friction, then compiles down to HTML for display. The two are complementary rather than competitors: Markdown is the comfortable writing layer, HTML is the powerful rendering target underneath.

Against a rich-text word processor like the model behind DOCX, Markdown is plain text, which brings real advantages. It works in any editor, diffs cleanly in version control so you can see exactly what changed, and never locks your content in a proprietary binary. What it gives up is precise visual formatting and features like tracked changes; Markdown records structure and intent, not exact appearance.

This combination of readability and simplicity is why Markdown became the default for developer documentation, README files, forum and chat posts, static-site content, and technical note-taking. Wherever people want to write structured text quickly, keep it in version control, and render it to the web, Markdown fits naturally, which is what turned a small 2004 project into one of the most widely used writing formats online.

MKV Technical Specifications

MARKDOWN vs Other Document Formats

Markdown keeps source human-readable with light formatting, while HTML offers richer structure at the cost of verbosity.

Advantages & Disadvantages

Common Use Cases

Markdown is used wherever lightweight, readable text formatting is valuable.