A Simple Syntax, Many Interpretations
Markdown was designed to let people write formatted text using readable punctuation: asterisks for emphasis, hash marks for headings, and brackets for links. But its original description left some details open to interpretation. That gave software makers room to decide how the same sequence of characters should be read—and to add features the basic format did not define.
A Markdown app does not merely display punctuation. It parses the text, deciding which characters mark structure and which should appear literally. Small differences in those decisions can change the result. One platform may recognize a line beginning with `- [ ]` as an unchecked task box; another may show the brackets and dash as ordinary text. Tables and strikethrough are also common extensions, but they are not supported everywhere.
Why Compatibility Is Hard
Markdown’s appeal is partly its flexibility: a writer can use a lightweight format that works well for a particular site or tool. The tradeoff is that a document may rely on features outside the shared core. Copy it elsewhere, and the new parser may omit a feature, interpret punctuation differently, or handle an edge case another way.
Projects such as CommonMark have sought to define a more precise, consistent core. Even with such efforts, platforms can keep adding their own extensions. A file labeled “Markdown” therefore does not guarantee identical rendering across apps. For content meant to travel, sticking to basic headings, paragraphs, lists, emphasis, and links makes surprises less likely.
