Markdown Previewer
Write Markdown on the left, see the rendered HTML update instantly on the right. Export clean HTML when you're done — nothing you type ever leaves your browser.
By Alex van den Berg · Last reviewed · How we test our tools
Markdown syntax cheat sheet
| Element | Markdown | Result |
|---|---|---|
| Heading | # H1 · ## H2 · ### H3 | Section titles, largest to smallest |
| Bold | **bold text** | bold text |
| Italic | *italic text* | italic text |
| Strikethrough | ~~old~~ | |
| Link | [text](https://url) | a clickable link |
| Image |  | an embedded image |
| Inline code | `code` | code |
| Code block | ```lang ... ``` | Syntax-styled block |
| Blockquote | > quoted text | Indented, tinted quote |
| List | - item · 1. item | Bulleted or numbered list |
| Table | | a | b | |---|---| | A bordered data table |
| Horizontal rule | --- | A dividing line |
Why Markdown instead of rich text?
John Gruber and Aaron Swartz created Markdown in 2004 with a simple goal: writing should look like writing, even before it's converted to HTML. A line starting with # obviously reads as a heading; text between ** obviously reads as emphasised — you don't need to render it to understand the structure.
That plain-text nature is why Markdown dominates developer documentation, README files, GitHub issues, static site generators (Jekyll, Hugo, Astro), and note-taking apps (Obsidian, Notion's import format). Because it's plain text, it works cleanly with version control: a Git diff on a Markdown file shows exactly what changed in the sentence, not a wall of HTML attribute noise.
Frequently Asked Questions
Is this Markdown converter GitHub-flavoured?
It supports the core CommonMark elements plus the GitHub-flavoured extras used most often: fenced code blocks, tables, and strikethrough (~~text~~). It does not implement footnotes or task-list checkboxes.
Does this tool store or upload my Markdown?
No. Parsing and rendering happen entirely in your browser via JavaScript. Nothing is sent to a server, so it's safe to use for drafts, private notes, or content you haven't published yet.
Can I export the rendered HTML?
Yes — use "Copy HTML" to copy the rendered markup to your clipboard, or "Download HTML" to save it as a standalone .html file, ready to paste into a CMS, email template, or static site.
Why does my table not render correctly?
GitHub-flavoured Markdown tables need a header row, then a separator row made of dashes and pipes (e.g. |---|---|), then your data rows. Missing that separator row is the most common reason a table shows up as plain text instead of a grid — check the cheat sheet above for the exact syntax.
What's the difference between Markdown and rich text (WYSIWYG)?
Markdown is plain text with lightweight formatting symbols (like ** for bold) that any text editor can open and understand. Rich text / WYSIWYG editors store formatting invisibly, usually as HTML, which is harder to version-control, diff, or read as raw text. Markdown is generally preferred for documentation, READMEs, and any content that lives in Git.
Sources & further reading
- CommonMark Spec — the standardised, unambiguous Markdown specification. commonmark.org
- GitHub Docs — "Basic writing and formatting syntax" (GFM extensions). docs.github.com