JWT Decoder
Decode JSON Web Token headers and payloads, inspect registered claims, and understand token status.
Encoded Token
132 / 100,000 bytes
Header
Algorithm and token type
{
"alg": "HS256",
"typ": "JWT"
}
Payload
Claims and application data
{
"sub": "1234567890",
"name": "ToolNest User",
"iat": 1719792000
}
Issued At
Jul 1, 2024 00:00:00 UTC
Expires At
Not provided
Signature
Present - not verified
Token decoded. No numeric expiry claim was found.
How to Use
- 1Paste JWTAdd the complete encoded token.
- 2DecodeParse header and payload JSON.
- 3Inspect ClaimsReview issuer, subject, and timestamps.
- 4Verify SeparatelyValidate the signature in your backend.
Technical Specs
- Maximum Size
- 100 KB
- Encoding
- Base64URL
- Time Zone
- UTC
- Signature
- Displayed, not verified
Related Tools
Security note
Decoding is not verification
Anyone can decode a JWT. Never trust its claims until your backend verifies the permitted algorithm, signature, issuer, audience, and time-based claims using trusted keys.
Frequently Asked Questions
Does decoding verify the signature? +
No. Decoding only reveals token content; verification needs the expected key and security policy.
Is my JWT stored? +
No database persistence or token history is used.
How is expiration detected? +
A numeric exp claim is compared with the current UTC Unix timestamp.
Can JWT payloads contain secrets? +
They should not. JWT payloads are encoded, not encrypted.
Related Articles
Developer newsletter
Stay Ahead
Get practical developer guides, new tools, and workflow improvements without inbox noise.