Is my Markdown uploaded?
No. Rendering happens in the browser tab with no network requests.
Paste Markdown, get HTML. Tables, code fences, task lists. Output is sanitised. Nothing uploaded.
Drop files here or
Markdown allows raw HTML inline. That is a feature until someone pastes a document containing a `<script>` tag, and now the HTML you are about to publish to your own site carries an injection. Any Markdown to HTML converter that passes HTML straight through is a liability if you send a CMS the output.
This converter renders with Marked and then runs the result through DOMPurify, so script tags, event handlers and javascript: URLs are stripped while ordinary markup, tables and code blocks survive intact.
What is supported, and what the sanitiser removes.
| Rendering behaviour | Behaviour | Notes |
|---|---|---|
| Parser | Marked | CommonMark plus GitHub tables, task lists and fenced code with language classes. |
| Sanitiser | DOMPurify | Script tags, inline event handlers and javascript: URLs are removed from the output. |
| Tables | GitHub-flavoured | Pipe tables render as real table markup. |
| Code blocks | Fenced, language class | A fenced js block produces a code element with the language-js class, ready for a highlighter. |
| Output | HTML fragment | A body fragment, not a full document, which is what a CMS field wants. |
| Live preview | As you type | Rendered output updates without a round trip because nothing leaves the page. |
Markdown permits inline HTML. If you convert a stranger's file and publish the result, you have published their script tags.
This is CommonMark plus GFM. Custom syntax extensions do not render.
Mixed tabs and spaces break indented code blocks. Use fenced blocks instead.
Raw HTML passes through the parser, so an HTML document produces itself back. That is not a conversion.
Images stay relative. If the HTML goes somewhere else, the paths break.
No. Rendering happens in the browser tab with no network requests.
It is sanitised with DOMPurify, so script tags and event handlers are stripped. Still review before publishing to a CMS.
Yes, GitHub-flavoured pipe tables render as real tables.
Code fences produce language class names but no highlighting. Add a highlighter on your site.
No, an HTML fragment, which is what you paste into a CMS field.
No. This is one direction only.
Yes, `- [ ]` and `- [x]` render as checkbox markup.
Yes, from the results panel.
FileKit Desktop runs every conversion locally as a single offline file — no 10-file limit, batch conversion, and no network connection required. One-time $19, no subscription.
See FileKit Desktop — $19