What is rendered

The converter uses the marked library with GitHub-flavored Markdown enabled. ATX headings, fenced code, tables, strikethrough, autolinks and task lists follow that dialect. Paragraphs are wrapped in p. Inline code stays code. A link is an anchor with the href you wrote. Images become img tags. The output is a fragment, not a full document: there is no html or body wrapper, so you can drop it into a layout you already have. Line breaks inside a paragraph follow Markdown rules, which means a single newline is usually a space, not a br.

Safety

Marked does not execute the Markdown, but raw HTML inside the Markdown is part of the dialect and can appear in the output. If you paste untrusted comments, run the HTML through a sanitizer before you insert it into a page. This tool does not add rel=noopener for you on every link. The in-page preview assigns the HTML to a sandboxed view so you can see headings and lists. Do not treat the preview as a security boundary for hostile input. For a document you wrote yourself, copying the fragment is the whole job.

Worked example

The sample heading becomes h1. The word world is strong. The guide is an anchor pointing at https://example.com. The two items become a ul with two li elements. There is no extra wrapper div. Fenced code, if you add it, becomes pre and code. A pipe table becomes a table element. The sibling HTML to Markdown page walks the other direction and will not preserve every tag choice, so do not round-trip a carefully hand-written fragment and expect the same bytes.

Why local

Draft release notes often mention unreleased names. Rendering them locally means the draft is not posted to a preview host just to see the HTML. The same page is useful when a static site generator is too heavy for a one-off fragment you need to paste into a CMS that stores HTML. Pair it with the CSV to Markdown table page when the document is mostly a table.

Frequently asked questions