SAML Request Decoder
Decode Base64 SAML requests from redirect or POST bindings into readable XML.
Decode SAML requests from traces
Browser dev tools and proxy logs often show opaque SAMLRequest or SAMLResponse query
parameters or POST fields. Redirect binding uses DEFLATE-compressed, Base64-encoded XML; POST binding typically
uses plain Base64 without compression.
Paste the parameter value (URL-safe Base64 is accepted) to recover XML and read high-level fields such as
Issuer, Destination, and AssertionConsumerServiceURL. For assertion
contents inside a response, continue with the
SAML Assertion Inspector
and
SAML Condition Time Validator.
How decoding works
- Normalize URL-safe Base64 to standard alphabet and padding.
- Try raw DEFLATE inflation (redirect binding).
- If that fails, interpret bytes as UTF-8 XML (common for POST binding).
- Parse XML and surface protocol message attributes in a summary table.
Frequently Asked Questions
Can I decode SAMLResponse values?
Yes. The same Base64 and DEFLATE rules apply to responses in redirect binding; POST responses are usually plain Base64 XML.
Does this verify signatures?
No. Signature validation needs the peer certificate and canonicalization. Use this tool for readability during troubleshooting only.
Is my SAML payload uploaded?
No. Decoding uses in-browser Base64 and DEFLATE libraries only.