JWT Decoder
DEVDecode JWT header and payload claims, check expiry and verify HS256 signatures.
About JWT Decoder
Frequently asked questions
Does decoding a JWT prove it is valid?
No. Decoding only converts Base64URL text into JSON. A token could be expired, forged or signed with a different key and still decode perfectly. You must verify the signature and validate the issuer, audience, expiry and not-before claims before trusting it.
Is it safe to paste a JWT into this tool?
The token is decoded locally with JavaScript and is not uploaded. That said, JWTs can contain sensitive claims, so use a test token when possible and avoid pasting long-lived production credentials into any browser tool.
Why can I not verify RS256 or ES256 tokens here?
Asymmetric verification needs the issuer’s public key or a JWKS document plus algorithm-specific handling. This tool focuses on HMAC verification, which only needs a shared secret. Use your identity provider or a JWKS-aware verifier for RS256 and ES256.
What do exp, iat and nbf mean?
exp is the expiry time, iat is when the token was issued and nbf is the earliest time it may be accepted. All three are Unix timestamps in seconds. The claims table converts them to local dates and shows whether they are in the past or future.
Quick tips
- Use the copy button to move formatted output straight into your editor.
- Validation errors point to the exact position in your input.
- All formatting and checks happen locally - nothing is uploaded.