Normalize XML configs into approachable YAML files
DOMParser validates first, then YAML mirrors the same normalization path used internally for years.
Developer notes
• CDATA-derived text survives as literals but may coerce quotes. • Namespace-heavy docs may widen keys — sanity-check YAML consumers. • Split monstrous configs before mobile editing.
When teams pick this route
• Infra rotations favoring indented YAML readability. • Helm previews after lifting XML inventories. • Docs teaching structural equivalence.
About these options
CSV exports: choose a delimiter (Auto follows locale — semicolon on /fr), RFC-minimal vs always-quoted fields, line endings, and whether to emit a header row. CSV imports: delimiter + whether row 1 holds column names (Auto delimiter follows locale only for convenience). JSON output (XML, YAML, or CSV sources): indentation (including compact one-line) and optional recursive key sort. JSON → XML: toggle pretty-printing and indent width. YAML output: indent width, readable vs tighter layout, and deterministic string quoting (there is no source YAML file to “preserve”). XML comments are not represented in the intermediate JSON tree.
Worked examples
Regional service rollout
Sample input
Sample output
Release artefacts list
Sample input
Sample output
Navigate related converters
Shape-check via XML → JSON, pivot spreadsheets with XML → CSV, optimise documents using XML minifier.
XML → YAML FAQ
DOM caveats
Why quoted numbers?
YAML quotes ambiguous scalars; logical types still trace back to JSON intermediary parity.
XPath transforms?
Not supported — DOM snapshot only.
Huge files?
Desktop Chrome recommended.
CDATA handling?
Text nodes translate like other literals; verify downstream parsers.
Looking for every converter, encoder, and minifier in one place? Developer tools hub Open the curated developer tools catalogue.