Encoded token
Paste a three-part JWT, with or without a Bearer prefix. This browser processes the token and key locally.
Examples
Header Payload Signature
Decoded JSON
Header
—
Payload
—
Verify signature
Use a shared secret for HMAC or an SPKI public key (PEM) for RSA or ECDSA. This checks only the signature.
Registered claims
Times are shown in your local time zone and in UTC, and compared with your device clock.
Custom claims
Raw token segments
Header
Payload
Signature
Does decoding a JWT verify its signature?
No. Decoding reads the header and claims without a key. To verify the signature, select the expected algorithm and supply its key. Your application still needs to check the issuer, audience and applicable time claims.
Choose Signed HS256 under Examples. The token is decoded, the expected algorithm is preselected from its header, and the demo key verifies it at once. Change one character of the key to see Invalid signature, then load Unsigned · expired to see how exp is marked against your device clock.