HTML Formatter and Beautifier

No. Formatting runs entirely in your browser with client side code, so your markup never leaves your device and nothing is logged.

Opening a tag increases the indent for everything nested inside it, and its closing tag drops back a level. Each level is one indent unit, so tags line up under their parent.

They are void elements that cannot contain anything, so the formatter never increases the depth after them. Sibling tags that follow stay at the same level rather than drifting to the right.

No. The content of those four elements is whitespace sensitive or is not HTML, so the tool captures each block whole and emits it verbatim without reindenting a single character inside.

Runs of whitespace inside ordinary text are reduced to a single space and trimmed, which is how browsers render HTML anyway. This keeps lines tidy. Text inside pre and textarea is exempt and stays exactly as written.

Yes. When a tag holds only a single run of text, such as a list item or a heading, the text and closing tag are merged onto the opening tag's line instead of being split across three lines.

No. It beautifies and indents for readability and does not shrink the file or check for errors. For the smallest output use a minifier, and for correctness use a validator.

Yes. Pick 2 spaces, 4 spaces, or a tab from the Indent menu. The API accepts any string in its indent field, so you can send four spaces, a tab, or another sequence.

The formatter is tolerant. An unterminated tag is kept as text, an open comment runs to the end of the input, and a raw block with no closing tag is preserved verbatim, so you still get output.