Safe by default
The sorter only reorders the specific repeated element path you choose. Non-matching siblings stay anchored, which keeps V1 much safer than global alphabetizing.
Sort repeated XML collections safely with a tree-picked target path, field-based sort keys, and a verification-first reorder preview.
Sort one repeated XML collection at a time with field-based rules, attribute normalization, and a verification-first preview.
The sorter only reorders the specific repeated element path you choose. Non-matching siblings stay anchored, which keeps V1 much safer than global alphabetizing.
Use child text, attribute, or tag-based keys to normalize XML collections before comparing versions, debugging feeds, or reviewing API snapshots.
The reorder preview shows what moved and lets you jump back to the original node area before you trust the normalized output.
No. This first release is scoped on purpose. You choose a target element path, and the sorter only reorders matching repeated elements inside that collection.
You can sort by tag name, an attribute value, direct text content, or a child text path such as name or meta/priority. Primary and secondary keys are supported.
Element order can be schema-significant in XML. Scoped sorting reduces the risk of changing unrelated structure while still helping you normalize feeds, configs, and repeated record sets.
Yes. Attribute sorting is available as an optional normalization toggle for the output, and it is kept separate from element sorting.
No. Validation, target inspection, sorting, preview generation, and output rendering all happen locally in your browser.