XML to JSON

XML attributes are prefixed with @_ in the JSON to keep them distinct from child elements. For example, <div class="main" id="hero"><span>text</span></div> becomes {"div": {"@_class": "main", "@_id": "hero", "span": "text"}}. This convention is the de-facto standard set by fast-xml-parser, xml2js, and most other XML-to-JSON libraries — it lets you reliably round-trip back to XML if needed, and it avoids name collisions when an element has both an attribute and a child element with the same name. Text content inside an element with attributes is stored in a #text key. Once you know the convention, the JSON is straightforward to consume from any language.

Yes. All nested elements are preserved at arbitrary depth — there's no recursion limit. Repeated sibling elements (like multiple <item> tags inside <items>) are automatically converted into a JSON array, which is what you almost always want for downstream JavaScript processing. Mixed content (text and elements interleaved) is preserved using the #text key. The only edge case where you'll need to think carefully is when an element appears once in some XML documents and multiple times in others — your downstream code should be defensive and handle both single-object and array shapes, since the parser doesn't force consistency across documents.

Yes, both work cleanly. SOAP responses with their nested <soap:Envelope>, <soap:Body>, and namespaced elements convert directly — namespace prefixes are preserved as part of the JSON keys (e.g., "soap:Body"), so you can navigate the structure exactly like you would in a SOAP client. RSS feeds with their <channel>, <item>, <pubDate>, and <description> elements also map cleanly, and repeated <item> entries become a JSON array automatically. For SVG, you'll get a JSON tree of the SVG element structure, which is useful if you're building a visual editor or analyzing SVG content programmatically.

Yes, up to 5MB, processed entirely in your browser. The fast-xml-parser library is genuinely fast — it streams through the document once rather than building a DOM, so even 5MB of XML converts in well under a second on modern hardware. For files in the 50-100MB range you would want a Node.js script with sax-style streaming, but for everything API-related or config-related (which is almost always under a megabyte), this in-browser tool is more than fast enough and avoids any privacy concern about uploading proprietary API responses to a third party.