Why We Use .md (Markdown), and Why It's Becoming a Standard

Our article pages are written in .md files.

On March 9, I participated as a panelist at an International Women's Day event co-hosted by the British Embassy and the Canadian Embassy in South Korea. As an AI Engineer, I shared a brief talk about the current era of AI and how the way developers work is changing. During the networking session that followed, I received many questions.

The questions ranged widely — from South Korea's homegrown foundation models to how multilingual data is handled. At one point, Markdown files came up, and someone asked why they matter. I don't think I explained it as well as I could have, so I went home, did some research, and decided to put my thoughts together.

This article is my attempt to articulate why I feel markdown is increasingly taking on the role of a standard.

Markdown Is Not Just README Syntax

Many people think of markdown as "that thing developers use for READMEs." But in practice, markdown plays a much broader role.

• You can quickly draft a document
• Diffs are clean, making it a natural fit for Git
• It lets you express structure — headings, lists, links, code blocks — with minimal overhead
• It easily feeds into documentation sites, wikis, blogs, issues, PRs, and notes

In other words, markdown is less about being a fancy editor and more about being a lightweight working format that bridges writing, editing, and sharing.

In the Age of AI, Markdown Becomes Even More Important

With generative AI entering the picture, we're not writing less — we're writing more.

• Writing prompts
• Giving task instructions to agents
• Summarizing meeting notes
• Leaving review comments
• Organizing experiment logs
• Writing release notes and articles

What matters in this workflow isn't "beautifully formatted documents." It's a format you can write quickly, revise easily, refine with AI, and share with your team.

Markdown fits perfectly here. It's text-based, so it's easy for humans to read, easy for models to process, and easy to track in version history. In practice, markdown keeps structure while staying lighter than HTML-heavy content, which is one reason it keeps showing up in AI-facing workflows.

That's why markdown isn't just a document format — it functions as a shared working format that both humans and AI can collaborate on.

In 2026, Markdown Is Becoming the Lingua Franca of AI Agents

Between 2025 and 2026, several pivotal developments have elevated markdown's status even further.

Cloudflare: "Markdown for Agents"

In February 2026, Cloudflare announced a feature that automatically converts HTML web pages to markdown when requested by AI agents. When an AI agent includes Accept: text/markdown in its HTTP headers, Cloudflare's edge network performs real-time HTML → Markdown conversion. Based on Cloudflare's own blog, this resulted in up to an 80% reduction in token usage¹.

This isn't just a feature addition. It means web infrastructure has started treating AI agents as first-class citizens — and the interface format it chose is markdown.

AGENTS.md: A README for AI

If README.md serves as a guide for human developers, AGENTS.md is emerging as a guide for AI coding agents. By documenting a project's structure, coding conventions, testing methods, and PR guidelines in markdown, AI agents can read the file and gain context about the project.

By August 2025, over 20,000 GitHub repositories had adopted AGENTS.md, and by early 2026 that number surpassed 60,000. Major AI coding tools including OpenAI Codex, Google Jules, and Cursor recognize this file². More recent reporting also notes that adoption and proven performance impact are not the same thing, and the value of context files is still being evaluated more rigorously³.

llms.txt: A robots.txt for AI

Just as robots.txt guides search engine crawlers, llms.txt is a proposal for providing LLMs with a site's key information in markdown format. It was proposed by Jeremy Howard of Answer.AI in September 2024, and companies like Anthropic, Vercel, Cloudflare, and Hugging Face have begun adopting it⁴.

What's worth noting is that all of these emerging standards have chosen markdown as their default format.

Markdown's Strength Lies in Being Content-First

Word, Notion, and Google Docs are all powerful, of course. But at the drafting stage, they often make you think about formatting before content.

Markdown, on the other hand, almost always makes you focus on content and structure first.

• # is a heading
• - is a bullet
• 1. is an ordered list
• [text](url) is a link

The syntax is simple enough to stand the test of time. Even when tools change, the source survives, and converting to HTML or other rendered outputs is straightforward.

Why We Can Say Markdown Is "Becoming a Standard"

Precision of language matters here.

Claiming that markdown has become a single, unified, officially ratified standard would be an overstatement. The classic problem with markdown has always been that "everyone calls it markdown, but every implementation behaves differently."

That's exactly why CommonMark was created. The CommonMark project explains that John Gruber's original markdown description wasn't precise enough, and the legacy implementation Markdown.pl had been effectively frozen since 2004, leading to inconsistent rendering across systems. (The latest official spec is version 0.31.2, released January 2024.)⁵

CommonMark addresses this by providing a stricter, more interoperable markdown specification. And this isn't just theory. The CommonMark website explicitly mentions that major platforms like GitHub, GitLab, Reddit, Stack Overflow / Stack Exchange, and Discourse have adopted it⁶.

So markdown isn't a "perfect single standard" — it's more accurate to describe it as an ecosystem where de facto standardization has strongly converged around CommonMark.

In Practice, What You'll Encounter Most Is GitHub Flavored Markdown

