What is inside a JWT
A JWT has three parts separated by dots:
- Header: the signing algorithm, such as HS256 or RS256.
- Payload: the claims, such as who the user is (
sub), when the token was issued (iat) and when it expires (exp). - Signature: proves the first two parts were not changed.
The first two parts are only Base64URL-encoded, not encrypted. Anyone holding the token can read them, which is why this tool can decode it without a key.
What to check when a login fails
expin the past: the token has expired; the client should refresh it.nbfin the future: the token is not valid yet, often a clock difference between servers.- Wrong
audoriss: the token was issued for another app or by another server. alg: none: an unsigned token. Your server must never accept it.
Keep tokens safe
A JWT works like a password until it expires. Never paste production tokens into tools that send them to a server. This decoder runs entirely in your browser.
Frequently asked questions
Can this tool verify a JWT signature?
No. Verifying needs the secret or public key, which should never leave your server. Decoding only shows what the token contains.
Is a JWT encrypted?
A normal signed JWT (JWS) is only encoded, so anyone can read its contents. Don't put secrets in the payload. Encrypted tokens (JWE) have five parts and can't be read without the key.
Why does my token show as expired?
The exp claim is earlier than the current time on your device. Get a fresh token, and check that your server and device clocks are correct.
Sources
The rules and figures in this tool come from these official sources, last checked November 12, 2026.
- RFC 7519: JSON Web Token (JWT) rfc-editor.org