Convert XML into clean JSON — attributes, text and repeated tags handled — on your own device, nothing uploaded.
An .xml or .json file — or paste below · converted on your device, nothing uploaded
No size limit · files are processed on your device and never uploaded · how it works
XML in
JSON out
Attributes map to @name, text to #text, and repeated tags become arrays. Runs entirely in your browser.
Runs in your browser. Files are never uploaded — you can go offline after the page loads.
How to use the XML to JSON
Paste XML or drop an .xml file.
Choose pretty or minified JSON.
Copy the JSON or download it.
Easy to use
Drop files, pick options, download. Whole folders at once, no signup, no daily limit.
Best quality
The same engines the professionals use — SVGO, resvg, MozJPEG, libwebp, libavif — compiled to run in your browser.
Private & secure
Files are processed on your device and never uploaded. Close the tab and nothing remains anywhere.
XML into predictable JSON
This parses XML with the browser's real XML engine, then maps it to JSON with a consistent convention: attributes
become keys prefixed with @, an element's text becomes #text when it also carries
attributes, and sibling elements sharing a tag are gathered into an array. That predictability is what makes the
output easy to consume in code.
It runs both ways — JSON to XML — and everything happens in your browser, so nothing is
uploaded. To tidy the JSON afterwards, use the JSON Formatter.
Frequently asked questions
How are attributes and repeated tags handled?
Attributes become keys prefixed with @, an element’s text becomes #text when it also has attributes, and sibling elements with the same tag are collected into an array.
Can it go back to XML?
Yes — flip to JSON → XML to rebuild indented XML from JSON that follows the same convention.
Is my file uploaded?
No — parsing and conversion happen entirely in your browser.
Most online converters upload your file to a server. InfyTool ships the actual encoders to your browser as WebAssembly instead, so processing happens inside your tab — faster for batches, and nothing to delete afterwards.
No upload, ever. Turn off Wi-Fi after the page loads and every tool keeps working.
No limits. No file-size cap, no queue, no watermark, no account.
Runs on your CPU. Batches use several cores in parallel; nothing is throttled.