What is CommonMark? Definition of the markdown standard

CommonMark is an unambiguous specification of markdown syntax: the standard that defines exactly how a given piece of markdown should render, used as the baseline by GitHub, Discourse, Discord, and most modern markdown tools.

The motivation is interoperability. Early markdown had ambiguous cases (exactly how deeply lists could nest, what made something a paragraph versus a heading, what characters needed escaping), and different implementations resolved them differently. The same document might look correct in one tool and broken in another. CommonMark settled the ambiguities so a document that conforms renders identically across implementations that follow the spec.

Where the spec lands in practice

For most users, the difference is invisible: they write what looks like markdown and it renders. The spec matters when a document needs to travel: across editors, into a chat surface, into an AI coding tool, into version control. A CommonMark-conformant document survives every leg of that journey unchanged.

For LLM workflows, that interoperability is a real benefit. A feedback document exported as CommonMark renders the same way for a human reviewer reading it on a web page and for a coding agent ingesting it from a markdown file.

Frequently asked questions

How is CommonMark different from "markdown"?

Markdown is the family of related text-to-HTML formats started by John Gruber in 2004. CommonMark is the precise specification that nailed down the ambiguous cases: exactly how lists nest, what characters need escaping, what the parsing rules are.

Why does CommonMark matter for LLM workflows?

Because AI tools can rely on consistent output. A markdown document that follows the spec renders the same in GitHub, in Claude Code, in Cursor, and in the user's editor. Off-spec markdown might render four different ways.