HTML to Markdown Converter

HTML to Markdown Converter

What this HTML to Markdown converter does

This page turns HTML into Markdown. It sanitizes the input first, then converts supported elements such as headings, paragraphs, lists, links, images, tables and code blocks into Markdown syntax. You can paste HTML or fetch it from a public URL, then copy or download the converted .md file. It is useful for migrating a small page, cleaning up a CMS export or turning an email into documentation.

Sanitization happens first

Before conversion, the HTML is passed through a sanitizer. That step removes scripts, iframes, comments and some structural elements such as sections and articles, and it can drop attributes it does not allow. Sanitization is a safety measure, but it also means the output may not contain everything from the source. If a script, embedded video or custom widget disappears, that is expected behaviour, not a conversion bug.

Supported elements

Headings, paragraphs, emphasis, strong text, links, images, lists, blockquotes and code blocks generally convert well. Tables are supported, but complex tables with merged cells or nested content may lose structure. Inline styles are not translated into Markdown. A styled div becomes plain text or is removed, and CSS classes do not carry over. The converter focuses on semantic HTML, not visual fidelity.

How to use it

Paste the HTML into the editor, or use the URL tab to fetch a public page. Press convert. The Markdown appears in a read-only editor. Use copy for the clipboard or download for a `.md` file. The input limit is 200,000 characters. For a full website, convert one page at a time and check the result; a whole site has navigation, scripts and repeated boilerplate that need separate handling.

What happens to links and images

Links become Markdown link syntax, and images become image syntax with their source URL. Relative URLs stay relative unless the converter resolves them against a base URL; check the output if the Markdown will live in a different path. Alt text may be preserved, but decorative or missing alt text is not invented. A link with a JavaScript href may be dropped or left as plain text.

Code, tables and whitespace

Preformatted code and code blocks are usually preserved, but syntax highlighting classes are not. Tables become pipe tables where possible; merged cells, captions and footnotes may be lost. Consecutive spaces and line breaks are normalized in many HTML-to-Markdown conversions, so a layout that depends on precise whitespace may change. Review the Markdown source, not only the rendered preview.

When this is useful

Use it to move a blog post, a help article, a README source or a simple email into a Markdown-based system. It is also handy for turning a snippet of HTML into readable documentation. It is not a website scraper, a PDF converter or a full CMS migration tool. For a large content migration, use a script with a tested converter and a review step.

Limits and server processing

The HTML is sent to the Newisty server for sanitization and conversion. The input limit is 200,000 characters. URL fetch happens on the server, so private or login-protected pages will not work. The converted Markdown is returned to the browser; the page does not publish it or store it permanently. Download the file if you need a copy.

Privacy and sensitive content

Do not paste private emails, internal documents or pages containing credentials unless you accept server processing. The sanitizer removes scripts, but it does not make the content confidential. If the HTML contains personal data, the server still receives it before conversion. Use a local converter for sensitive material.

Common problems

If the output is mostly plain text, the source may rely on divs and CSS instead of semantic headings and lists. If a table is broken, check for merged cells or nested tables. If images are missing, check whether their sources were relative or stripped. If a URL fetch fails, the page may require login or render its content with JavaScript. If the request is rejected, the input may exceed 200,000 characters.

Quality checks

Read the Markdown source and compare it with the original page. Check heading levels, link targets, image alt text, table columns and code fences. Look for lost footnotes, captions and nested lists. Render the Markdown in the target system, because a preview in one editor can hide problems that appear in another. Fix the source HTML if the conversion repeatedly loses an important structure.

What not to do

Do not use the converter as a security filter for untrusted HTML. Do not expect scripts, iframes or embedded widgets to survive. Do not assume visual styling will become Markdown. Do not paste confidential content without checking the privacy implications. Do not convert a whole site blindly; review each page and keep the original HTML until the migration is verified.

Migrating a page in stages

A single conversion rarely produces a finished document. Convert the main article first, then add the navigation, images and cross-links by hand. Keep the original HTML until the Markdown has been reviewed in the target system. Compare heading levels, link destinations and image alt text, not just the visible words. If the source uses a layout table for design, replace it with normal paragraphs and lists instead of trying to preserve the grid. For a repeated template, build a small test set of pages and fix the converter settings before converting the rest.

Working with generated HTML

HTML produced by a page builder is often full of wrapper divs, inline styles and tracking attributes. The converter may keep the text but drop the structure, so the Markdown can look flatter than the original. Start from the most semantic part of the page and remove repeated headers, cookie banners and footers before converting. If the source is available as Markdown or a clean export, use that instead. Conversion is a convenience, not a substitute for cleaning up the content model.

Frequently Asked Questions