Markdown Previewer

Markdown exists because writing HTML by hand for every paragraph, list, and heading is slow, and reading raw HTML is worse. **bold**, a leading # for a heading, a leading - for a list item — Markdown's syntax is close enough to how people already format plain text that it reads fine even before it's rendered, which is exactly why READMEs, changelogs, and comment boxes across the web use it.

This tool renders GitHub-Flavored Markdown (GFM) — the same dialect GitHub, GitLab, and most developer tools use, which adds tables, task lists, and strikethrough on top of base Markdown. The rendered HTML is passed through a sanitizer before it's ever displayed, so raw HTML or a script tag embedded in the Markdown source can't run — only get displayed as literal text. Everything happens locally in your browser.

• •Leave a blank line between a paragraph and the next block (a list, heading, or blockquote) — Markdown parsers use blank lines to tell where one block ends and the next begins, and skipping one is the most common cause of "why isn't my list rendering as a list."
• •Fence code blocks with triple backticks and a language name (```js) rather than indenting with four spaces — it's more readable in the raw source and this tool (like GitHub) uses the language name for syntax awareness.
• •GFM tables need a header row and a separator row (|---|---|) — the separator row's dashes are what tell the parser "this is a table," not just any row full of pipe characters.
• •Task list checkboxes ([ ] and [x]) render as real, disabled checkboxes here for visual fidelity, but they're just text in the underlying Markdown — clicking one in a real renderer (like GitHub's issue tracker) doesn't toggle anything unless that specific platform wires it up.