How to decode a JWT
- Paste the token. A leading
Beareris ignored, so an Authorization header value works as is. - Header and Payload appear as JSON. Claims shows
exp,iatandnbfas UTC dates with how long ago or how soon, plus issuer, subject, audience and token ID. - For an HS256, HS384 or HS512 token, enter the shared secret under Verify HS256 / HS384 / HS512 signature and press Verify.
Example
Signed with HS256 and the secret kitchen-table-42:
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJodHRwczovL2xvZ2luLmV4YW1wbGUub3JnIiwic3ViIjoic3ZjLXJlcG9ydHMiLCJhdWQiOiJyZXBvcnRzLWFwaSIsInNjb3BlIjoicmVwb3J0czpyZWFkIiwiaWF0IjoxNzkwODQxNjAwLCJleHAiOjE3OTA4NDUyMDB9.5Wcs1uZjdO41tDjsl5b7M1CKVW23Yc6Un_p3ygZ26co
Payload:
{
"iss": "https://login.example.org",
"sub": "svc-reports",
"aud": "reports-api",
"scope": "reports:read",
"iat": 1790841600,
"exp": 1790845200
}
Claims shows iat as 2026-10-01 08:00:00Z and exp as 2026-10-01 09:00:00Z, marked expired: a one-hour token. With the secret, Verify says Signature verified.; any other secret gets Invalid signature for this secret.
Decoded locally
A JWT is a bearer credential: whoever holds an unexpired token can use it. Decoding needs only Base64URL and JSON parsing, so this page does it in JavaScript and checks HMAC signatures with the browser’s Web Crypto API. The token and secret are never sent or saved, a reload clears them, and once loaded the page keeps working offline.
What the JWT decoder does not do
- RS256, ES256 and other public-key algorithms need the issuer’s public key, which this tool does not take; Verify says
Only HS256, HS384 and HS512 can be checked with a secret. - Decoding is not verification. Anyone can write a token with any payload; only a valid signature proves who issued it.
- Encrypted tokens (JWE) have five parts. Their payload cannot be read without the key, and the tool says so.
A single segment also decodes in Base64 to JSON. Compare two payloads in JSON diff, or browse a long one in the JSON formatter.