Markdown Preview
Write and preview Markdown in real time. Export as HTML. All client-side.
Live Markdown Editor
Markdown Preview
Write markdown on the left, see the result on the right.
Text Formatting
Bold text, italic text, strikethrough, and inline code.
Lists
- Item one
- Item two
- Nested item
- Item three
- First step
- Second step
- Third step
Task List
- Write the draft
- Add a code sample
- Proofread before publishing
Links & Images
Blockquote
The best tools get out of your way. This one does exactly that.
Code Block
function greet(name) {
return `Hello, ${name}!`;
}Table
| Tool | Category | Free |
|---|---|---|
| JWT Decoder | Dev | ✓ |
| Color Picker | Design | ✓ |
| UUID Generator | Dev | ✓ |
Everything processes in your browser. Nothing is stored.
CommonMark vs GitHub Flavored Markdown
Markdown was created in 2004 as a way to write formatted text in plain characters that stay readable even before they are rendered. Because the original spec left edge cases undefined, CommonMark emerged as a strict, unambiguous standardisation — it pins down exactly how nested lists, emphasis, and tricky punctuation should parse, so every compliant renderer produces the same HTML. GitHub Flavored Markdown (GFM) is a superset of CommonMark that adds the features developers use every day: pipe tables, task lists with tick-boxes, strikethrough with double tildes, automatic linking of bare URLs, and fenced code blocks with language tags for syntax highlighting. This editor supports the common, portable subset: headings, ordered and unordered lists, task lists, tables, code spans and fences, blockquotes, links, images, bold, italic, and strikethrough. Sticking to that subset keeps your documents working across GitHub, GitLab, Notion, Obsidian, and most static-site generators.
Markdown table and task-list syntax
A table is built from pipes and a divider row. Separate each column with a vertical bar | , then add a line of dashes under the header. Colons in that divider set alignment: :--- is left, :---: is centred, and ---:is right-aligned. You do not need the cells to line up visually in the source — the renderer handles spacing — but aligning them makes the raw Markdown far easier to read. Task lists are unordered list items with a checkbox: write - [ ] for an unchecked item and - [x] for a completed one. They are perfect for to-do lists, pull-request checklists, and acceptance criteria, and on platforms like GitHub the boxes become clickable. Use the formatting toolbar above to insert lists, tasks, links, and emphasis around whatever text you have selected, rather than memorising every marker.
When to use Markdown vs a WYSIWYG editor
Markdown shines when content lives close to code or version control: READMEs, technical docs, blog posts in a static-site generator, issue templates, and notes you want to grep, diff, and keep for decades in plain text. Because it is just text, it is future-proof, diff-friendly in git, and never traps your words in a proprietary format. A WYSIWYG editor (Word, Google Docs, a rich CMS) is the better choice when non-technical collaborators need to format without learning syntax, when you need complex page layout, comments and track-changes, or precise typography and image positioning. Many modern tools split the difference with a hybrid editor that accepts Markdown shortcuts while showing formatted output live — much like the split view here. A sensible rule: if the text will be read mostly by machines or developers, write Markdown; if it will be polished and laid out by people, a WYSIWYG tool will save you time.
Frequently Asked Questions
Find this useful?
These tools are free and ad-free. Support the project!