XML formatter

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from XML formatter

XML formatter helps you pretty-print markup in XML. Indentation makes element nesting easier to inspect in compact XML documents. This is useful when the information is already available but its structure, presentation, or consistency makes it difficult to inspect. Work with a representative sample first so that you can recognize the expected result before applying the same operation to a larger document. Whitespace may be meaningful in mixed content, signed documents, or application-specific XML. Formatting can change the literal bytes. Keep the original input available while reviewing the output. The important check is whether the result still has the intended values and relationships, rather than whether it merely looks neater. Check text nodes, namespaces, and any signature or canonicalization requirements before replacing the original.

Guide updated October 13, 2026

How to use this tool

1. Place the XML input in the relevant editor. If the tool compares or combines documents, keep each document in its own input.
2. Select the available settings for the operation you need. Check text nodes, namespaces, and any signature or canonicalization requirements before replacing the original.
3. Review any syntax errors before interpreting the result. A valid document with the wrong structure needs a different fix from malformed input.
4. Inspect the changed portion and at least one unchanged portion. Keep a copy of the original XML until the result has been checked in its destination.

SEE IT IN PRACTICE

A worked example

<root><name>Ada</name></root>

<root>
  <name>Ada</name>
</root>

The root element and name child become easier to distinguish. In element-only content, this layout is commonly more readable.

Whitespace-sensitive XML

A paragraph containing text and inline elements is mixed content, so adding whitespace between nodes may alter the text seen by an application. Signed XML and byte-based comparisons introduce further constraints. Use formatting primarily for inspection unless you have established that reserialization is acceptable. Preserve the original document when the exact bytes are part of a verification workflow.

Preserve the element hierarchy

Pretty printing should make parent and child elements easier to see. After formatting, check a repeated element, an attribute, and a text-containing element rather than just the outer root. Namespace prefixes are part of how names are represented and should not be changed casually. If the XML participates in signing or byte-for-byte comparison, keep the original and use the formatted version only for inspection unless reserialization is explicitly allowed.

When this tool is useful

• Read XML service responses while keeping the underlying structure visible.
• Inspect element nesting with a compact, reproducible sample.
• Prepare readable XML examples before copying data into another application.

Tips for a better result

• Whitespace may be meaningful in mixed content, signed documents, or application-specific XML. Formatting can change the literal bytes.
• Check text nodes, namespaces, and any signature or canonicalization requirements before replacing the original.
• Use a small XML example to isolate an unexpected result. Add nested objects, arrays, quoted text, and empty values only as needed to reproduce the behavior.

Frequently asked questions