WSDL Formatter & Viewer
This WSDL formatter indents the document and lists what it actually declares — the services, the operations you can call, the messages they exchange, the bindings and the declared types. That summary is the point: a WSDL is usually several hundred lines of namespace declarations and schema imports wrapped around a handful of operations, and answering the only question that matters — what can I call, and what does it take? — otherwise means reading all of it. Both the formatted document and the summary are shown side by side, so you can find an operation in the list and then go and read its definition.
How it works
Formats a WSDL document and lists what it actually declares — the services, the operations you can call, the messages they exchange, the bindings and the declared types.
A WSDL is usually several hundred lines of namespace declarations wrapped around a handful of operations. The summary answers "what can I call?" without reading all of it.
Everything runs in your browser — nothing you paste is sent to a server.
What a WSDL declares
- Types — the XML Schema definitions of the data structures used.
- Messages — the inputs and outputs, built from those types.
- Port types — the abstract operations, each pairing an input message with an output.
- Bindings — how those operations travel over a protocol, almost always SOAP over HTTP.
- Services — the endpoints where the bindings are actually available.
Reading it in the useful order
A WSDL is written in that order and best read in reverse. Start with the service to find the endpoint, follow its binding to a port type, and read the operations there — those are the calls you can make. Only then look at the messages and types for a specific operation.
Why they are so long
Most of a WSDL is embedded XML Schema, and schemas are verbose. A service with three operations routinely produces 600 lines, of which perhaps 30 describe the operations.
Frequently asked questions
What does the WSDL viewer show?
The formatted document, plus lists of the services, operations, messages, bindings and types it declares.
Why is a summary useful?
A WSDL is mostly namespace and schema boilerplate. The question you actually have — what operations exist — takes a lot of reading to answer, and the summary answers it immediately.
What is the difference between a port type and a binding?
A port type declares the abstract operations. A binding says how they are carried over a protocol — usually SOAP over HTTP. One port type can have several bindings.
What are messages?
The inputs and outputs of the operations. Each operation refers to messages by name, which is why the same message can appear in several operations.
Does it call the service?
No. It reads the document you paste and makes no network request of any kind.
Is my WSDL uploaded?
No. Everything runs in your browser, so an internal service definition never leaves your device.
Related tools
SOAP Message Formatter
This SOAP formatter indents an envelope and pulls out the operation and any fault.
XML Formatter & Beautifier
This XML formatter re-indents minified or messy XML while preserving comments and CDATA.
XML Viewer
This XML viewer renders any document as a collapsible tree with attributes and copyable paths.