HTML Minifier_

Whitespace and comments removed, and nothing else. Attributes keep their quotes, closing tags stay closed, and no attribute is dropped for being empty — every one of those is a saving that some minifiers take and each one has a way of going wrong.

HTML is the one markup on this site where minifying can change what a reader sees rather than only what a parser reads. The space between two inline elements is rendered; remove it and two words run together on the page. Everything here is built around not doing that.

toolkit.codes/html-minifier

Client-Side

Before

—

After

—

Untouched regions

—

Smaller by

—

HTML_In

Minified_Out

UTF-8

Ready

100% LOCAL

Input: Any HTML — a full page, a fragment, or template output. Conditional comments are recognised and kept, because they are instructions rather than notes.
Output: The same markup with collapsible whitespace collapsed and ordinary comments removed. What renders is identical to what rendered before.
Processing: Compacted in this tab by a single pass that parks the regions it must not touch, collapses what is left, and puts them back byte for byte.
Limits: Whitespace and comments only. No attribute-quote removal, no dropping optional closing tags, no minifying of inline CSS or JavaScript — those are real savings and each is a real risk.
Whether it is safe depends on your CSS: A minifier reads your markup and cannot read your stylesheet. Any element styled white-space: pre, pre-wrap or break-spaces renders its whitespace exactly as written — and that styling can arrive from a class, a framework, or a rule three files away. So
and are protected here by name, and anything else you have made whitespace-significant through CSS is something only you know about.</dd></div></dl></section><section class="mt-14 max-w-3xl mx-auto space-y-4"><h2 class="text-lg font-mono font-bold text-foreground">The markup where minifying is visible</h2><h3 class="text-sm font-mono font-bold text-foreground">A space between inline elements is content</h3><p class="text-sm font-mono text-muted-foreground leading-relaxed">HTML collapses runs of whitespace to one space, and that one space is rendered. <code class="text-foreground"><span>Hello</span> <span>world</span></code> shows two words with a gap; delete the space between the tags and it shows <em>Helloworld</em>. Between block-level elements the same whitespace renders as nothing at all and can go freely. So a correct HTML minifier has to know which elements are inline — and that is a list, not a rule, which is why minifiers disagree about the edges of it.</p><h3 class="text-sm font-mono font-bold text-foreground">Four regions that are never touched</h3><p class="text-sm font-mono text-muted-foreground leading-relaxed">Inside <code class="text-foreground"><pre></code> and <code class="text-foreground"><textarea></code>, whitespace is content the browser renders exactly. Inside <code class="text-foreground"><script></code> and <code class="text-foreground"><style></code> it belongs to a different language with its own rules — and JavaScript in particular can have a line break that inserts a semicolon. All four are parked before anything is collapsed and restored byte for byte afterwards, and the count of how many were protected appears above so you can check it matches what you expected.</p><h3 class="text-sm font-mono font-bold text-foreground">Conditional comments are not comments</h3><p class="text-sm font-mono text-muted-foreground leading-relaxed">A comment beginning <code class="text-foreground"></pre></div></div></div><div class="rounded-md border border-border bg-surface overflow-hidden" data-section="usecase"><div class="px-4 py-3 border-b border-border"><h3 class="m-0 font-mono text-sm font-bold text-foreground">A page with a code sample in it</h3><p class="m-0 mt-1 font-mono text-xs text-muted-foreground leading-relaxed">Everything inside pre is content. Collapsing it would reflow the sample and change what the reader sees.</p></div><div class="grid grid-cols-1 md:grid-cols-2"><div class="border-b md:border-b-0 md:border-r border-border/50"><div class="px-4 py-1.5 bg-secondary/30 font-mono text-[9px] uppercase tracking-wider text-muted-foreground">Contains a pre block</div><pre class="m-0 p-3 font-mono text-[11px] text-foreground/80 overflow-x-auto whitespace-pre-wrap break-words"><p>Run this:</p> <pre> npm install npm test</pre></pre></div><div><div class="px-4 py-1.5 bg-secondary/30 font-mono text-[9px] uppercase tracking-wider text-muted-foreground">Collapsed around it, never inside</div><pre class="m-0 p-3 font-mono text-[11px] text-primary/90 overflow-x-auto whitespace-pre-wrap break-all"><p>Run this:</p><pre> npm install npm test</pre></pre></div></div></div><div class="rounded-md border border-border bg-surface overflow-hidden" data-section="usecase"><div class="px-4 py-3 border-b border-border"><h3 class="m-0 font-mono text-sm font-bold text-foreground">An email template with conditional comments</h3><p class="m-0 mt-1 font-mono text-xs text-muted-foreground leading-relaxed">Outlook still reads them. A minifier that treats them as comments removes working behaviour and the failure only shows in one client.</p></div><div class="grid grid-cols-1 md:grid-cols-2"><div class="border-b md:border-b-0 md:border-r border-border/50"><div class="px-4 py-1.5 bg-secondary/30 font-mono text-[9px] uppercase tracking-wider text-muted-foreground">In the template</div><pre class="m-0 p-3 font-mono text-[11px] text-foreground/80 overflow-x-auto whitespace-pre-wrap break-words"> </pre></div><div><div class="px-4 py-1.5 bg-secondary/30 font-mono text-[9px] uppercase tracking-wider text-muted-foreground">One kept, one removed</div><pre class="m-0 p-3 font-mono text-[11px] text-primary/90 overflow-x-auto whitespace-pre-wrap break-all"></pre></div></div></div></section><section class="mt-14 max-w-5xl mx-auto" data-section="reference"><h2 class="text-lg font-mono font-bold text-foreground mb-4">What is collapsed, and what is protected</h2><div class="overflow-x-auto rounded-md border border-border focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-primary" tabindex="0" role="region" aria-label="What is collapsed, and what is protected"><table class="w-full border-collapse font-mono text-sm"><thead><tr class="bg-secondary/40"><th class="px-4 py-2.5 text-left text-[10px] uppercase tracking-wider text-muted-foreground font-bold whitespace-nowrap border-b border-border">In the markup</th><th class="px-4 py-2.5 text-left text-[10px] uppercase tracking-wider text-muted-foreground font-bold whitespace-nowrap border-b border-border">Result</th><th class="px-4 py-2.5 text-left text-[10px] uppercase tracking-wider text-muted-foreground font-bold whitespace-nowrap border-b border-border">Why</th></tr></thead><tbody><tr class="border-b border-border/50 last:border-b-0"><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">Indentation between block elements</td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">Removed</td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">It renders as nothing, so nothing is lost.</td></tr><tr class="border-b border-border/50 last:border-b-0"><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">A space between two inline elements</td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text"><strong>Kept</strong></td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">It renders as a space. Removing it joins two words on the page.</td></tr><tr class="border-b border-border/50 last:border-b-0"><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">Runs of spaces and newlines in text</td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">Collapsed to one</td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">Exactly what the browser does when it lays the text out.</td></tr><tr class="border-b border-border/50 last:border-b-0"><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">Inside <code><pre></code> and <code><textarea></code></td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text"><strong>Untouched</strong></td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">Whitespace there is content, and is rendered as written.</td></tr><tr class="border-b border-border/50 last:border-b-0"><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">Inside <code><script></code> and <code><style></code></td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text"><strong>Untouched</strong></td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">A different language with different rules — and JavaScript can insert a semicolon at a line break.</td></tr><tr class="border-b border-border/50 last:border-b-0"><td class="px-4 py-2.5 align-top text-muted-foreground rich-text"><code></code></td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">Removed</td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">For the author, not the browser.</td></tr><tr class="border-b border-border/50 last:border-b-0"><td class="px-4 py-2.5 align-top text-muted-foreground rich-text"><code><!--[if mso]></code></td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text"><strong>Kept</strong></td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">An instruction rather than a comment. Outlook still acts on these.</td></tr><tr class="border-b border-border/50 last:border-b-0"><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">Attribute quotes, optional closing tags</td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text"><strong>Unchanged</strong></td><td class="px-4 py-2.5 align-top text-muted-foreground rich-text">Real savings with real edges. They belong in a build with tests behind it.</td></tr></tbody></table></div><p class="mt-2 font-mono text-[11px] text-muted-foreground rich-text">The two rows marked as kept for rendering reasons are the ones that go wrong when whitespace is treated as uniformly disposable, and both fail in front of a reader rather than in a validator.</p></section><section class="mt-14 max-w-5xl mx-auto" data-section="tips"><h2 class="text-lg font-mono font-bold text-foreground mb-4">Minifying markup without surprises</h2><ul class="m-0 p-0 list-none grid grid-cols-1 md:grid-cols-2 gap-x-10 gap-y-3"><li class="flex gap-3 font-mono text-sm text-muted-foreground leading-relaxed"><span class="text-primary shrink-0" aria-hidden="true">▸</span><span class="rich-text">Compare the rendered pages, not the source. HTML minification succeeds or fails visually, so a screenshot before and after catches what a diff of the markup will not.</span></li><li class="flex gap-3 font-mono text-sm text-muted-foreground leading-relaxed"><span class="text-primary shrink-0" aria-hidden="true">▸</span><span class="rich-text">Watch for elements you made whitespace-significant in CSS. A rule setting <code>white-space: pre-wrap</code> makes an ordinary div behave like a pre, and no minifier can see your stylesheet.</span></li><li class="flex gap-3 font-mono text-sm text-muted-foreground leading-relaxed"><span class="text-primary shrink-0" aria-hidden="true">▸</span><span class="rich-text">Minify last in the pipeline. Templating engines and post-processors that pattern-match on markup want it laid out; the browser does not care either way.</span></li><li class="flex gap-3 font-mono text-sm text-muted-foreground leading-relaxed"><span class="text-primary shrink-0" aria-hidden="true">▸</span><span class="rich-text">Keep conditional comments if the markup is ever sent as email. Outlook renders with Word, and those instructions are how a template survives it.</span></li><li class="flex gap-3 font-mono text-sm text-muted-foreground leading-relaxed"><span class="text-primary shrink-0" aria-hidden="true">▸</span><span class="rich-text">Check the saving against a compressed response before adding a build step. Indentation is what a compressor removes first, so the wire gain is far smaller than the file gain.</span></li></ul></section><section class="mt-14 max-w-5xl mx-auto" data-section="gotchas"><h2 class="text-lg font-mono font-bold text-foreground mb-4">How minified HTML breaks</h2><div class="grid grid-cols-1 md:grid-cols-2 gap-4"><div class="p-4 rounded-md border border-warning/40 bg-warning/5"><h3 class="m-0 mb-1.5 font-mono text-sm font-bold text-warning flex gap-2"><span aria-hidden="true">⚠</span>Two words run together</h3><p class="m-0 font-mono text-sm text-muted-foreground leading-relaxed rich-text">The space between inline elements is rendered. This is the most common HTML minification bug and it is visible on the page rather than in any error.</p></div><div class="p-4 rounded-md border border-warning/40 bg-warning/5"><h3 class="m-0 mb-1.5 font-mono text-sm font-bold text-warning flex gap-2"><span aria-hidden="true">⚠</span>A code sample reflows</h3><p class="m-0 font-mono text-sm text-muted-foreground leading-relaxed rich-text">Whitespace inside <code><pre></code> is content. Anything that collapses it has rewritten the sample rather than compacted the file.</p></div><div class="p-4 rounded-md border border-warning/40 bg-warning/5"><h3 class="m-0 mb-1.5 font-mono text-sm font-bold text-warning flex gap-2"><span aria-hidden="true">⚠</span>CSS you did not write makes whitespace matter</h3><p class="m-0 font-mono text-sm text-muted-foreground leading-relaxed rich-text">An element styled <code>white-space: pre</code> renders its spaces exactly, and the rule may live in a framework three files away. A minifier reads markup, not stylesheets.</p></div><div class="p-4 rounded-md border border-warning/40 bg-warning/5"><h3 class="m-0 mb-1.5 font-mono text-sm font-bold text-warning flex gap-2"><span aria-hidden="true">⚠</span>A conditional comment disappears</h3><p class="m-0 font-mono text-sm text-muted-foreground leading-relaxed rich-text">Stripping <code><!--[if …]></code> removes behaviour that Outlook and older browsers act on, and the failure appears in one client rather than everywhere.</p></div></div></section><section class="mt-14 max-w-5xl mx-auto" data-section="techspecs"><h2 class="text-lg font-mono font-bold text-foreground mb-4">Method, protection and limits</h2><dl class="m-0 grid grid-cols-1 lg:grid-cols-2 rounded-md border border-border bg-surface overflow-hidden"><div class="grid grid-cols-1 sm:grid-cols-[160px_1fr] gap-1 sm:gap-4 px-4 py-3 border-b border-border/50 lg:odd:border-r"><dt class="font-mono text-[10px] uppercase tracking-wider text-muted-foreground pt-0.5">Method</dt><dd class="m-0 font-mono text-sm text-foreground/90 rich-text">A single pass that parks pre, textarea, script and style regions, collapses the whitespace that remains, and restores the parked regions byte for byte.</dd></div><div class="grid grid-cols-1 sm:grid-cols-[160px_1fr] gap-1 sm:gap-4 px-4 py-3 border-b border-border/50 lg:odd:border-r"><dt class="font-mono text-[10px] uppercase tracking-wider text-muted-foreground pt-0.5">Inline elements</dt><dd class="m-0 font-mono text-sm text-foreground/90 rich-text">Whitespace adjacent to a, span, strong, em, code, img, button, label and the rest of the inline set is preserved as a single space, because the browser renders it.</dd></div><div class="grid grid-cols-1 sm:grid-cols-[160px_1fr] gap-1 sm:gap-4 px-4 py-3 border-b border-border/50 lg:odd:border-r"><dt class="font-mono text-[10px] uppercase tracking-wider text-muted-foreground pt-0.5">Comments</dt><dd class="m-0 font-mono text-sm text-foreground/90 rich-text">Removed, except those beginning with a conditional test, which are instructions rather than notes.</dd></div><div class="grid grid-cols-1 sm:grid-cols-[160px_1fr] gap-1 sm:gap-4 px-4 py-3 border-b border-border/50 lg:odd:border-r"><dt class="font-mono text-[10px] uppercase tracking-wider text-muted-foreground pt-0.5">Not attempted</dt><dd class="m-0 font-mono text-sm text-foreground/90 rich-text">No attribute-quote removal, no optional closing-tag omission, no boolean-attribute collapsing, no minifying of inline CSS or JavaScript. Each is a genuine saving with a genuine edge case.</dd></div><div class="grid grid-cols-1 sm:grid-cols-[160px_1fr] gap-1 sm:gap-4 px-4 py-3 border-b border-border/50 lg:odd:border-r"><dt class="font-mono text-[10px] uppercase tracking-wider text-muted-foreground pt-0.5">Limits</dt><dd class="m-0 font-mono text-sm text-foreground/90 rich-text">Input is refused above 8 MB; output past 2 MB is truncated for display while Copy carries the whole result.</dd></div><div class="grid grid-cols-1 sm:grid-cols-[160px_1fr] gap-1 sm:gap-4 px-4 py-3 border-b border-border/50 lg:odd:border-r"><dt class="font-mono text-[10px] uppercase tracking-wider text-muted-foreground pt-0.5">File handling</dt><dd class="m-0 font-mono text-sm text-foreground/90 rich-text">Uploads are read inside the page with the browser File API and are never transmitted; Download writes out what is already in the tab.</dd></div><div class="grid grid-cols-1 sm:grid-cols-[160px_1fr] gap-1 sm:gap-4 px-4 py-3 border-b border-border/50 lg:odd:border-r"><dt class="font-mono text-[10px] uppercase tracking-wider text-muted-foreground pt-0.5">Network</dt><dd class="m-0 font-mono text-sm text-foreground/90 rich-text">None from tool code. A test sweep calls every function this page uses with <code>fetch</code> and <code>XMLHttpRequest</code> replaced by stubs that throw, so a stray request fails the build instead of shipping. Disconnect from the network and the page still works.</dd></div></dl></section><section class="mt-14 max-w-5xl mx-auto" data-section="faq"><h2 class="text-lg font-mono font-bold text-foreground mb-4">Questions about minifying HTML</h2><div class="rounded-md border border-border divide-y divide-border/50"><details class="group"><summary class="flex items-baseline gap-3 px-4 py-3 font-mono text-sm font-bold text-foreground cursor-pointer list-none hover:bg-surface transition-colors min-h-11"><span class="text-primary transition-transform group-open:rotate-90" aria-hidden="true">›</span>Can minifying HTML change how a page looks?</summary><p class="m-0 px-4 pb-4 pl-11 max-w-3xl font-mono text-sm text-muted-foreground leading-relaxed rich-text">Yes, and that is what makes it different from minifying JSON or CSS. Whitespace between inline elements is rendered as a space, so removing it joins two words visibly. Whitespace inside pre and textarea is content. Both are protected here — and both are exactly what goes wrong when whitespace is treated as uniformly disposable.</p></details><details class="group"><summary class="flex items-baseline gap-3 px-4 py-3 font-mono text-sm font-bold text-foreground cursor-pointer list-none hover:bg-surface transition-colors min-h-11"><span class="text-primary transition-transform group-open:rotate-90" aria-hidden="true">›</span>Why is my saving smaller than I expected?</summary><p class="m-0 px-4 pb-4 pl-11 max-w-3xl font-mono text-sm text-muted-foreground leading-relaxed rich-text">Because indentation is a small share of a real page. Tag names, attributes, class lists and text are the bulk, and none of it can be removed. If the file is still large, look at what is in it rather than at how it is laid out.</p></details><details class="group"><summary class="flex items-baseline gap-3 px-4 py-3 font-mono text-sm font-bold text-foreground cursor-pointer list-none hover:bg-surface transition-colors min-h-11"><span class="text-primary transition-transform group-open:rotate-90" aria-hidden="true">›</span>Should I minify HTML if the server uses compression?</summary><p class="m-0 px-4 pb-4 pl-11 max-w-3xl font-mono text-sm text-muted-foreground leading-relaxed rich-text">The gain on the wire is a fraction of the gain on disk, because indentation is the most compressible thing in the document and a compressor removes it first. Minify because your build does it, or because the markup is stored somewhere raw where no compression applies.</p></details><details class="group"><summary class="flex items-baseline gap-3 px-4 py-3 font-mono text-sm font-bold text-foreground cursor-pointer list-none hover:bg-surface transition-colors min-h-11"><span class="text-primary transition-transform group-open:rotate-90" aria-hidden="true">›</span>Why are quotes still around my attributes?</summary><p class="m-0 px-4 pb-4 pl-11 max-w-3xl font-mono text-sm text-muted-foreground leading-relaxed rich-text">Because removing them is only safe when the value contains no space, quote, equals sign or backtick — and a value that is safe today can come from a template variable tomorrow. It is a legitimate optimisation for a build tool that can test the result, and a poor bet for a text box.</p></details><details class="group"><summary class="flex items-baseline gap-3 px-4 py-3 font-mono text-sm font-bold text-foreground cursor-pointer list-none hover:bg-surface transition-colors min-h-11"><span class="text-primary transition-transform group-open:rotate-90" aria-hidden="true">›</span>What happens to my inline CSS and JavaScript?</summary><p class="m-0 px-4 pb-4 pl-11 max-w-3xl font-mono text-sm text-muted-foreground leading-relaxed rich-text">They are left exactly as written. Both are different languages with different rules, and JavaScript in particular has line breaks that insert semicolons. Minify them with a tool for that language, then minify the markup around them.</p></details><details class="group"><summary class="flex items-baseline gap-3 px-4 py-3 font-mono text-sm font-bold text-foreground cursor-pointer list-none hover:bg-surface transition-colors min-h-11"><span class="text-primary transition-transform group-open:rotate-90" aria-hidden="true">›</span>Are conditional comments removed?</summary><p class="m-0 px-4 pb-4 pl-11 max-w-3xl font-mono text-sm text-muted-foreground leading-relaxed rich-text">No. A comment starting with a conditional test is an instruction rather than a note, and Outlook still acts on them because it renders with the Word engine. Ordinary comments are removed; these are kept.</p></details><details class="group"><summary class="flex items-baseline gap-3 px-4 py-3 font-mono text-sm font-bold text-foreground cursor-pointer list-none hover:bg-surface transition-colors min-h-11"><span class="text-primary transition-transform group-open:rotate-90" aria-hidden="true">›</span>Is minified HTML valid HTML?</summary><p class="m-0 px-4 pb-4 pl-11 max-w-3xl font-mono text-sm text-muted-foreground leading-relaxed rich-text">Yes. Nothing here changes the structure of the document — only the whitespace between elements, in the places where the browser was going to collapse it anyway. Anything that parsed before parses after.</p></details><details class="group"><summary class="flex items-baseline gap-3 px-4 py-3 font-mono text-sm font-bold text-foreground cursor-pointer list-none hover:bg-surface transition-colors min-h-11"><span class="text-primary transition-transform group-open:rotate-90" aria-hidden="true">›</span>Does my markup leave the browser?</summary><p class="m-0 px-4 pb-4 pl-11 max-w-3xl font-mono text-sm text-muted-foreground leading-relaxed rich-text">No. The work is JavaScript running in this tab. Every function it calls is covered by a test that stubs <code>fetch</code> and <code>XMLHttpRequest</code> to throw, so a request that slipped in would break the build rather than reach a server — and you can confirm it for yourself by disconnecting and carrying on.</p></details></div></section><script type="module" src="/_astro/html-minifier.astro_astro_type_script_index_0_lang.CFR94DsA.js"></script></div><div class="mt-14 max-w-5xl mx-auto"><h2 class="text-xs font-mono font-bold text-muted-foreground uppercase tracking-widest mb-4">Related_Tools</h2><div class="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-4"><a href="/html-formatter" class="block p-4 rounded-md border border-border bg-surface hover:border-primary/50 hover:bg-secondary transition-all no-underline"><span class="block text-sm font-mono font-bold text-foreground mb-1">HTML Formatter</span><span class="block text-xs font-mono text-muted-foreground leading-relaxed">Reformat messy HTML with consistent indentation.</span></a><a href="/css-beautifier" class="block p-4 rounded-md border border-border bg-surface hover:border-primary/50 hover:bg-secondary transition-all no-underline"><span class="block text-sm font-mono font-bold text-foreground mb-1">CSS Beautifier and Minifier</span><span class="block text-xs font-mono text-muted-foreground leading-relaxed">Format or minify CSS without touching the whitespace that is grammar.</span></a><a href="/js-minifier" class="block p-4 rounded-md border border-border bg-surface hover:border-primary/50 hover:bg-secondary transition-all no-underline"><span class="block text-sm font-mono font-bold text-foreground mb-1">JavaScript Minifier</span><span class="block text-xs font-mono text-muted-foreground leading-relaxed">Minify JavaScript through a real parser, and see which switch is risky.</span></a><a href="/json-minifier" class="block p-4 rounded-md border border-border bg-surface hover:border-primary/50 hover:bg-secondary transition-all no-underline"><span class="block text-sm font-mono font-bold text-foreground mb-1">JSON Minifier</span><span class="block text-xs font-mono text-muted-foreground leading-relaxed">Strip whitespace from JSON, and see what it actually saved.</span></a><a href="/html-encode" class="block p-4 rounded-md border border-border bg-surface hover:border-primary/50 hover:bg-secondary transition-all no-underline"><span class="block text-sm font-mono font-bold text-foreground mb-1">HTML Entity Encoder and Decoder</span><span class="block text-xs font-mono text-muted-foreground leading-relaxed">Escape text into HTML entities, or decode them back.</span></a><a href="/html-to-markdown" class="block p-4 rounded-md border border-border bg-surface hover:border-primary/50 hover:bg-secondary transition-all no-underline"><span class="block text-sm font-mono font-bold text-foreground mb-1">HTML to Markdown Converter</span><span class="block text-xs font-mono text-muted-foreground leading-relaxed">Convert HTML back to Markdown, with an account of what was lost.</span></a></div></div></div></section></main><footer class="bg-background border-t border-border py-12"><div class="mx-auto w-full max-w-screen-xl px-4 md:px-8"><div class="grid grid-cols-1 md:grid-cols-3 gap-8 mb-12"><div class="md:col-span-2"><div class="flex items-center gap-2 mb-4"><div class="w-5 h-5 rounded bg-primary flex items-center justify-center"><span class="text-primary-foreground font-mono font-bold text-[10px]">T</span></div><span class="text-md font-mono font-bold text-foreground">toolkit.codes</span></div><p class="text-xs font-mono text-muted-foreground max-w-sm leading-relaxed">Free online developer utilities: formatters, converters, encoders, generators, and text tools. Everything that's live is in the <a href="/all" class="text-muted-foreground underline underline-offset-2 hover:text-primary transition-colors">index</a>.</p></div><div><h3 class="text-[10px] font-mono font-bold text-muted-foreground uppercase tracking-widest mb-4">System</h3><ul class="flex flex-col gap-2 list-none p-0"><li><a href="/all" class="text-xs font-mono text-muted-foreground hover:text-primary no-underline transition-colors">Index</a></li><li><a href="/about" class="text-xs font-mono text-muted-foreground hover:text-primary no-underline transition-colors">About</a></li><li><a href="/privacy" class="text-xs font-mono text-muted-foreground hover:text-primary no-underline transition-colors">Privacy</a></li></ul></div></div><div class="pt-8 border-t border-border"><span class="text-[10px] font-mono text-muted-foreground">© 2026 Toolkit.codes</span></div></div></footer><script type="module" src="/_astro/BaseLayout.astro_astro_type_script_index_0_lang.CD8NImTv.js"></script></body></html>