Skip to content

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

Try
0 characters

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.

Explore the AI terminalDownload for MacDownload for Windows

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.

Registered JWT claims and their meanings
ClaimNameMeaning
issIssuerWho issued the token. Compare with the issuer your application trusts.
subSubjectThe person or client the token describes. Its meaning depends on the issuer.
audAudienceThe intended recipient, as a string or array. Your API must be an intended audience.
expExpirationThe token expires at this time, in seconds since the Unix epoch.
nbfNot beforeThe token must not be accepted before this time.
iatIssued atWhen the token was issued. It does not set an expiration by itself.
jtiJWT IDA 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.

Related tools for your next task.

Your privacy preferences. We use product analytics to improve CtrlOps. Google Analytics cookies and live chat stay off until you allow them. Cookie policy