Markdown Preview
- Write or paste your Markdown into the editor.
- The preview updates as you type.
- Copy the generated HTML, or keep editing until the result looks right.
The parser runs in GitHub Flavored Markdown mode, which adds tables, strikethrough with double tildes, task lists with brackets and automatic link detection on top of original Markdown.
The automatic line break option is off. That means a single newline does not produce a visual break — the original Markdown behaviour. To force one, leave a blank line or end the line with two spaces.
Headings, emphasis, lists, blockquotes, code blocks, images and links all work the conventional way.
Markdown allows embedded HTML, and that is a genuine attack vector: a document from a third party can carry a script tag or an event attribute that runs code in the viewer’s page.
So the generated HTML is sanitized before it is displayed. Only a closed list of elements survives — headings, paragraphs, lists, tables, code, links and images — along with a few attributes such as href, src, alt and title.
In practice, if you paste a script tag into the editor it comes back stripped in the preview. That is not a limitation, it is deliberate protection.
If you render Markdown from untrusted sources in your own application, this sanitization step is mandatory. Parsing Markdown without it is a vulnerability.
Everything runs in your browser. The text is never sent to a server or logged, which makes the tool suitable for internal drafts or an unpublished README.
Frequently asked questions
Because automatic line breaks are off, following original Markdown. Use a blank line between paragraphs, or end the line with two spaces.
Sanitization removes anything outside the allowed element list. Script tags, iframes and event attributes are dropped to prevent code execution.
Very closely, since GFM mode is on. Differences can appear in GitHub-specific extensions such as user mentions and issue references, which are not part of the specification.
Yes, using the pipe syntax with a row of hyphens separating the header. That is part of GFM.
No. Parsing and sanitization happen in your browser.