JWT Decoder icon

JWT Decoder & Verifier

Paste a JSON Web Token to read its claims, check whether it has expired and verify its signature.

100% FreeNo Signup RequiredPrivacy Friendly
Header
Payload

Claims

Verify the signature

Paste the secret or public key to check the signature – it is verified in your browser and never sent anywhere.

JWT Decoder

A JSON Web Token has three Base64URL parts: a header (algorithm and type), a payload of claims (user ID, expiry, roles) and a signature. The JWT decoder shows the header and payload as formatted JSON, turns timestamps like exp and iat into readable dates and tells you whether the token has expired.

To check that a token is genuine, paste the shared secret (HS256/384/512) or the public key as PEM or JWK (RS, PS and ES algorithms). Verification uses the browser’s Web Crypto API, so tokens and keys never leave your device.

Last updated November 17, 2026 · Reviewed by the ToolsPoint team

How to Use JWT Decoder

  1. Paste the JWT (a “Bearer ” prefix is removed automatically).
  2. Read the header, payload, claims and expiry status.
  3. Optionally paste the secret or public key and click Verify signature.

JWT Decoder Features

  • Readable claims: exp, iat and nbf as dates, with expiry status.
  • Signature verification: HS256/384/512, RS256/384/512, PS256/384/512 and ES256/384/512.
  • PEM and JWK keys: paste either format.
  • Warnings: flags alg: none and encrypted JWE tokens.
  • Local only: uses Web Crypto in your browser.
  • Free and unlimited: use it as often as you like without registering.
  • Privacy-first: files and text never leave your computer or phone.
  • Works everywhere: Windows, macOS, Linux, ChromeOS, iPhone, iPad and Android in any modern browser.

Standard Claims

ClaimMeaning
issWho issued the token
subWho the token is about (user ID)
audWho the token is for
expExpiry time (Unix seconds)
nbfNot valid before
iatIssued at
jtiUnique token ID

Security Reminders

  • Decoding is not verifying – anyone can read a JWT payload, so never put secrets in it.
  • Always verify the signature on the server and reject alg: none.
  • Treat production tokens like passwords: don’t paste them into tools that send data to a server. This one doesn’t.

Who Uses the JWT Decoder?

  • Developers debugging authentication
  • Checking token expiry and scopes
  • Security reviews and API testing

Frequently Asked Questions

Is it safe to paste my token here?
The token is decoded and verified locally in your browser; nothing is uploaded. Still, avoid sharing live production tokens in screenshots or chats.
Why does verification fail with the right secret?
Check whether the secret is Base64-encoded (tick the option), that there are no extra spaces or line breaks, and that the token was not modified.
Can it decode encrypted tokens (JWE)?
It recognizes 5-part JWE tokens and shows the header, but the payload can only be read with the decryption key.
What format should the public key be in?
A PEM public key (-----BEGIN PUBLIC KEY-----) or a JWK object, for example one key from a JWKS endpoint.
What is the difference between HS256 and RS256?
HS256 uses one shared secret to both sign and verify, so every service that verifies tokens can also create them. RS256 uses a private key to sign and a public key to verify, which is safer when many services need to check tokens but only one should issue them.
Why is my token rejected even though it isn’t expired?
Common causes are a wrong audience (aud) or issuer (iss), a not-before (nbf) time in the future, clock differences between servers, or a signature made with a different key.

Get new free tools in your inbox

One short email a month with new tools, guides and productivity tips. No spam — unsubscribe anytime.

By subscribing you agree to receive emails from ToolsPoint Online. See our Privacy Policy.