Write and preview Markdown with syntax highlighting, GitHub Flavored Markdown, and export to HTML.
Markdown Live Preview shows Markdown source and its rendered result together, so formatting errors are visible while you type. It supports GitHub Flavored Markdown, syntax highlighting for recognized fenced-code language labels, and HTML export. The most common surprise is paragraph behavior: one ordinary newline inside a paragraph usually appears as a space in the preview. Insert a blank line when you intend to start a new paragraph.
A concrete input and expected output from the current implementation.
Input
# Build status - [x] Parsed - [ ] Published
Expected output
The rendered preview contains a level-one heading reading "Build status", followed by a two-item task list. "Parsed" is checked and "Published" is unchecked.
The leading # creates a level-one heading. Under GitHub Flavored Markdown, [x] and [ ] at the start of list-item content create checked and unchecked task-list items.
Edits in the Markdown input are reflected in the preview. Headings, emphasis, links, blockquotes, lists, tables, task-list items, and fenced code are interpreted as document structure rather than shown as source punctuation. For a fenced code block, place a language identifier after the opening fence to request syntax highlighting; highlighting depends on that identifier being recognized.
HTML export converts the current Markdown document into HTML corresponding to the rendered structure. For example, Markdown headings, paragraphs, strong emphasis, lists, and code blocks become their HTML counterparts instead of retaining the original Markdown markers. Check the live preview first, because the export records the parser's interpretation of ambiguous spacing, nesting, and fence boundaries.
Not necessarily. GitHub Flavored Markdown defines Markdown plus extensions such as tables, task-list items, strikethrough, and extended autolinks, but GitHub pages also apply their own styling and may add repository-aware behavior. Use this preview to check GFM structure, then verify on GitHub when exact appearance, issue linking, or repository-relative paths matter.
No. A fenced block is rendered as code, and a recognized language label can control highlighting, but neither operation establishes that the snippet is valid or produces the claimed result. Run the snippet in the appropriate language environment when execution, compilation, package availability, or runtime output is part of the question.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.