Format and beautify WSDL XML documents.
Format and indent XML documents with proper nesting and tag alignment.
Validate XML well-formedness and check for unclosed tags or syntax issues.
View and explore XML data using a dedicated code viewer.
Pretty print your XML data with proper indentation.
Convert XML documents and attributes into clean JSON objects.
SOAP traffic almost never arrives in a readable state. Captured requests and responses come off the wire as one continuous line, and the part you actually need — a fault code, a single field in the body, the contents of a security header — is buried in the middle of it. This SOAP formatter re-indents the envelope so its anatomy is obvious: the Envelope element, the optional Header, the Body, and any Fault within it, each at its proper depth with namespace prefixes preserved. Paste a captured request or response and read it as a structured document instead of a string. It is particularly useful when debugging an integration where one side reports an error and you need to see exactly what was sent or returned. Formatting is entirely client-side, which matters because SOAP headers routinely carry authentication tokens.
It is the XML wrapper around every SOAP message. The Envelope element contains an optional Header for metadata such as authentication, and a mandatory Body carrying the request, response, or Fault.
Format the response and look inside the Body for the Fault element. It contains the fault code and a human-readable reason, and often a detail element with service-specific information.
Yes. Formatting happens entirely in your browser — the envelope is never transmitted, stored, or logged. That matters because WS-Security headers often carry tokens.
No. Only whitespace between elements is adjusted. Namespace prefixes, attributes, and element content are preserved exactly.
It is not well-formed XML. Captured traffic is often truncated mid-document, or includes HTTP headers above the envelope that need removing first.
A SOAP envelope is an individual message exchanged with a service. A WSDL is the document describing the service itself. Both are XML, but they are read for different reasons.