Text
Markdown Preview / HTML ↔ Markdown
Live preview of Markdown as formatted HTML, plus two-way conversion: Markdown → HTML and HTML → Markdown.
Markdown is a lightweight markup language that formats text with plain characters (**bold**, # heading, - list) and stays readable even unrendered. This tool gives you a live preview of Markdown as HTML and converts in both directions.
How to use it
- Preview: write Markdown on one side — the formatted result appears immediately on the other.
- Markdown → HTML: get ready-to-use HTML markup to paste into a page or an email template.
- HTML → Markdown: paste HTML markup to get its Markdown equivalent — handy for moving content into a README or a Markdown-based CMS.
Common uses
- Writing a README.md for a GitHub repository with a live preview of the formatting.
- Preparing text for a CMS or documentation system that accepts Markdown.
- Quickly turning HTML copied from a webpage into clean Markdown for notes.
Things to keep in mind
Different platforms (GitHub, GitLab, Discord) support slightly different Markdown extensions (tables, strikethrough, checkboxes) — the base syntax is the same everywhere.
Converting HTML to Markdown loses whatever Markdown can't express: complex layout, inline styles, deeply nested elements.
Article about this tool: Markdown: why plain-text syntax beat rich text editors
Frequently asked questions
What conversions are offered?
Three modes are available: a live preview of Markdown rendered as formatted HTML, an explicit Markdown → HTML conversion, and a reverse HTML → Markdown conversion.
Which Markdown rendering engine is used?
It's a simple client-side Markdown rendering in JavaScript, unrelated to any particular server-side templating engine like Blade or Twig; the result reflects standard Markdown, not framework-specific syntax.
Is my Markdown or HTML content sent to a server?
No, conversion and preview happen entirely in the browser, no content is transmitted online.
Why does the same file look different across different apps?
The original Markdown spec doesn't define tables, strikethrough text, or syntax highlighting in code blocks — these are extensions from various implementations. GitHub Flavored Markdown and the CommonMark specification handle some ambiguous cases differently, so rendering of the same file can differ depending on the parser.
What gets lost when converting complex HTML to Markdown?
HTML supports far more formatting options than basic Markdown, so complex tables, nested styles, or non-standard markup can get simplified or lost in the reverse conversion.