Runs 100% locally — your token never leaves this page.
Header (JOSE)
-
Payload (Claims)
-
Time claims
| Claim | Unix | Local time | Status |
|---|
Verify signature (HS256/384/512)
How to Use
- Paste a JWT (a 'Bearer ' prefix is removed automatically) — header and payload decode instantly with a structure/expiry status banner.
- Check the claims table for human-readable iat, exp, nbf and auth_time values with local times.
- Optionally paste your secret to verify HS256/384/512 signatures — everything stays on your device.
Registered JWT claims
| Claim | Name | Meaning |
|---|---|---|
| iss | Issuer | Who created and signed the token |
| sub | Subject | Whom the token refers to |
| aud | Audience | Intended recipients |
| exp | Expiration | Unix seconds — reject after |
| nbf | Not Before | Unix seconds — valid from |
| iat | Issued At | Unix seconds — issue time |
| jti | JWT ID | Unique identifier, replay defense |
Frequently Asked Questions
Is it safe to paste a production JWT here?
Yes — decoding and HMAC verification run entirely in your browser via atob and crypto.subtle. The token is never sent anywhere (you can even go offline).
Which algorithms can be verified?
HS256, HS384 and HS512 are verified with your secret (UTF-8 text or Base64URL). Asymmetric algorithms (RS256, ES256, EdDSA) are decoded but not verified — public-key verify needs the issuer's JWK.
What do iat / exp / nbf mean?
iat = issued at, exp = expiration, nbf = not-before — all Unix seconds. The claims table renders them as local times plus live relative status.
Why does my token fail to decode?
A JWT needs three Base64URL segments separated by dots (header.payload.signature). A 'Bearer ' prefix is stripped automatically — check for truncation or stray whitespace.