1. Parse
The source is scanned into a tag stream with line numbers, so every finding points back to a place in your code.
Your rendered page will appear here.
HTML Compiler
Paste HTML, CSS, and JavaScript, then compile it. The compiler parses your markup, reports unclosed tags and duplicate ids, strips comments and dead whitespace, and emits a single self-contained file — or a JavaScript template function. Everything runs in your browser; publish the compiled artifact to a public URL when you are ready.
Definition
An HTML compiler takes source markup and turns it into something ready to ship. It reads your document the way a browser would, reports what is broken or wasteful, and writes out an optimized artifact — usually a single minified HTML file with the comments, indentation, and redundant attributes removed.
That is different from an editor, which only helps you type, and from a plain minifier, which shrinks bytes without telling you anything. A compiler gives you both: a diagnostic report you can act on, and an output file you can hand to a client, attach to an email, or deploy as-is.
Pipeline
Every compile runs the same pipeline. Nothing is uploaded, and each pass shows up in the report below the editor.
The source is scanned into a tag stream with line numbers, so every finding points back to a place in your code.
Nesting is validated against a stack, and the parsed document is checked for duplicate ids, missing alt text, and missing metadata.
Comments are dropped (conditional comments are kept), whitespace collapses, gaps between block elements close, and redundant attributes are removed.
You get a single-file HTML artifact or a JavaScript template function, plus byte counts you can compare against the input.
Output targets
Switch the target above the editor and recompile. The diagnostics stay the same — only the artifact changes.
One .html file with the CSS and JavaScript still inline. Nothing to bundle and nothing to upload alongside it — attach it to an email and it opens anywhere.
The compiled markup is escaped into a template function you can import from any bundler. Handy when the same snippet renders on the server and in the browser.
Publish the compiled artifact and share a public link that serves the optimized page instead of the original source.
How to use
No account, no build step, no npm install.
Start from the sample, open a local .html file, or drop one onto the editor pane.
Press Compile, fix whatever the diagnostics flag, then compile again — later edits recompile automatically.
Copy the artifact, download it, or publish it to a hosted URL you can share anywhere.
Questions
Not quite. A minifier only shrinks bytes. A compiler also parses the document and reports problems — unclosed tags, mismatched nesting, duplicate ids, missing alt text — before writing out the optimized file.
It should not. The optimizer only removes things that do not affect rendering: comments, whitespace around block elements, and redundant attributes. Open the compiled output in a new tab to confirm it behaves identically.
A module exporting a template function that returns the compiled markup as a string. Backticks, dollar-braces, and backslashes are escaped, so you can paste it straight into a JS or TS project.
Yes. Inline style and script blocks are preserved. CSS comments inside style blocks are stripped, while script content is left intact so nothing breaks at runtime.
No. Files referenced by a remote src or href are reported as external dependencies and left alone. The compiler never fetches third-party URLs, so nothing about your page leaks to another server.
No. Parsing, diagnostics, and optimization all run in your browser. Your code only reaches a server when you press Publish — and then it publishes the compiled artifact.
The HTML Editor is a writing surface with a live preview. This compiler adds a build step on top: it validates the document, optimizes it, and hands you an artifact you can download or publish.