Free JWT Decoder & Verifier: Decode and Verify JWT Online
Read the claims. Check the signature. Understand the difference.
Free · No signupDecoded and verified in your browser
JWT decoder and verifier
Decoded data is readable, not encrypted. The token and verification key stay in this page’s memory.
See what’s inside your token.
Paste a JWT to inspect its header and payload, or try a sample above.
Decoding requires no key. Verification does.Runs locally. Tokens and keys are not uploaded, stored in the URL, or saved to browser storage.
From a token to the request behind it
Keep debugging your API in CtrlOps.
Inspect server logs, edit configuration and work in the terminal from one local desktop workspace.
Read the payload
Small names.
Useful claims.
These registered claims have defined meanings. Their presence alone does not prove who issued the token or what a user is allowed to do.
| Claim | Name | Meaning |
|---|---|---|
iss | Issuer | Who issued the token. Compare with the issuer your application trusts. |
sub | Subject | The person or client the token describes. Its meaning depends on the issuer. |
aud | Audience | The intended recipient, as a string or array. Your API must be an intended audience. |
exp | Expiration | The token expires at this time, in seconds since the Unix epoch. |
nbf | Not before | The token must not be accepted before this time. |
iat | Issued at | When the token was issued. It does not set an expiration by itself. |
jti | JWT ID | A token identifier. Replay protection still requires application-side state or policy. |
What the tool checks
Readable is not
the same as trusted.
Decode without sending your token anywhere
Paste a compact JWT, a Bearer token or an Authorization header. The first two Base64url segments decode to JSON: a header describing the signing algorithm and a payload containing claims. The signature is the third segment. Signed tokens are usually readable; Base64url is encoding, not encryption.
Verify with an algorithm and key you trust
Choose the expected algorithm from your issuer’s configuration. For HMAC, enter the exact shared secret and its encoding. For RSA, RSA-PSS or ECDSA, paste the public key or a trusted JWKS. Verification uses the jose library and the browser’s Web Crypto API. Token-provided URLs and embedded keys are not used to establish trust.
Then check the claims
A matching signature can belong to an expired token, the wrong audience or a different issuer. Enter your expected issuer and audience to inspect those separately. Expiration and not-before checks use your device clock, with zero clock tolerance by default. The readable claims view shows NumericDate timestamps in UTC and your local timezone.
Keep application policy in your application
This page is a debugging tool. It does not check revocation, permissions, session state or every token profile’s requirements. Your API must enforce those rules before granting access. For the protocol and implementation guidance, see RFC 7519 and JWT Best Current Practices.
A few useful answers
JWTs,
explained.
Yes. Decoding and signature verification run entirely in your browser using the Web Crypto API - the token, the secret, and any key you paste are never sent to a server or logged. That said, treat real access tokens carefully anywhere, and prefer expired or test tokens when you can.
Yes. The header and payload of a JWT are only Base64URL-encoded, not encrypted, so they can always be decoded without any key. You only need a secret or public key to verify the signature - that is, to prove the token is authentic and unmodified.
Paste the token, choose the algorithm configured by your issuer, and provide the matching key. For HS256/384/512 that is the shared secret. For RS, PS, or ES algorithms it is the issuer’s trusted public key, which you can paste as a PEM public key, public JWK, JWKS, or X.509 certificate. Choose Verify signature to check it. Signature matches or Signature mismatch is reported separately from expiration and other claim checks.
The exp claim is a Unix timestamp; at that time, a correct server must stop accepting the token, subject to any configured clock tolerance, even if its signature still matches. This tool shows expiration separately from the signature result. The Readable claims tab converts exp, iat, and nbf into local and UTC times.
No. A standard JWT (a JWS) is signed, not encrypted. The signature guarantees the contents were not changed, but the payload is fully readable by anyone who has the token. Never store passwords or sensitive data in a JWT payload. If you need the contents hidden, use an encrypted JWE instead.
HS256 uses a single shared secret to both sign and verify, so anyone who can verify can also create tokens. RS256 uses a key pair: the issuer signs with a private key and everyone else verifies with the public key, so verifiers can never mint their own tokens. Use HS256 for a single self-contained service and RS256 when tokens are issued centrally and verified in many places.
alg: none is a JWT that declares it has no signature. If a server trusts the algorithm named in the token header, an attacker may strip the signature, set alg to none, and forge claims. This tool flags unsigned tokens and refuses to verify them. Servers should enforce their configured expected algorithm rather than accept whatever the token requests.
All the common JWS algorithms: HS256/384/512 (HMAC), RS256/384/512 (RSA PKCS#1 v1.5), PS256/384/512 (RSA-PSS), and ES256/384/512 (ECDSA). Verification uses the browser Web Crypto API, so no data leaves your machine.
Keep debugging
Related tools for your next task.