Markdown Preview
Type Markdown on the left and watch the rendered preview update as you go.
Markdown Preview
Type on the left, see the result here.
Formatting
Text can be bold, italic or inline code. Links work too: example.
- Unordered list item
- Another item
- Ordered list item
- Second item
A blockquote for quoted text.
function hello() {
return "code block";
}That is the whole idea.
Processed on your device — nothing is sent anywhere.
How it works
- Type or paste Markdown into the editor on the left.
- Watch the preview on the right update live — headings, bold and italic text, lists, blockquotes, code blocks and links render as you type.
- Keep editing until the preview looks right, then copy your Markdown wherever it is needed.
Frequently asked questions
- Which Markdown syntax is supported?
- The preview covers the everyday core of Markdown: headings with # through ######, **bold**, *italic*, `inline code`, fenced code blocks, unordered and ordered lists, blockquotes, horizontal rules and links. It is intentionally minimal, so extended syntax such as tables and footnotes is not rendered.
- Is raw HTML in my Markdown rendered?
- No. Any HTML tags you type are escaped and shown as plain text rather than executed. This keeps the preview safe — pasted content can never inject scripts or hidden markup into the page.
- Is my text sent to a server?
- No. The renderer is plain JavaScript running entirely in your browser, so nothing you type is uploaded, logged or stored. The tool also keeps working offline once the page has loaded.
- What is Markdown actually used for?
- Markdown is the standard plain-text format for README files on GitHub, documentation sites, technical blogs, and note apps such as Obsidian, and platforms like Reddit and Discord accept subsets of it. Learning the dozen core symbols once lets you write formatted text in all of these places without touching a rich-text editor.
- Why does my Markdown look different on GitHub or elsewhere?
- There is no single Markdown standard — GitHub, Reddit, Discord and static site generators each support different extensions and edge cases. Core syntax like headings, emphasis, lists and links renders the same almost everywhere, which is exactly the subset this preview covers. Features beyond that, such as tables or task lists, depend on the destination platform.
About this tool
This page is a live Markdown preview: a plain-text editor on the left, the rendered result on the right, updating keystroke by keystroke. It covers the core syntax used every day — all six heading levels, bold and italic emphasis, inline code and fenced code blocks, ordered and unordered lists, blockquotes, horizontal rules and links — which is exactly the subset that renders consistently on GitHub, documentation sites, forums and note-taking apps.
The renderer is a small piece of JavaScript that runs entirely in your browser. Your text is never uploaded, logged or stored, so drafts containing internal documentation or unpublished writing stay on your machine, and the tool keeps working offline once the page has loaded. As a safety measure, raw HTML embedded in the Markdown is escaped and displayed as text rather than executed — pasted content from unknown sources cannot inject scripts or hidden markup into the preview.
The common use cases are all variations on one theme: seeing what your Markdown will look like before it lands somewhere that matters. Drafting a README or a pull request description and checking the heading structure reads well. Debugging a list that refuses to nest or emphasis that will not close, where watching the preview react as you edit exposes the mistake in seconds. Writing an answer or post for a Markdown-based forum. Or simply learning the syntax, since the immediate feedback loop teaches it faster than any cheat sheet.
A few tips from practice. Put a blank line between blocks — most “broken” Markdown comes from a missing empty line before a list, heading or code fence. Indent nested list items consistently, and use fenced code blocks rather than indentation for code, as fences survive copy-paste far better. When output looks wrong on a specific platform, test the core-syntax version here first; if it renders correctly, the difference lies in that platform’s extensions rather than your text.