Who uses Markdown — and who doesn't
It quietly runs under a huge slice of the things you read and write online. But it isn't the right tool for everything — and knowing the edges makes you better at using it.
The developers (all 180-million-plus of them)
Markdown's biggest home is the world of software. Nearly every project on GitHub — the platform where 180-million-plus developers collaborate across hundreds of millions of repositories — opens with a README.md file written in Markdown. It's how code gets explained, documented, and discussed. GitLab, Stack Overflow, and countless documentation sites run on it too. If you've ever read a project's homepage on GitHub, you've read rendered Markdown.
The writers and note-takers
A whole generation of writing tools adopted Markdown as their native language — apps like Obsidian, Notion, Bear, Typora, and Logseq. The appeal is simple: your notes stay as portable .md files you can read in any editor, with no proprietary format locking them in. Bloggers and technical writers lean on it for the same reason Gruber did in the first place — it gets out of the way of the words.
- Developers & open-source projects
- Technical & documentation writers
- Note-takers and researchers
- Bloggers and newsletter authors
- Forum & chat communities
- AI chatbots, by default
- Print & magazine designers
- Pixel-precise marketing layouts
- Complex spreadsheets & data
- Slide-by-slide presentations
- Anyone who wants WYSIWYG
- Heavy academic typesetting*
The machines
The newest big user isn't a person at all. Large language models — the AI behind modern chat assistants — output Markdown by default. It's compact, structured, and easy to render, which makes it a natural way for an AI to return a tidy answer with headings and lists. Markdown has quietly become a shared language between humans and machines.
And who doesn't reach for it
Markdown is deliberately small, and that's also where it stops. It was built for structure, not precise visual design. If you need exact control over fonts, columns, page breaks, or where an image sits to the millimetre, Markdown isn't your tool — that's the territory of page-design software and, for heavy academic or mathematical typesetting, systems like LaTeX. People who prefer clicking buttons in a WYSIWYG editor may never touch the raw marks at all.
There's a subtler gap too: some popular features aren't really "Markdown." Tables, for instance, aren't part of the core CommonMark standard — they're an add-on that GitHub and others layer on top. So a document that looks perfect on GitHub can fall apart when pasted somewhere that doesn't support those extensions. Knowing what's core and what's an extension is what separates a casual user from a confident one — and it's exactly what the next read covers.