Loading SOAP Formatter...
Please wait a moment

How to Format SOAP Messages - Step by Step Guide

Step 1

Input Your SOAP Message

Start by entering your SOAP (Simple Object Access Protocol) message that needs formatting:

•
Paste SOAP content: Copy SOAP messages from your web service requests, responses, or testing tools
•
Upload SOAP files: Select .xml, .soap, or .txt files containing SOAP envelopes
•
Use sample data: Click "Sample" to load example SOAP message and see the formatting in action

Example: Unformatted SOAP Input

Here's what messy, unformatted SOAP looks like:

<?xml version="1.0"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><Authentication><Username>user123</Username><Password>pass456</Password></Authentication></soap:Header><soap:Body><GetCustomerRequest><CustomerId>12345</CustomerId><IncludeOrders>true</IncludeOrders></GetCustomerRequest></soap:Body></soap:Envelope>
Step 2

Automatic SOAP Formatting

A moment after you stop typing, the formatted message appears on the right. Since SOAP is plain XML, here is what happens to it:

•
Proper indentation: Clean hierarchy showing envelope, header, and body structure
•
Well-formedness check: broken XML (an unclosed tag, a bare &) is reported with its line and column. The SOAP envelope rules themselves are not checked
•
Content left alone: text values, attributes, CDATA, comments, entities and namespace prefixes are copied exactly; only the whitespace between tags changes

Example: Beautifully Formatted SOAP Output

The same SOAP message, now properly formatted and readable:

<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Header>
    <Authentication>
      <Username>user123</Username>
      <Password>pass456</Password>
    </Authentication>
  </soap:Header>
  <soap:Body>
    <GetCustomerRequest>
      <CustomerId>12345</CustomerId>
      <IncludeOrders>true</IncludeOrders>
    </GetCustomerRequest>
  </soap:Body>
</soap:Envelope>
Step 3

Customize Formatting Options

Tailor the SOAP formatting to your preferences! Available options include:

•
Indentation size: Choose 2, 4, or 8 spaces for proper SOAP structure visualization
•
Minify option: Compress SOAP for network transmission or bandwidth optimization
•
Copy and download: Easy export options for integration into your testing workflow

Perfect for SOAP Web Services Development:

✓API Testing: Format SOAP requests and responses for testing
✓Debugging: Clean SOAP messages for easier troubleshooting
✓Documentation: Formatted SOAP for API documentation
✓Integration: Clean SOAP for system integration
✓Development: Readable SOAP for service development
✓Logging: Formatted SOAP for better log analysis

What is SOAP?

SOAP (Simple Object Access Protocol) is a messaging protocol specification for exchanging structured information in web services. It uses XML for message format and relies on application layer protocols like HTTP for message negotiation and transmission.

SOAP messages consist of an envelope containing optional header and mandatory body elements. The envelope defines the XML document as a SOAP message, headers contain application-specific information, and the body contains the actual message content. Proper formatting makes SOAP messages easier to read, debug, and maintain for developers working with web services.

Frequently Asked Questions

How do I format a SOAP message?

Paste the envelope into the left editor, upload a .xml, .soap or .txt file, or click Sample. A moment after you stop typing, the right side shows it with one element per line, indented by the 2, 4 or 8 spaces you pick under Indent. The formatter only rewrites the whitespace between tags. Element text, attribute values, CDATA, comments and entities such as &amp; stay exactly as they were, so an ID like 8901240544102066246 or a zip code like 00501 is never touched.

Can I format SOAP messages from different web service platforms?

Yes. A SOAP envelope is ordinary XML, so requests and responses from .NET WCF, Java JAX-WS, Apache CXF, PHP SoapClient, Python zeep or a SoapUI log all work, whether they use SOAP 1.1 or 1.2. Namespace declarations and prefixes like soap:, soapenv: or ns2: stay on the elements where they were written and are never reordered.

Does it check that my SOAP message is valid?

It checks one thing: that the message is well-formed XML, using your browser's XML parser. An unclosed tag, a missing quote or a bare & gives you the line, column and reason instead of output. It does not check SOAP rules, such as whether there is a Body inside the Envelope or whether the payload matches the service's WSDL.

To check plain XML on its own, try the XML validator.

Does the formatter handle SOAP faults?

Yes. A Fault is just another element inside the Body, so faultcode, faultstring and detail (or Code, Reason and Detail in SOAP 1.2) are indented like everything else. Long stack traces inside a detail element keep their own line breaks, because text content is copied as is.

What about big messages and attachments?

Large envelopes with WS-Security headers or hundreds of items are fine; everything runs in your browser, and with multi-megabyte messages the editor is what slows down first. For MTOM or SwA attachments, paste only the XML part. The binary MIME parts around it are not XML and will be reported as an error.

Need to compare the items in a long response? XML to Table shows the same message as rows.

Is the SOAP formatter free, and is my message uploaded?

It is free and needs no account. The message is formatted inside your browser and is not sent to our server, which matters when the header carries a username, token or password. Download saves soap-formatted.xml, or soap-minified.xml after you press Minify.