Shape legacy SOAP contracts into JSON you read beside OpenAPI drafts. Paste WSDL 1.1 XML, pick which slices matter, and export a structured outline without shipping the file off your machine.
Namespaces stay intact. If the parser complains, run the document through the XML pretty printer first.
Draft-07 style wrapper. Bindings and services append when present.
Contract archaeology
First, many teams treat the WSDL file as the whole truth for runtime behavior. The file describes shape and endpoints, not retries, auth edge cases, or idempotency.
Second, JSON does not replace SOAP by magic. You still owe consumers a clear mapping from elements to fields.
Third, nested XSD features such as choice groups, substitution groups, or imports across HTTP boundaries need more than a single pass in the browser.
Fourth, people paste WSDL fragments without the outer definitions wrapper and wonder why the root check fails. The parser looks for a definitions element in the WSDL namespace, not for a random schema shard.
You paste text. The page runs DOMParser against the XML mode, rejects parsererror nodes, then insists on a definitions root. Namespace prefixes on SOAP nodes vary by generator, so the script looks for soap:operation and soap:address first, then falls back to the SOAP namespace URI when vendors omit the prefix.
Checked boxes gate types, messages, and port types. Bindings and services always merge into definitions when the source includes them because those sections answer where you POST without another click.
XSD type strings such as xsd:string map to JSON string, integer, number, or boolean. Anything unknown becomes string on purpose so you spot oddities fast instead of silently dropping data.
Integration engineers comparing two vendor contracts side by side. QA drafting mock payloads from element trees. Technical writers who want one JSON blob to feed diagrams or internal wikis.
portType lines up with binding before they touch generated clients.Raw tree view without schema framing lives in the XML to JSON tool. Envelope-focused payloads pair with SOAP to JSON. If you want codegen-oriented schema text instead, try XML to JSON Schema for XSD-heavy documents.
We still recommend XML validation when a schema file exists, because this converter trusts structure, not business rules.
Some architects want RAML, AsyncAPI, or hand-written YAML instead of JSON. Fair. This export still helps because diff tools and jq-style filters read JSON cleanly, you paste into slide decks without fighting indentation, and junior developers stop asking which XSD file owned a field name.
If your organization mandates OpenAPI 3 for gateways, treat the output here as a research artifact you translate manually. Automatic WSDL-to-OpenAPI generators exist elsewhere, they often need hand fixes for faults, headers, and WS-Security policies anyway.
Multi-megabyte WSDL bundles with inlined schemas stress any textarea. Collapse unused documentation nodes in your source repo before you paste. Split vendor packs into the single service you need when policy allows.
Mobile browsers recover memory slower than desktop Chrome. If you only need operations and endpoints, turn off types temporarily, run the conversion, copy JSON, then reload before you tackle the full schema.
We bias toward readable two-space indentation so the string grows quickly. Download early when you pass a few hundred kilobytes of text so you do not rely on the DOM holding the entire pretty-printed blob.
The tool does not call remote URLs, resolve <import> chains, or certify compliance with your enterprise registry. Output is a sketch for humans and tools, not a signed API contract. For large files, expect slower typing as the textarea grows with content.
Reviewed March 2026. Logic follows WSDL 1.1 structure as exposed through the browser DOM parser, XSD type strings map to simple JSON types where prefixes match xsd: style names.
