HTML Tools

Most HTML tool sites scatter each function across separate pages, so cleaning a Word paste, minifying it, and converting it to Markdown means three tabs and three pastes. This workbench keeps everything in one Monaco-powered editor: pick a tool from the tab bar, and your input stays put when you switch. Every tab is deep-linkable (#minify, #encode, #viewer), each transform runs live as you type, and the stats bar shows input size, output size, and the exact percentage saved or added.

Turns minified or messy markup into clean, consistently indented code — 2 or 4 spaces, your call. It handles the cases naive indenters break: void elements like <img> never drift the indentation, <pre> and <textarea> content passes through byte-for-byte, inline elements stay on their lines so no visible spaces appear, and embedded CSS and JavaScript are formatted with their own language rules.

Strips comments, collapses whitespace runs, and removes the spaces between block-level tags — the characters browsers never needed. Content inside <pre>, <textarea>, <script>, and <style> is protected and restored untouched, and conditional comments survive. A typical page loses 5–20% of its raw size; the stats bar shows your exact number. Pair it with gzip or Brotli on the server for the full saving.

Paste from Microsoft Word or Google Docs and get semantic HTML back. The cleaner strips what Office leaves behind:

Escape the five reserved characters (& < > " ') to entities, or decode any entity back to text — named, decimal, and hex formats supported, with a swap button to flip direction. Decoding uses the browser's own parser, so every named entity in the HTML spec resolves correctly. Use it to display code as text, fix double-encoded &amp;amp; strings, and clean up scraped content.

Both directions with GitHub Flavored Markdown: tables, task lists, strikethrough, and fenced code blocks with language hints. HTML to Markdown runs on Turndown, the engine trusted by Joplin and the Obsidian ecosystem; Markdown to HTML runs on Marked, one of the most widely used Markdown engines in JavaScript. Typical jobs: migrating CMS content into Hugo or Astro, preparing scraped pages for LLM pipelines where Markdown costs fewer tokens, and publishing README content as web pages.

Converts markup into JSX that compiles inside a React component — one of the most-reached-for tools among React developers converting templates, emails, or documentation snippets:

Strips every tag and returns readable plain text. Script and style contents are deleted outright, entities are decoded (&amp; becomes &, double-encoded sequences collapse), and block elements become line breaks so paragraphs survive. Use it to extract article text, prepare content for word counts or NLP, and de-HTML CMS exports.

Live structural checking as you type: unclosed tags, mismatched closing tags, and unexpected closers are flagged as errors; a missing DOCTYPE, missing html/head/body, and deprecated tags like <font> and <center> surface as warnings. Each issue is a clear one-line message, and the counter in the stats bar tracks errors and warnings as you fix them.

A full code editor on the left, the rendered page on the right, updating as you type. Scripts execute inside a sandboxed frame that has no access to this page or your data, so running tutorial examples and testing snippets is safe. It is the quickest way to answer "what does this markup actually look like" without creating a file.

Ten tools in one editor: HTML Formatter (beautifier), HTML Minifier, HTML Cleaner, HTML Encoder/Decoder, HTML to Markdown, Markdown to HTML, HTML to JSX, HTML to Text, HTML Validator, and a live HTML Viewer. Switch between them with the tabs above the editor — your input carries over, so you can clean a snippet, then minify it, then convert it without pasting three times.

No. Every tool runs entirely in your browser with client-side JavaScript — minifying, formatting, converting, and validating all happen on your machine. You can verify it: open your browser's developer tools, switch to the Network tab, and run any conversion. No requests carry your code. That is also why there are no size limits and no rate limiting.

Yes, with one caveat most online minifiers ignore: whitespace inside <pre>, <textarea>, <script>, and <style> is content, not formatting. This minifier protects those blocks and restores them byte-for-byte, keeps conditional comments, and only fully removes spaces between block-level tags — between inline elements like links, a space is visible text, so it collapses to a single space instead of disappearing.

They are opposite directions of the same transform. Beautifying adds indentation and line breaks so humans can read the markup; minifying removes them so browsers download fewer bytes. A healthy workflow uses both: readable source, minified output. Here they are two tabs apart, and the stats bar shows exactly how many bytes each direction adds or saves.

Open the Beautify tab and paste the minified code. The formatted version appears live with each nested element on its own line, indented by 2 or 4 spaces — your choice. Embedded <style> blocks are formatted as CSS and <script> blocks as JavaScript, using the js-beautify engine that powers the most established formatters on the web.

Encoding (also called escaping) replaces reserved characters with entities — < becomes &lt; — so they display as text instead of being parsed as markup. Decoding reverses it. The Encode/Decode tab does both directions with a swap button, and outputs named (&amp;), decimal (&#38;), or hex (&#x26;) formats. Decoding runs on the browser's own parser, so all 2,000+ named entities in the HTML spec are supported.

Yes. The HTML to Markdown tab includes GitHub Flavored Markdown support, so tables become pipe tables, strikethrough survives, and checkbox lists become - [x] task lists. One limit comes from Markdown itself: cells that span rows or columns have no Markdown equivalent and are flattened. The reverse direction, Markdown to HTML, supports the same GFM features and adds a rendered preview.

Everything React requires to make HTML compile as JSX: class becomes className, for becomes htmlFor, attributes like tabindex are camelCased, inline style strings become style objects, void tags like <br> and <img> self-close, and HTML comments become {/* JSX comments */}. It converts syntax, not logic — inline event handlers keep their original strings, so wire up real React handlers yourself.

It is built for markup pasted from Microsoft Word or Google Docs: inline style attributes, class and id attributes, comments including Word conditional comments, Office namespace tags like <o:p>, embedded style blocks, scripts, and empty wrapper spans and font tags. What remains is clean semantic markup that inherits your site's stylesheet instead of fighting it.

It checks document structure: unclosed tags, mismatched closing tags, and unexpected closing tags as errors, plus warnings for a missing DOCTYPE, missing html/head/body, and deprecated tags like <font> and <center>. It is a fast structural checker for everyday debugging, not a full W3C specification validator — for spec-level conformance, use validator.w3.org as the final gate.

Yes. The Preview tab renders your HTML live in a sandboxed frame next to the editor as you type — scripts run inside the sandbox only, so testing snippets is safe. The Formatter, Cleaner, and Markdown to HTML tabs also offer a rendered preview of their output, which is the fastest way to confirm a transform did not change what users see.

Everything is free with no account, no ads, and no usage limits. Each tab has a shareable deep link — /html#minify opens the Minifier, /html#html-to-jsx opens the JSX converter, and so on — so you can bookmark or share exactly the tool you mean.