XML formatter
Format XML instantly
Paste XML, choose indentation and collapse behavior, then copy the formatted output
<hello> <world>foo</world> <world>bar</world> </hello>
Introduction / overview
The XML formatter takes raw XML on the left and produces a consistently-indented, easy-to-read version on the right. It’s ideal for debugging, code reviews, and quickly understanding a nested document.
Use it when your XML is hard to scan — especially when tags are nested several levels deep or when you need clean diffs in git.
What the options mean
- Indent size controls how many spaces are used per nesting level.
- Collapse content keeps simple text nodes compact so your output doesn’t explode into dozens of lines.
If your next step is converting data formats, try our JSON prettify tool for readable payloads.
How to use / quick start
Paste your XML
Paste raw XML into the left input. You can format tiny snippets or full documents.
Choose options
Set the indent size and decide whether to collapse text content.
Copy the formatted output
Use the copy button on the right to paste the result into your editor, ticket, or PR comment.
A quick way to reason about indentation
If your indent size is spaces and a tag is nested levels deep, the leading spaces are roughly:
This isn’t “math you must do” — it’s just a mental model for why a larger indent can make deep XML very tall.
Step-by-step examples
Example 1: Compact snippet → readable XML
Input:<hello><world>foo</world><world>bar</world></hello>
Set Indent size to and keep Collapse content enabled. The output becomes easy to scan line-by-line.
Example 2: Deep nesting with a larger indent
If you choose spaces and your data is nested levels, you’ll see up to leading spaces at the deepest level.
Practical takeaway: for very deep documents, a smaller indent usually stays more readable.
Real-world examples / use cases
Background: you receive a dense XML response in logs. Inputs: paste the response, set . Result: the formatted XML reveals the exact nested field that differs.
Background: a config file was edited by multiple people. Inputs: format both versions to normalize whitespace. Result: diffs focus on semantic changes, not messy formatting.
Background: you’re writing a README or a support article. Inputs: format snippets so indentation is consistent. Result: readers understand structure faster.
Background: you want to compare XML data with JSON. After formatting, it’s often easier to extract fields or copy segments into other tools like JSON prettify.
Common scenarios / when to use
Not a good fit: if you need to validate against an XSD schema or canonicalize XML for cryptographic signatures, you’ll need specialized tooling.
Tips & best practices
- Pick a consistent indent size (commonly or ).
- Keep “Collapse content” on when your XML has many short text nodes (it reduces noisy line breaks).
- When you see “Provided XML is not valid”, look for unescaped or mismatched closing tags.
- For huge documents, format smaller slices (a subtree) to keep your browser snappy.
Calculation method / formatting rules
Formatting is mainly about whitespace: newlines and indentation. The formatter reads the XML structure (elements, nesting, and text nodes) and then outputs the same structure with consistent spacing.
Indentation model
For a given nesting level and indent size :
Where is the count of leading spaces before the tag.
What “collapse content” does (in plain terms)
When enabled, simple text-only nodes are kept compact so you don’t get extra whitespace in places where it doesn’t help readability.
Related concepts / background
Whitespace in XML
In many XML contexts, whitespace between elements is not semantically important — but in mixed-content documents it can be. That’s why “collapse content” is a preference: it optimizes for readability, not every edge case.
Frequently asked questions
Does formatting change my XML data?
It changes whitespace and line breaks. The tag structure and text content should remain the same for typical XML.
Why do I see an “XML is not valid” error?
Common causes include missing closing tags, unescaped characters like , or an incomplete copy/paste.
What indent size should I use?
Most teams use or spaces. Smaller indents can be easier for deep XML.
Can I share my formatted result?
Yes — use the Share button below the calculator. You can choose whether to include your inputs/results.
Is my XML uploaded anywhere?
This formatter runs locally in your browser for formatting. Avoid sharing sensitive data in public links.
Limitations / disclaimers
- Formatting optimizes readability, not canonicalization for signatures.
- Whitespace can matter for certain mixed-content documents; review before using output in strict pipelines.
- Do not use this tool as a substitute for schema validation (XSD) when correctness is critical.
External references / sources
Related Calculators
HTML WYSIWYG editor
Edit rich text in a simple WYSIWYG editor and copy Prettier-formatted HTML instantly. Runs locally in your browser.
Phone parser and formatter
Parse, validate, and format phone numbers. Get the country, calling code, type, and common formats like E.164 and RFC3966. Runs locally in your browser.
PDF Signature Checker
Verify the signatures of a PDF file locally in your browser and inspect certificate details. No data is sent to any server.
Fraction to Percent Calculator
Convert fractions to percentages and vice versa instantly
Grams to Tablespoons Converter
Convert grams to tablespoons for any ingredient instantly. Perfect for cooking and baking with support for multiple ingredients.
Decimal to Percent Converter
Convert decimal numbers to percentages with real-time bidirectional conversion