Question 1

How do I convert HTML to Markdown without installing a library?

Accepted Answer

Paste your HTML fragment into jslet's HTML to Markdown converter and the output appears instantly. The tool runs entirely in your browser: it parses the HTML with the browser's own DOM parser, then walks the element tree converting each tag to its Markdown equivalent — h1-h6 to #-######, p to blank-line separated paragraphs, ul/ol to - and 1. lists, a to [text](href), img to ![alt](src), pre/code to fenced code blocks, table to GitHub-flavored pipe tables, blockquote to >, and strong/em/code to **, * and backticks. The output is GitHub-flavored Markdown, so it works directly in GitHub READMEs, GitLab wikis, Notion imports and most static site generators. No server, no upload — the conversion never leaves your browser.

Question 2

Why does my HTML table come out as raw HTML in Markdown?

Accepted Answer

Markdown does not have a native table syntax — GitHub-flavored Markdown (GFM) added pipe tables as a convention, and that is what this tool emits. But if a table cell contains block-level elements (a nested div, a list, or multiple paragraphs), it cannot be represented as a flat pipe row, so the converter falls back to keeping the table as HTML. That is the correct behavior: a GFM pipe table with a block element inside breaks every renderer. If you need a clean table, flatten the cell content first. The same fallback applies to any construct Markdown cannot express — the tool keeps the HTML so nothing is lost, rather than producing broken Markdown.

Question 3

Does this tool work with full web pages or just fragments?

Accepted Answer

Both. Paste a full page and the converter ignores the head, script, style, and nav boilerplate, converting only the meaningful content. Paste a fragment — a single table, a blockquote, an article body — and it converts just that. The DOM parser used is the browser's own, so malformed HTML (unclosed tags, stray attributes) is auto-corrected the same way a browser renders it, which means what you see is what you get: the Markdown matches the rendered page, not the raw source quirks.

Question 4

Is my HTML sent to a server?

Accepted Answer

No. Everything runs in your browser via JavaScript — your HTML never leaves your device. This matters when converting proprietary documentation, internal wikis or client content. Open the Network tab (F12) before converting and you will see zero outbound requests. Free, no account, no usage limits.

HTML →Markdown Converter

🟢📖 What This Converter Does (and What Markdown Can't Do)