Translate XML payloads into clipboard-friendly JSON
SOAP, RSS or sitemap chunks become REST-friendly structures with toast-safe error reporting.
Developer notes
• Mixed-content nodes flatten per xmlToJson() parity rules. • Pretty printing is clipboard-only. • Validate consuming JSON schemas before production.
When teams pick this route
• Front-end mocking fetch() payloads from SOAP exports. • Platform squads diffing configs before REST cutovers. • SRE exploratory tooling.
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
Attributes lift into JSON fields next to nested text
Sample input
Sample output
Repeating tags collapse into arrays
Sample input
Sample output
Navigate related converters
Round-trip experiments: JSON → XML, slim files with XML minifier, or convert toward YAML via XML → YAML.
XML → JSON FAQ
Browser parsing
Different from xmllint?
This uses DOMParser — great for snippets, less ideal for gigabyte dumps.
XSD enforcement?
Structural validity only.
CDATA preserved?
Text nodes remain with equivalent content — inspect JSON consumers.
Why quote differences?
Copy/paste then run through your formatter as needed.
Looking for every converter, encoder, and minifier in one place? Developer tools hub Open the curated developer tools catalogue.