JWT Decoder and Verifier
Decode and verify JSON Web Tokens locally in your browser. Tokens and keys never leave your device.
- Runs in your browser
- Nothing is uploaded
- Ctrl/⌘ + Enter runs it
Paste a JWT or load the example. Nothing leaves your browser.
Decoded parts appear here.
Header
Payload
How to use this tool
- Paste the JWT, with or without the "Bearer" prefix, or load the example.
- Read the decoded header, payload and time claims.
- Paste the secret or public key that should have signed it.
- Select Verify signature and read the verdict.
Quick answers
Is it safe to paste a JWT into this decoder?
Yes. Decoding and verification run entirely in your browser with the Web Crypto API. The token, secret and public key are never sent over the network or stored.
Can this tool verify a JWT signature?
Yes. Paste the shared secret for HS256, HS384 or HS512 tokens, or the public key as PEM or JWK for RS, PS and ES algorithms, then select Verify signature.
Why is my JWT reported as expired?
The exp claim holds the expiry time in seconds since 1970. If that moment is in the past, the token is expired and servers should reject it.
Common use cases
- Inspect claims in an access token
- Check why a token is rejected
- Verify a signature with a secret or public key
What this tool does
- Decode the header and payload of signed JWTs into readable JSON
- Show exp, nbf and iat as UTC dates and flag expired or not-yet-valid tokens
- Verify HS256/384/512, RS256/384/512, PS256/384/512 and ES256/384/512 signatures with the browser's Web Crypto API
- Keep live tokens, secrets and keys on your device: nothing is uploaded or stored
Examples
Debug a 401 response
Paste the bearer token from a failing request and check whether it has expired, is not valid yet, or carries the wrong audience.
Confirm a signing key
Paste the shared secret or the provider's public key to confirm the token was signed with it before blaming the API.
Common issues
- A token with "alg": "none" is unsigned and must never be trusted.
- exp and nbf are seconds since 1970, not milliseconds.
- Base64url is not plain Base64: "-" and "_" replace "+" and "/", and padding is usually dropped.
- Encrypted tokens (JWE, five parts) cannot be decoded without the private key.
Privacy and security
Everything runs in your browser. Your data never leaves your device. The tool logic runs locally and does not send your input, output, files, or generated values to analytics.
FAQ
Is my token sent to a server?
No. The token and any key you paste stay in your browser; nothing is uploaded or saved.
Which algorithms can be verified?
HS256, HS384, HS512, RS256, RS384, RS512, PS256, PS384, PS512, ES256, ES384 and ES512.
Which key formats are accepted?
A text or base64-encoded secret for HS algorithms, and a PEM public key (BEGIN PUBLIC KEY) or a JWK for RS, PS and ES algorithms.
Can it decode encrypted tokens?
No. Encrypted tokens (JWE) need the recipient's private key; this tool decodes and verifies signed tokens (JWS).