Markdown Preview

You write Markdown in the editor pane and a rendered HTML preview updates as you type. The renderer follows the conventions you already know from GitHub: # through ###### for headings, **bold** and *italic*, fenced code blocks with triple backticks, ordered and unordered lists, links, images, blockquotes, horizontal rules, and pipe tables.

Key things it handles:

• Live rendering so you never guess how output will look
• Fenced code blocks with language hints, e.g. ```js
• Tables using the | and --- pipe syntax
• Task lists with - [ ] and - [x]
• Export to HTML that you can save or paste into another document

Because parsing happens in the browser, the preview reacts instantly with no network round-trip. Paste an existing README in and it renders immediately, which is a quick way to sanity-check a file before committing it.

Say you're drafting a short README section. You type this in the editor:

## Install

Run the following:

```bash
npm install my-tool

• Works offline
• Cloud sync

The preview shows a real `Install` heading, the shell command in a monospace block with its own background, a two-column table with a header row, and a checklist where the first item is ticked and the second is empty. If you forget a pipe or misalign the `---` separator row, the table breaks visibly in the preview, so you catch the mistake before it ships. Once it looks right, export the HTML and you have a portable copy of exactly what you see.

Markdown Preview fits anywhere you write Markdown but don't have a live preview handy:

• READMEs and docs - check headings, code blocks, and tables before pushing to a repo.
• Issue and PR descriptions - draft a comment, confirm the formatting, then paste it in.
• Release notes and changelogs - keep a consistent structure and verify lists render cleanly.
• Email and CMS content - write in Markdown, export HTML, paste into a system that accepts raw HTML.
• Learning Markdown - type a snippet and immediately see what each symbol does.
• Quick sanity checks - paste a file someone sent you to confirm it renders the way they intended.

It's especially handy when you're editing on a machine without your usual editor or extensions. Open the page, paste, and you have a working preview in seconds.

A few things that trip people up:

• Blank lines matter. Markdown needs an empty line between a paragraph and a list, a heading, or a code block. Without it, the list or block may merge into the paragraph above.
• Tables need a separator row. The |---|---| line directly under the header is required. Leave it out and the whole table renders as plain text.
• Indentation creates code blocks. Four leading spaces turn a line into a code block, which surprises people who indent for readability.
• Use fenced blocks for code, not inline. Single backticks are for short inline snippets like git status; triple backticks are for multi-line code.
• Hard line breaks need two trailing spaces or a blank line. A single newline inside a paragraph is usually collapsed.
• Escape literal characters with a backslash, e.g. \* to show an asterisk instead of starting italics.

Markdown is a plain-text syntax that maps to a subset of HTML. ## Title becomes <h2>Title</h2>, **bold** becomes <strong>bold</strong>, and a fenced code block becomes a <pre><code> pair. The point is readability: the source is legible on its own, and it converts to clean HTML predictably.

Most Markdown flavors, including the GitHub style this tool follows, also let you drop raw HTML inline when Markdown can't express what you need. For example, you can write <sub>subscript</sub> or a <details> block directly in your Markdown and it passes through to the output. That's useful for collapsible sections, alignment with <div align="center">, or anything beyond the core syntax. When you export, you get the fully expanded HTML, so what renders in the preview is what you take with you.