Decode JWT
Decode the readable header and payload of a three-part compact token locally. Inspect the claimed algorithm and numeric time fields without verifying signatures. Decoding makes no token-containing request; you can copy the formatted payload.
How to Decode a JWT and Read Its Claims
Decode JWT: how to use it
- Paste the token, with or without the Bearer prefix.
- Choose Decode token.
- Read the header, the payload and the issued, not-before and expiry times.
Limits and notes
Header and payload must be unpadded Base64URL UTF-8 JSON objects; a third segment may be empty or use the Base64URL alphabet, without cryptographic verification. Five-part compact tokens (JWE form) are unsupported; there is no key input, decryption, algorithm-policy or issuer/audience validation. The field limits user input to 100000 UTF-16 code units; JSON formatting supports nesting up to 256. Finite numeric iat, nbf and exp produce time rows in the browser time zone. Device-clock badges are not authentication decisions. Dates outside the browser range remain in the payload and show a diagnostic without a time badge. Edits keep the old result or error until Decode; the latest Decode wins and Clear prevents pending decode results or errors returning. Clear does not erase clipboard data or securely wipe browser memory.
How your privacy works →Decode JWT: common questions
Does this verify the signature?
No. Verifying needs the secret or public key of whoever issued the token. This tool only decodes the readable parts.
Is it safe to paste a real token?
Prefer the supplied public example or synthetic test data. A real token can carry credentials and private claims even after expiry. This decoder sends no token-containing decode request and provides no persistent token vault, but Copy payload deliberately writes to the clipboard. Clearing the workspace does not erase clipboard data or securely wipe browser memory.
Why can anyone read a token's contents?
In a readable three-part form, Base64URL encoding exposes the header and payload to the holder; encoding is not encryption. Verification with a trusted key, an appropriate algorithm and application checks can help detect changes. This decoder does not perform those checks, and a present signature segment proves nothing on its own. Five-part encrypted tokens are not decoded here.
Can I paste a Bearer token?
Yes, one initial case-insensitive Bearer prefix followed by whitespace is removed after trimming outer whitespace. A complete Authorization: line or additional wrapper text is not parsed as an HTTP header.
Are exp, nbf and iat seconds or milliseconds?
JWT NumericDate values are seconds since the Unix epoch, with fractions permitted. This tool uses finite numbers and multiplies them by 1000 for browser date display; it does not infer units or convert numeric strings into time rows.