A Markdown File Should Just Open

This argues that Markdown should be treated as a first-class document format by every modern operating system so a .md file will open as a readable, editable document without installing extra software. Markdown’s strengths - plain text portability, long-term accessibility, wide adoption in READMEs, documentation and publishing - mean operating systems ought to render headings, links, tables and lists instead of showing raw syntax. Current experiences are inconsistent: some platforms convert Markdown into rich-text when importing, others require obscure utilities or extensions, and viewers can silently discard unfamiliar syntax. A satisfactory native experience would let users toggle between formatted view and source, respect system fonts and accessibility, and preserve the original file in place across macOS, iOS, Windows, Linux, Android and visionOS.

Practical obstacles are small: CommonMark and GitHub Flavored Markdown already define usable baselines, and renderers can safely ignore extensions while preserving unknown content. Built-in viewers should avoid executing untrusted code, load external resources cautiously, and work offline. Growing use of Markdown by AI systems makes native support more urgent - exports, reports and generated documentation should open, edit and remain portable without locking users into a platform. Native OS support would increase interoperability, protect user ownership of files, and simplify everyday workflows.