JWT Decoder
Decode JSON Web Tokens locally to inspect headers, payload claims, and token expiration.
Decoded locally. Decoding does not verify the signature.
Decoded locally. Decoding extracts readable claims without validating the cryptographic signature. Never paste sensitive production tokens on untrusted networks.
Status
Valid (Not Expired)
Countdown
Expires in 3353d 13h 39m 16s
Algorithm
HS256
Standard Token Claims
Issued At (iat):
11/14/2023, 10:13:20 PM
Expires At (exp):
11/30/2035, 1:46:40 AM
Issuer (iss):
Not specified
Subject (sub):
1234567890
Header: Algorithm & Token Type
{
"alg": "HS256",
"typ": "JWT"
}Payload: Data Claims
{
"sub": "1234567890",
"name": "Prajwal Acharya",
"role": "admin",
"iat": 1700000000,
"exp": 2080000000
}How It Works
- 1Paste a base64url-encoded JSON Web Token (header.payload.signature).
- 2The tool extracts and decodes the header and payload segments instantly.
- 3Inspect standard claims including exp, iat, iss, sub, and aud with human-readable timestamps and countdowns.
Example Preview
Standard JWT Token
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IlByYWp3YWwgQWNoYXJ5YSIsImlhdCI6MTUxNjIzOTAyMn0.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
Frequently Asked Questions
Does this verify the JWT signature?
No. Decoding parses base64 claims without sending your secret key over the wire. Signature verification requires the private or HMAC secret.
Will my token be saved in history or server logs?
Never. The token is decoded entirely in memory in your browser.