Indent XML for inspection while keeping mixed text and preserved spaces intact. Format locally, copy the result and keep the original for comparison.
No result yet. Enter values or load the worked example.
Validate XML → preserve text-sensitive subtrees → indent element-only structure
ONE WORKED EXAMPLE
Two spaces reveal the nested SKU element. Its literal text remains 001.
<catalog> <sku>001</sku> </catalog>
<p>Hello <b>world</b>!</p>THE FIELD NOTES
Use the result now, then read the practical notes for assumptions, examples, limitations, and the choices behind it.
Two spaces reveal the nested SKU element. Its literal text remains 001.
The formatter checks that the XML is well formed, then adds two-space indentation around element-only structure. Mixed text, CDATA and subtrees marked xml:space="preserve" stay together without inserted spaces.
Two spaces reveal the nested SKU element. Its literal text remains 001.
For a different catalog source format, the json to csv converter extracts a table from JSON records and the csv formatter changes CSV delimiters. Neither accepts XML; this formatter keeps XML as XML.
DTDs, entity declarations and processing instructions are unsupported. XML parsing can normalize line endings and entity spelling, so keep the original when byte identity or a digital signature matters. This is formatting, not XSD validation or XML canonicalization.
THE PRODUCT IS NEXT
The formatter checks that the XML is well formed, then adds two-space indentation around element-only structure. Mixed text, CDATA and subtrees marked xml:space="preserve" stay together without inserted spaces.
Two spaces reveal the nested SKU element. Its literal text remains 001.
For a different catalog source format, the json to csv converter extracts a table from JSON records and the csv formatter changes CSV delimiters. Neither accepts XML; this formatter keeps XML as XML.
DTDs, entity declarations and processing instructions are unsupported. XML parsing can normalize line endings and entity spelling, so keep the original when byte identity or a digital signature matters. This is formatting, not XSD validation or XML canonicalization.
Indent XML for inspection while keeping mixed text and preserved spaces intact. Format locally, copy the result and keep the original for comparison.
DTDs, entity declarations and processing instructions are unsupported. XML parsing can normalize line endings and entity spelling, so keep the original when byte identity or a digital signature matters. This is formatting, not XSD validation or XML canonicalization.
No. Inputs are processed locally in this browser and are not included in analytics. Keep your own source copy before closing or refreshing the page.
BUILT BY LOOK ATLAS
Turn a simple product photo into polished, campaign-ready creative for your store, ads, and social channels. No studio. No reshoots.
Create your first shoot free, then keep going when you’re ready.