XML / XPath / SOAP Inspector
Paste XML to validate and pretty-print it, run a namespace-aware XPath expression, and inspect the result. The SOAP tab recognizes SOAP 1.1 / 1.2 envelopes and extracts fault code, reason, and detail; the Namespaces tab lists every xmlns declaration for use in XPath. Runs in your browser; nothing is uploaded.
Auto-runs as you type. Ctrl+Enter to re-run.
How to use the XML / XPath / SOAP Inspector
Parse, format, query, and debug XML, SOAP envelopes, and SAML assertions in your browser. Pretty-print the document, run XPath expressions with namespace-aware resolution, inspect SOAP 1.1 / 1.2 faults, and list every namespace declaration. Useful for legacy enterprise integrations, SAML troubleshooting, B2B partner debugging, and any XML payload that won't behave.
How to use it
- Paste your XML document, SOAP request / response, or SAML assertion.
- Read the verdict — well-formedness, element count, SOAP version, and namespace count appear immediately.
- Type an XPath expression in the option field to evaluate it against the document; the namespace resolver is built from the document's
xmlnsdeclarations. - Open the SOAP tab for the envelope version, body operation, and parsed Fault (code / reason / detail) for 1.1 or 1.2.
- Open the Namespaces tab to see every
xmlnsprefix and URI for use in XPath. - Hand off to XML → JSON, JSON Formatter, or Text Diff when you need the payload elsewhere.
When to reach for this tool
- You copied a SOAP response from a legacy integration and need to find the operation, status, or fault detail quickly.
- An XPath returned “no matches” and you suspect a default-namespace issue.
- You need the exact namespace prefixes declared on an XML document to write a working XPath.
- You want a validated, pretty-printed copy of a messy XML payload.
What it does
- Parser & formatter: validates well-formedness, pretty-prints with your chosen indent, and reports parse errors with line/column when the browser provides them.
- XPath tester: evaluates expressions against the parsed document with a namespace resolver derived from the document's declarations. String, number, boolean, and node-set results are all supported.
- Namespace inventory: lists every
xmlnsdeclaration (prefix and URI) so you can reference them in XPath. - SOAP inspector: recognizes SOAP 1.1 and 1.2 envelopes, reports the version and body operation, and parses Fault details (faultcode/faultstring for 1.1; Code/Reason for 1.2) with a plain-language explanation of the fault class.
- Workflow handoffs: send the document to XML → JSON, JSON Formatter, or Text Diff.
Privacy
XML parsing, formatting, XPath evaluation, SOAP inspection, and namespace analysis are all performed in your browser. No XML, headers, URLs, tokens, or XPath expressions are sent to a server. External DTDs and entities are never fetched. The tool does not execute any HTTP request.
FAQ
Does this upload my XML?
No. Everything runs locally in your browser tab. External DTDs and entities are never fetched.
Why does my XPath return no matches?
The most common reason is a default namespace. In XPath, unprefixed names match the “no namespace” — even if the source XML declares xmlns="…". Use a prefix from the Namespaces tab, or fall back to //*[local-name()='YourElement'].
What is the difference between SOAP 1.1 and SOAP 1.2?
SOAP 1.1 uses the http://schemas.xmlsoap.org/soap/envelope/ namespace and a SOAPAction HTTP header with text/xml content type. SOAP 1.2 uses http://www.w3.org/2003/05/soap-envelope and an application/soap+xml content type. Faults also have different shapes — the SOAP tab extracts both.
Can I convert XML to JSON, or redact secrets?
Whole-document XML → JSON lives in the XML to JSON Converter. To redact tokens or secrets before sharing a payload, use the HAR Sanitizer or another dedicated redaction tool — this inspector focuses on formatting, XPath, namespaces, and SOAP faults.
Runs locally in your browser. No uploads.