Is my Markdown sent to a server?

No. Rendering happens entirely in your browser using the marked library, and the resulting HTML is sanitized with DOMPurify before display. Nothing is transmitted or stored.

Is it safe to preview Markdown from untrusted sources?

The rendered output is passed through DOMPurify, which strips script tags, event handlers, and other dangerous HTML before it touches the page. Still, avoid clicking links in content you do not trust.

Which Markdown flavor is supported?

The tool uses marked, which supports CommonMark plus common GitHub-flavored extensions such as fenced code blocks and autolinks. Platform-specific extras like GitHub task-list checkboxes may render differently than on GitHub itself.

Markdown Preview

Overview

A split-pane Markdown editor: type in the left pane and the right pane shows the rendered result immediately. Parsing is done by marked and every render is sanitized with DOMPurify, so embedded HTML cannot inject scripts into the page. Useful for drafting READMEs, checking how a snippet will render, or debugging Markdown syntax.

How to use

Type or paste into the Markdown pane — it starts with a small sample document.
Watch the Preview pane update on every keystroke.
Iterate until the output looks right, then copy your source from the left pane.

Examples

**bold** and _italic_ → bold and italic text in the preview
`inline code` and fenced ``` blocks render with monospace styling
[links](https://example.com), # headings, and - list items render as clickable links, headings, and bullet lists

Notes

The preview approximates final appearance; GitHub, GitLab, and static-site generators each apply their own CSS and extensions, so spacing and advanced syntax may differ on the destination platform. Raw HTML that DOMPurify deems unsafe is silently removed from the preview.