Free Online JWT Decoder
Last updated: October 12, 2026
Quick answer: Debugging auth? Paste any JWT (JSON Web Token) to instantly decode its header and payload, see claims like sub, exp, and roles in readable form, and check whether the token has expired — all in your browser, tokens never uploaded.
🔒 100% Private: Data never leaves your device.
Header
—
Payload (claims)
—
✓ Free forever · ✓ No signup · ✓ Tool inputs stay in your browser — never sent to our servers.
How to Use the JWT Decoder
- Paste the full JWT (the three dot-separated segments) into the box.
- Click Decode Token — header and payload appear as formatted JSON.
- Read the expiry badge to see if the token is still valid.
- Never paste production secrets into any online tool you don't trust — this one runs 100% locally.
Why Use Our JWT Decoder?
- Instant decode — header, payload, and signature split and pretty-printed.
- Expiry check — exp/iat/nbf claims translated to human-readable dates with a valid/expired badge.
- Malformed-token detection — clear errors instead of silent garbage.
- Fully private — decoding runs in your browser; tokens never leave your device.
Common Use Cases
- Debugging login failures: Paste the token your app received and check whether it's expired, has the wrong audience, or carries unexpected claims — the fastest way to see why auth broke.
- Checking token contents before sharing: Decode first to see exactly which claims — user IDs, emails, roles — you're about to hand to support or paste into a bug report.
- Diagnosing clock-skew errors: Compare the iat/exp timestamps against the current time to spot tokens minted or expiring in the 'future' because a server clock drifted.
- Auditing third-party tokens: Inspect what data a vendor's token actually exposes about your users before you integrate it — some carry far more than the docs admit.
- Learning OAuth2 and OpenID Connect: Decode real access and ID tokens side by side to see scopes, audiences, and issuers in the wild — the concepts click faster than any diagram.
JWT Decoder vs Alternatives
- jwt.io: The classic reference decoder — also fully client-side. It adds optional signature verification when you paste a secret, which you should never do with production keys. Ours is the lighter, faster paste-decode-expiry check with a human-readable expiry badge.
- Command line (jwt-cli / Python): The right call inside a dev workflow — decode tokens in scripts and CI logs without leaving the terminal. For a one-off paste from a browser, this page is quicker.
- Browser devtools console:
JSON.parse(atob(token.split('.')[1]))decodes the payload in seconds with zero tools. Fine for developers; this page is friendlier for everyone else and adds expiry math. - Our Base64 Encoder: A JWT payload is just base64url — you can decode each segment by hand there. This page does all three segments at once, plus expiry checks and malformed-token errors.
Bottom line: jwt.io is the classic reference and the CLI wins inside a dev workflow. For the fastest paste → decode → expiry verdict with no clutter and nothing uploaded, this page is the shorter path.
Frequently Asked Questions
What is a JWT?
A JSON Web Token: three base64url segments (header.payload.signature) used for authentication. The payload carries claims like user ID and expiry.
Can this tool verify the signature?
Signature verification needs the secret key, which you should never share. This tool decodes the readable parts; verification belongs on your server.
Why does my token show as expired?
The exp claim is a Unix timestamp. If it's in the past, the token is expired — request a fresh one from your auth server.
Is it safe to paste tokens here?
This tool runs entirely in your browser and never transmits your token. As a rule, prefer decoding tokens locally rather than on unknown sites.
What's the difference between JWT and JWE?
JWTs are signed but readable (payload is only base64-encoded). JWE tokens are encrypted and can't be decoded without the key.
Why does a decoder show 'invalid signature'?
Decoders don't have your secret key, so they can't verify the signature — that message is normal and expected. Only your server, holding the secret, can truly verify a token.
How do I decode a JWT in Python or JavaScript?
In Python:
jwt.decode(token, options={"verify_signature": False}) with PyJWT. In Node: JSON.parse(Buffer.from(token.split('.')[1], 'base64').toString()). Both give you the payload dict — the same thing this page shows.What's the difference between an access token and an ID token?
In OpenID Connect, the ID token describes the user (who they are); the access token authorizes API calls (what they're allowed to do). Decode both here to see which claims each carries.
Why is my JWT so long?
Tokens grow with their claims — embedded permissions, roles, and profile data bloat the payload. Long tokens inflate every HTTP header; keep claims minimal and move bulky data to your database.
What does 'alg: none' mean in a token header?
An unsecured JWT with no signature — anyone can forge one. The infamous 'alg: none' attack tricked servers into accepting unsigned tokens. Never accept alg:none tokens from untrusted sources.
Can I edit a JWT's payload to change my role?
You can decode and re-encode the payload, but the signature will no longer match — any correctly implemented server rejects the tampered token. Only the issuer, holding the signing key, can mint valid tokens.