Are my files uploaded to a server?

No. Conversion happens entirely inside your browser and file contents are never transmitted. The single exception is importing by URL, which passes through a server to fetch that page on your behalf.

Will the downloaded HTML still look right somewhere else?

Yes. Styles are written into the exported file, so it keeps its formatting even offline, and any images you supplied are embedded in the file.

Can it convert HTML back into Markdown?

Yes. Drop an .html file, paste HTML source, paste content copied from a web page, or fetch a page by URL. All four routes are supported.

Do tables and code blocks break?

No. GFM tables stay tables and fenced code keeps its language tag in both directions, including when converting back into Markdown.

It is free and needs no account, with no limits on any feature. Hosting is covered by a single ad slot below the tool, and exported files never contain ads.

How to use & FAQ

This page covers what the Markdown ↔ HTML converter can do, how to use it, and the questions people ask most often.

What it does

Both directions. It converts Markdown to HTML, and it converts existing HTML — or content copied straight out of a web page — back into Markdown.
Tables, code, diagrams and math survive. GFM tables and task lists, syntax-highlighted fenced code, Mermaid diagrams and LaTeX math (KaTeX) are all preserved rather than flattened into plain text.
One file, images included. Drop in the images your document references and they are embedded into the HTML. Move that single file anywhere and the pictures come with it.
Several files at once. Drop a batch of .md or .html files, step through them one by one, then download them individually or all together as a ZIP.
Print and save as PDF. The result is styled for print, so you can send it to a printer or save it as a PDF without any extra step.
Import from a URL. Enter a web address and the page content is fetched and turned into Markdown for you.

How to use

Drag a Markdown or HTML file anywhere onto the window. You can also pick files with the Choose files button on the left, or simply type or paste into the middle pane.
Watch the result appear on the right. The direction is chosen from the file extension, and you can override it with the buttons at the top.
If your document contains images, drop those files in too. They are matched to the document by file name.
Export from the controls at the bottom: Download HTML, Copy source, Print / PDF, or Download all as ZIP.

FAQ

Are my files uploaded to a server?: No. Conversion happens entirely inside your browser and file contents are never transmitted. Once the page is open it keeps working even without a network connection. The single exception is importing by URL, which passes through a server in order to fetch that page on your behalf.
Will the downloaded HTML still look right somewhere else?: Yes. Styles are written into the exported file, so it keeps its formatting even when opened offline. If you supplied images, they are embedded in the file and travel with it.
Can it convert HTML back into Markdown?: Yes. Drop an .html file, paste HTML source, or paste content you copied out of a web page and it is converted back to Markdown with the formatting intact. You can also fetch a page by entering its address.
Do tables and code blocks break?: They are built to survive both directions. GFM tables stay tables and fenced code keeps its language tag, including when converting back into Markdown.
How are diagrams and math handled?: Mermaid diagrams are rendered to images before export, so the downloaded file needs no extra software to display them. Math is typeset with KaTeX. If a document contains neither, those engines are never downloaded, which keeps the page light.
Is it free?: It is free and needs no account, with no limits on any feature. Hosting is covered by a single ad slot below the tool; the converter itself and the files you export never contain ads.

Why convert Markdown to HTML at all

Markdown is a format for the person writing. A single # makes a heading and a single - makes a list, which keeps you focused on the text. The reader's situation is different. GitHub and Notion render those characters for you, but the moment a file leaves that context the recipient gets raw symbols. Converting to HTML moves a document from "easy to write" to "easy to read".

That is why this tool puts weight on producing a single file. If you still have to ship a CSS file alongside it, or a folder of images, the recipient's job has not really gotten easier.

Why nothing is uploaded

A converter receives other people's documents by definition — internal memos, unpublished drafts, contracts. Making those pass through a server means asking you to trust that server. Doing the work inside the browser removes the need to trust anything in the first place.

The preview pane is isolated for the same reason. If someone's Markdown contains a script, it does not run in this page. Using a tool should never be the thing that causes the problem.

Why tables and code so often break

Markdown does not have one official standard. Tables, task lists and strikethrough were not in the original spec — they are GitHub's extension (GFM). Depending on which flavour a converter follows, the same document comes out differently. This tool follows GFM: tables stay tables and fenced code keeps its language tag.

The reverse direction has the same problem. Many converters flatten HTML tables into paragraphs, which leaves you fixing them by hand. Here a table comes back as a table, and code comes back as a fenced block with its language.

Back to the converter