🔒 Processed locally in your browser — no data uploaded
← Back to Home

Markdown Preview

Markdown Input
Preview

What the Markdown Preview does

Markdown Preview is a two-pane editor: source on the left, rendered document on the right. Typing in the left pane redraws the preview immediately, so headings, lists and code blocks appear as you write them rather than after a save. The right pane is styled with the GitHub dark markdown stylesheet, which gives a close reading of how a README section will look once it is published.

The renderer handles headings in three levels, bold and italic, inline code, fenced code blocks, links, images, bullet lists, blockquotes, horizontal rules, and paragraphs split by blank lines. Source text is escaped before rendering, so angle-bracket tags show up as literal characters instead of turning into elements. The box loads with a short sample document covering that syntax, and there is no server call anywhere in the pipeline.

How to use it

  1. Type or paste MarkdownPut the document in the left pane, replacing the sample text. The preview reads that box on every input event, so there is no render button to press and no save step.
  2. Watch the right paneThe rendered result updates as you type. Keep both panes side by side on a wide screen; in a narrow window they stack and you scroll between source and result.
  3. Compare against real outputRendering uses the GitHub dark markdown stylesheet, so heading sizes, code backgrounds and quote shading match that look. That makes the page useful when drafting a README or docs page destined for GitHub.
  4. Copy what you needThere is no export or download control. Select text from the preview pane to copy rendered content, or copy the source out of the left pane and paste it into your own file.

Options and formats

Heading levelsOne, two and three hash marks map to h1, h2 and h3. Deeper levels are not converted and will show as literal hash characters inside the preview.
EmphasisDouble asterisks give bold, single asterisks give italic, and three give both together. Underscores are not converted, so stay with asterisks if the formatting matters.
CodeBackticks mark short inline snippets; triple-backtick fences wrap multi-line blocks and accept a language tag, which is parsed but never used for colouring. A fence needs a closing line.
Links and imagesSquare brackets with a URL in parentheses make a link that opens in a new tab; adding a leading exclamation mark to the same syntax loads an image from that URL instead.
Lists, quotes and rulesDash or asterisk lines become bullet items, a leading angle bracket makes a quote block, and three dashes alone on a line draw a horizontal rule.

Things to watch out for

Numbered lists stay as textOnly dash and asterisk bullets become list items. A numbered outline renders as ordinary paragraphs with the digits visible in the prose, so switch to bullets or check the order in another editor.
Tables are not convertedPipe tables come out as a block of plain text with every pipe and dash still showing. If the document depends on tables, verify it in the tool you will actually publish with.
Indented bullets are skippedThe bullet rule matches lines that begin at the left margin. A nested item indented by a space or two stays literal, so flatten lists while drafting or expect a mixed-looking preview.
HTML tags show as charactersAngle brackets are escaped before rendering, so a pasted div or br appears as visible text rather than markup. That keeps pasted HTML from injecting anything live into the preview pane.

Frequently asked questions

How do I render a multi-line code block?

Open with three backticks on their own line, paste the code, then close with three more. A language name after the opening fence is accepted but ignored, so there is no syntax colouring. Without the closing fence, the backticks and everything under them stay as raw text.

Can I preview tables or task lists?

No. The renderer is a compact regex pass rather than a full CommonMark or GitHub-flavoured implementation. Pipe tables, checkbox lists and footnote syntax fall through as plain text with their markers visible. Check table-heavy documents in the editor you will publish with.

Can I paste HTML and see it rendered?

No, and that is deliberate. The source is escaped before the preview is built, so tags appear as visible characters instead of becoming elements. Nothing you paste turns into live markup or script inside the pane, which makes short snippets safe to inspect here.

Where is the generated HTML?

There is no HTML export. The preview builds elements directly in the page, so the markup exists only as long as the tab is open. When you need an HTML file, copy the source into a converter or a static site generator that writes one out.

Does the sample text come back on reload?

Yes. The left pane is refilled with the bundled sample document every time the page loads, and your edits are not stored anywhere on disk. Copy anything worth keeping into your own file before refreshing or navigating away from the tab.

What is this page best used for?

Quick syntax checks: confirm that a heading level, a fenced block or a link renders the way you expect before you commit a README. It is faster than a full editor for that job, but not a replacement when tables, numbering or chart syntax are involved.