Start with the outline
A useful draft has a visible hierarchy. Put one main heading at the top, then use second-level headings for the major parts and third-level headings only for real subdivisions. Headings describe relationships; they are not a way to make an isolated line look larger.
Write the direct answer first and keep each paragraph centered on one idea. Lists work well for parallel items or a sequence of steps. A numbered list implies an order; an unordered list does not. Previewing the outline often reveals a missing step before you spend time polishing individual sentences.
Try a small syntax sample
Start a line with # and a space for a main heading. Use ## for a section, a dash and a space for a list item, and a greater-than sign for a quote. Wrap a short phrase in two asterisks for emphasis in bold, or one for italics. Keep code inside inline backticks or a fenced code block.
Our preview supports this small, documented subset. It does not implement every CommonMark edge case or every extension used by GitHub, a wiki or a publishing platform. Tables, images and raw HTML are intentionally excluded. When a target platform has extra syntax, check that platform’s preview rather than treating this tool as a complete compatibility test.
Try it with your own input
Your result
Keep text from becoming executable code
A preview turns source text into HTML. That makes the boundary between text and markup important: an angle-bracket sequence in a draft should not unexpectedly create an executable element. This tool escapes raw HTML before constructing its supported elements, and permits only the documented URL schemes in links.
Try a literal script tag in the editor. It should appear as text, not run. A JavaScript-scheme link should not become a clickable executable link. This is a practical demonstration of the tool’s behavior, not a claim that every Markdown renderer is safe by default. Different renderers and application settings make different trust decisions.
Make links useful to readers
Use link text that describes the destination. A sentence containing “read the CSV conversion guide” is easier to understand out of context than a sentence with several identical “click here” links. Check that an internal link starts with the intended root path and that an external link uses the expected domain.
Encoding a URL value is different from escaping HTML. The encoding guide explains when percent encoding is appropriate. Do not repeatedly encode an entire link until it appears to work: that can hide a bad boundary between a URL, a component and a document.
Review the exported fragment
The Copy HTML control exports a fragment with headings, paragraphs and the supported inline elements. It does not add a complete HTML document, a stylesheet or application-specific metadata. When inserting it into another page, inspect how that page styles headings, links, lists and code.
Before publishing, test a narrow screen, keyboard navigation and long code lines. Count the final draft with the Word Counter if you have a length target. Save the original Markdown alongside the exported HTML so future edits remain straightforward; a rendered fragment is a result, not your only editable source.
Common questions
Is this a full CommonMark renderer?
No. It is a small documented dialect for headings, paragraphs, lists, quotes, code, emphasis and links.
Can I embed HTML or a video?
Raw HTML is displayed as text. Embeds and remote images are not supported in this preview.
Why does my GitHub preview look different?
GitHub supports extensions and rendering rules that this small preview does not implement. Check the target platform for publication.
What does Copy HTML export?
It exports an HTML fragment. Add a full document wrapper and your own styles if you need a standalone page.
Where is the draft stored?
Only in this tab’s memory. The tool does not autosave or upload it; download or copy it before closing.