JWT Decoder
Decode JWT header and payload locally without claiming signature verification.
Read the guideRun the tool
The calculation runs in your browser. This tool does not send your input to JVR Software.
More information
Back to the toolWhat it is and when to use it
JWT Decoder shows the readable header and claims inside a JSON Web Token. It helps developers inspect expiry, issuer and audience during authorised debugging and compare test tokens from a sign-in integration. Reading claims and verifying that those claims can be trusted are separate tasks.
How it works
A signed JWT usually contains three Base64URL segments separated by dots. The tool decodes and parses the first two segments as JSON and reports whether a third segment was present. It does not compare a signature with a key, decrypt a token, or validate application-specific claims.
How to use it
- Use a synthetic token or one created specifically for your own test environment.
- Paste the complete token as text without a Bearer prefix and run the decoder.
- Treat every returned claim as unverified and check it against the settings of your authorised application.
Worked example
An exp claim typically represents an instant in Unix seconds. If it reads 1700000000, use Unix Timestamp Converter to inspect the equivalent UTC date. The decoded header can also show the algorithm label chosen by the token issuer.
Reading the result
iss normally identifies the issuer, aud the intended audience, and exp the expiry. A signaturePresent value only means the third segment contains text. It does not establish authenticity or the right of anyone to use that token.
A readable exp, nbf or iat claim is a timestamp assertion made by whoever produced the input. Use Timestamp Converter to inspect the time in UTC. A trusted verifier must establish the signature and apply the expected issuer, audience and time rules before using those claims to grant access.
Common mistakes and limits
A real access token can function as a credential even when copied into an offline note. Avoid pasting production tokens into general workspaces and never publish decoded claims with private identifiers. Use your application library and trusted issuer keys for real validation.
