Browser-native parsing
Toolsle reconstructs indentation by walking whatever structure DOMParser yields. Browser recovery rules silently fix some broken tags—which is handy for exploratory cleanup but risky for audited templates—diff the output against source control whenever precision matters.
When to reach for JSON or Markdown
Data payloads still belong in JSON; prose-first workflows often start in Markdown before converting to semantic HTML elsewhere on Toolsle—use whichever stage matches where you are editing.
Frequently asked questions
How do I pretty print HTML?
Paste or upload your markup, choose spacing, hit Pretty print, then copy from the Output column or overwrite the input iteratively while you refactor.
What does minify HTML do here?
It removes discretionary whitespace introduced by authoring tools while respecting literal content stored inside preserved blocks such as scripts and templates.
Is the preview sandbox safe?
Preview runs with the strictest iframe sandbox Toolsle configures—assume scripts cannot execute inside that pane.
Does this validator fix invalid HTML?
It parses like a forgiving browser, then re-serializes—you may notice implicit closing tags appearing or attributes reordering slightly.
Is my HTML uploaded?
Nothing is sent off-device for this formatter.