The Unlikely Origin Story of Markdown
Few technologies have a creation story as quietly human as Markdown's. There was no venture capital, no grand product launch, no team of engineers working across time zones. There was John Gruber — a writer and developer with strong opinions about how plain text should look — and a set of simple conventions he wanted to share with the world. What happened next is the kind of story that sounds improbable in retrospect: those conventions became the foundational formatting language of the modern web, developer tooling, documentation systems, and now, artificial intelligence.
In a recent episode of The Vergecast, host David Pierce sat down with John Gruber himself, along with writer and technologist Anil Dash, to recount how Markdown came to be and how it quietly conquered the digital world. Their conversation is a fascinating reminder that the technologies that endure are often not the most sophisticated ones — they are the ones that solve a genuinely human problem in a genuinely human way.
What Is Markdown, Really?
Before diving into its rise, it helps to understand what Markdown actually is — because the answer is more philosophical than technical. Markdown is not, strictly speaking, a programming language. It is not a markup language in the heavyweight sense that HTML or XML are. As Gruber himself has articulated, Markdown is better described as a set of conventions for formatting plain text.
The core idea is deceptively simple: if a broad enough group of people agrees to follow the same basic formatting habits when writing plain text, that plain text becomes significantly more expressive than a raw, unadorned string of characters. A hashtag symbol at the start of a line becomes a heading. A pair of asterisks around a word makes it bold. A hyphen at the start of a line creates a bullet point. None of these require a special application, a proprietary file format, or a rendering engine to be legible. They are readable as plain text and renderable as rich text — and that dual nature is precisely the source of Markdown's power.
Steady Growth, Then a Step Change
Markdown's adoption has not been a sudden explosion. It has been a steady, almost inevitable climb — the kind that happens when a tool is genuinely useful and has no meaningful drawbacks. Developers adopted it for README files on GitHub. Technical writers adopted it for documentation. Bloggers adopted it for posts. Note-taking apps like Obsidian and Notion built entire interfaces around it. Static site generators made it the default input format for websites.
But something shifted more recently that elevated Markdown from a popular convention to something closer to a universal standard. Large language models — the AI systems behind tools like ChatGPT, Claude, and countless others — have embraced Markdown as their default output format. When an AI assistant structures a response with headers, bullet points, bold terms, and numbered lists, it is almost certainly using Markdown. This makes intuitive sense: Markdown is both human-readable and machine-readable, which makes it the ideal bridge between the two. In the world of LLM agentic systems, where AI agents must communicate reliably with both humans and other software systems, Markdown has become the de facto lingua franca.
Plain Text Is the Real Winner
Gruber's own take on Markdown's success is characteristically sharp. He argues that the biggest driver of Markdown's continuing relevance is not Markdown itself — it is the broader triumph of plain text files. Plain text has won, both for system configuration and for the interchange of human-readable prose. And because LLMs are trained on human-readable prose, plain text has also become the medium through which AI systems best understand and generate content.
This is an important distinction. Markdown did not win because it was a clever language that outcompeted rivals. It won because it formalized the way thoughtful people were already inclined to format their plain text. Gruber did not invent a new way of writing — he codified an existing one. That is a very different, and arguably more durable, kind of innovation.
Even the spread of Markdown into unexpected corners of the tech world — including Apple's developer ecosystem, where it appeared prominently at WWDC 2026 — reflects this underlying truth. Markdown shows up wherever plain text is taken seriously, which turns out to be nearly everywhere that matters.
The Formatting Holy Wars
Of course, no technology story is complete without a few villains, and the Markdown story has its share of frustrations. Gruber has never hidden his annoyance at platforms that adopted their own competing conventions — particularly the choice, made by apps like Slack and WhatsApp, to use asterisks for bold text rather than italic. To those who believe this should mean bold and not italic, Gruber's response is blunt.
It is a small grievance in the grand scheme, but it speaks to something important about standards in general: their value comes precisely from their universality. A convention followed by most people most of the time is useful. A fragmented landscape of competing micro-conventions erodes that value and creates friction for users who move between platforms.
Why Markdown's Success Matters Beyond Tech
The story of Markdown is ultimately a story about how writing tools shape thought. When the friction of formatting is removed — when a writer can focus entirely on ideas and trust that their structure will be preserved and rendered correctly — writing improves. Documentation becomes clearer. Communication becomes more precise.
As AI systems become more deeply embedded in every layer of knowledge work, the fact that they speak Markdown fluently means that human writers who know Markdown are better positioned to collaborate with those systems. The convention Gruber formalized over two decades ago turns out to have been quietly future-proof all along.
Key Takeaways
- Markdown was created by John Gruber as a set of plain text formatting conventions, not a formal programming or markup language.
- Its adoption has grown steadily for years across developer tools, documentation, blogging platforms, and note-taking apps.
- The rise of large language models has accelerated Markdown's dominance, making it the standard output and input format for AI systems.
- The deeper story behind Markdown's success is the triumph of plain text files as the most portable, readable, and durable format for both human and machine communication.
- Inconsistent adoption by platforms like Slack and WhatsApp remains a point of contention, highlighting how fragmented standards diminish collective value.
- Markdown's longevity suggests that the best formatting tools are those that align with how thoughtful humans naturally write — and then get out of the way.
Whether you are a developer writing documentation, a content creator drafting blog posts, or an AI agent structuring a complex response, the odds are overwhelming that Markdown is part of how you communicate. That is not an accident. It is the result of a genuinely good idea, shared openly, at exactly the right moment in history.