109 chars · 1 line
132 chars · 10 lines
109 chars · 1 line
132 chars · 10 lines
JWT claim troubleshooting
A payload can be valid JSON and still omit aud. The decoder therefore succeeds, but applications that require audience restriction must enforce that requirement in their verifier instead of treating decode success as authorization. This tool is free to use. No account or payment is required.
Last updated
This decoder intentionally does not invent required-claim rules. A trusted service must decide whether aud is mandatory for the token type it accepts.
The issuer is present but no audience restriction is encoded.
{"sub":"123","iss":"https://issuer.example"}Require aud only if your token contract says it is mandatory.Common questions
Yes. Decoding only requires structurally valid token segments and JSON objects.
That depends on the token profile and verifier policy. Many APIs intentionally require it.
No. It only displays the claim data locally.
Debugging a specific JWT issue? Browse JWT troubleshooting.