Loading HTML to Markdown Converter...
Please wait a moment

Converting HTML to Markdown - A Quick Walkthrough

Step 1

Add Your HTML

First things first, get your HTML into the box. Web pages, email templates, exported docs, whatever you have, turning it into Markdown makes it far lighter to carry around and edit. Once it's converted you can keep polishing it in the Markdown editor or preview it in the Markdown viewer. There are a few ways to add it:

Just paste it: Drop your HTML straight into the input box
Open a file: Use "Upload" to pull in an .html or .htm file from your machine
Take it for a spin: Hit "Sample" to load some example HTML and see the conversion happen

Example: What You Paste In

A snippet of everyday HTML:

<h1>Welcome to My Project</h1>

<p>This is a <strong>simple</strong> paragraph.</p>

<ul>
  <li>First item</li>
  <li>Second item</li>
</ul>
Step 2

The Conversion Happens on Its Own

There's nothing to click. The moment your HTML is in, the converter gets going. Afterwards you can smooth out the result with the Markdown formatter if anything needs tidying. During the conversion the tool:

Reads the structure: Picks out headings, paragraphs, lists, links, and code blocks
Writes tidy Markdown: Produces proper Markdown syntax with the HTML tags stripped out
Keeps your formatting: Bold, italic, links, images, and nested lists all come along
Trims the clutter: Drops leftover HTML attributes and inline styling you don't need

Example: What Comes Back

That HTML, now rendered as clean Markdown:

# Welcome to My Project

This is a **simple** paragraph.

* First item
* Second item
Step 3

Look Over the Markdown

Give your fresh, portable Markdown a read-through. From here you can take it further with the Markdown to JSON or Markdown to plain text converters. What you'll get is:

Nothing but Markdown: Not an HTML tag in sight, only clean Markdown
Goes anywhere: Plays nicely with GitHub, GitLab, docs platforms, and static site generators
Lighter to work with: Far quicker to update and version-control than tag-heavy HTML
Step 4

Save or Share Your Markdown

Your Markdown is ready to move on. Want a printable copy instead? Send it over to the Markdown to PDF tool, or lay out a fresh table in the Markdown table generator. Whichever way you go, exporting is quick:

Copy in a tap: Grab the whole thing at once and drop it straight into your docs, wiki, or CMS
Save it locally: Download a .md file to keep on hand for a README, notes, or a blog draft
Drops in anywhere: Works out of the box with GitHub, Jekyll, Hugo, Gatsby, and every other Markdown engine

HTML to Markdown at a Glance

Short on time? Here's the cheat sheet for how the tags you'll see most often come out the other side.

<h1>Title</h1># Title
<strong>bold</strong>**bold**
<ul><li>item</li></ul>- item
<a href="url">text</a>[text](url)
<code>code</code>`code`
<blockquote>text</blockquote>> text

Keep this handy while you're checking output, then smooth over anything unusual in the Markdown editor.

What Actually Happens to Your Markup

My HTML was copied straight out of Word or Google Docs. Will the output be a mess?

It shouldn't be. Markup pasted from Word or Google Docs usually drags along a pile of mso-* styles, redundant <span> wrappers, and font declarations nobody asked for. None of that has a Markdown equivalent, so it gets left behind, and you're left with the actual headings, lists, and paragraphs. If a stray artifact slips through, a quick pass in the Markdown formatter tidies it up.

Do inline styles and class names carry over into the Markdown?

No, and that's by design. Attributes like style, class, id, and data-* only ever describe presentation, and Markdown has no place to put them. What survives is the meaning underneath, the heading is still a heading, the bold text is still bold, just without the CSS baggage riding along.

What happens with nested tables or a stack of wrapper <div>s?

Layout <div>s collapse away since they're just containers with nothing for Markdown to hold onto, leaving the text they wrapped behind. A table sitting inside another table is trickier: the outer grid becomes a Markdown table, but Markdown tables can't nest, so anything inside an inner table gets flattened into plain text within that cell. For anything elaborate, it's worth double-checking the result and rebuilding tricky grids by hand in the Markdown table generator.

Are HTML comments kept, or thrown away?

Thrown away. A <!-- comment --> is a note left for whoever edits the HTML later, not something meant for a reader, and Markdown has no syntax for it anyway, so it's dropped along with the rest of the invisible markup.

How are <br> tags and non-breaking spaces handled?

A <br> becomes a line break inside the paragraph it sits in, rather than starting a brand-new one. A non-breaking space (&nbsp;) gets turned into a regular space, since Markdown readers rarely need text glued together the way a web page sometimes does, and a normal space wraps far more predictably.

Can I paste in an entire saved webpage, or only a fragment?

Either works. Hand it a full page and it reads through the <body>, skipping <head>, <script>, and <style> blocks since none of those have anything Markdown can represent. Hand it a two-line snippet and it converts just as happily. Once you've got a result you like, preview it in the Markdown viewer before you ship it anywhere.

Any cost, sign-up, or size limit I should know about?

None of the above. It's free, there's no account to create, and no cap on how much HTML you feed it or how many times you come back. Convert one snippet or fifty full pages, the output quality doesn't change either way.