Realistically, the markdown most people interact with isn't original markdown — it's closer to GitHub Flavored Markdown (GFM).

GFM extends markdown with several elements commonly needed in practice:

• Tables
• Task lists (checklists)
• Strikethrough
• Autolinks

According to GitHub's official docs, markdown is used not just in .md files but across issues, PRs, discussions, and comments. This means markdown has become less of a writing syntax and more of a default language for collaboration interfaces.

In the 2025 Stack Overflow Developer Survey, markdown was named the "most admired sync tool" for the third consecutive year, and 84% of surveyed developers reported using or planning to use AI tools⁷. The simultaneous growth of markdown and AI tools is no coincidence.

Markdown is nearly ubiquitous across development teams:

Where You'll See It	What It's Typically Used For
README	Project overview, installation, usage
ISSUE	Bug descriptions, reproduction steps
PR	Change summaries, review points
WIKI / DOCS	Guides, policies, operational docs
RELEASE NOTE	Changelog entries
AGENTS.md	Project context for AI agents

IETF's text/markdown Is an Important Signal

In 2016, IETF RFC 7763 registered the text/markdown media type⁸.

This document doesn't lock markdown down as a single, complete specification either. It describes markdown as a family of plain-text formatting syntaxes with many variants.

Still, the fact that text/markdown was registered is significant. It means markdown had become so widely used across the internet ecosystem that a common identifier at the MIME level became necessary.

That doesn't happen for passing syntax trends. And in 2026, Cloudflare's Markdown for Agents leverages exactly this Accept: text/markdown header in production — making RFC 7763 a case of decade-old foresight becoming reality.

Why So Many Tools Converge on Markdown

The reason is simpler than you might think. Markdown satisfies all of the following conditions simultaneously:

1. Human-readable
2. Machine-parseable
3. Version-control friendly (Git diff)
4. Vendor-neutral
5. Low authoring cost (compared to HTML)
6. AI-native (LLMs have been trained on it at massive scale)

That's why documentation, blogs, developer collaboration, knowledge bases, static sites, and LLM input formats can all meet on top of markdown.

Gartner projects that by the end of 2026, 40% of enterprise applications will embed AI agents (up from less than 5% in 2025)⁹. The fact that markdown is being chosen as the shared format these agents read and write tells us that markdown's role has grown beyond just a document format.

Our article pages are written in md files for exactly this reason. It's a structure that lets us write fast, manage with Git, refine with AI, and render as web pages.

---

Why Markdown Elements Are More Than Enough in Practice

In reality, you use fewer elements than you'd expect:

• bullet list
• ordered list
• inline code
• code block
• table
• quote
• horizontal rule
• strikethrough

Just the patterns below are sufficient for most documents.

A Simple Checklist

• Draft written
• Links added
• Team review incorporated

Priority Example

1. Write quickly
2. Organize the structure
3. Add necessary links and references
4. Connect to a deployable format

Comparison Example

Aspect	Markdown	Heavy Document Editors
Drafting speed	Fast	Relatively slow
Git diff	Good	Limited
Compatibility with AI	Good	Moderate
Portability	High	Tool-dependent

You don't need a full-featured editor to produce a good document.
More often than not, a format you can write quickly and keep iterating on is stronger.

If I Had to Sum Up Why I Keep Using Markdown in One Line

I don't use markdown just because it's convenient.

I keep using it because it's a text-based shared format that bridges people, AI, editors, Git, documentation sites, and collaboration platforms with the least friction.

And that's why markdown isn't just a personal preference — it's already settling in as the de facto default across many major platforms and tools.

---

References

Footnotes

1. Cloudflare, "Markdown for Agents", February 2026. Automatically converts HTML when AI agents request Accept: text/markdown, with up to 80% token reduction reported on Cloudflare's own blog. — Cloudflare Blog: Introducing Markdown for Agents ↩

2. InfoQ, "AGENTS.md Emerges as Open Standard for AI Coding Agents", 2025. See for GitHub adoption numbers and supported tool list. — InfoQ: AGENTS.md ↩

3. InfoQ, "New Research Reassesses the Value of AGENTS.md Files for AI Coding", 2026. — InfoQ: AGENTS context file value review ↩

4. Jeremy Howard / Answer.AI, "llms.txt — A Proposal", September 2024. — llms.txt Specification / Answer.AI: Introducing llms.txt ↩

5. CommonMark Spec 0.31.2, released January 28, 2024. — CommonMark Spec 0.31.2 ↩

6. The CommonMark official website directly mentions adoption by GitHub, GitLab, Reddit, Stack Overflow, and Discourse. — CommonMark Official Site ↩

7. 2025 Stack Overflow Developer Survey. Markdown named most admired sync tool for the third consecutive year. 84% of developers using or planning to use AI tools. — 2025 Stack Overflow Developer Survey ↩

8. IETF RFC 7763, "The text/markdown Media Type", 2016. — RFC 7763 Full Text ↩

9. Gartner forecast cited in Aakash Gupta's March 7, 2026 post. — The PM's Guide to Agent Distribution ↩