Skip to main content
WizTools123
Free Online Tools

Tool Categories


Security Tools New Tool

Free Online JWT Decoder, Signature Verifier and Token Builder

Read what is inside a JSON Web Token, check that its signature is genuine, and sign a token of your own for testing. The header and payload are shown as formatted JSON with the times turned into real dates, the signature is checked against a shared secret or an RSA public key, and the issuer and audience can be checked too.

Free Forever Nothing Uploaded Expiry Checked Reads Only
Free Online JWT Decoder, Signature Verifier and Token Builder
Share this tool
Advertisement Slot (Top Banner) Google AdSense Unit • Responsive Banner
JWT Decoder Everything happens in this tab. Nothing you paste is sent anywhere.
Your token
Inside the token

Header
Payload
Time claimWhen (UTC)
What for
Key
Secret
Also check
Sign with
Add
seconds, blank for no exp
Buy Us A Coffee

Enjoying WizTools123? Help keep our server infrastructure 100% free and open for everyone.

Buy Us A Coffee
Sponsored Content (Below Tool) Google AdSense Placement

How to Use JWT Encoder and Decoder

Step by step, start to finish.

1
Paste your JWT

The whole thing, header.payload.signature. It is decoded the moment you paste, and reading it needs no key at all.

2
Read the header, the payload and the times

Both parts as formatted JSON, the algorithm named, and the issued, not-before and expiry claims turned into real dates.

3
Check the signature, if you want to

Switch to Verify and give it the shared secret or the RSA public key. The expected issuer and audience can be checked at the same time, because a valid signature on its own is only half the answer.

4
Or sign a token for a test

Switch to Make, write the payload as JSON and sign it with HS256, HS384 or HS512. What comes out is a real token, so use a test secret.

Key Features

What this tool does, and what it does not do.

Header and payload

Both shown as formatted JSON, with the algorithm named.

Times as dates

Issued, not-before and expiry turned from seconds into readable UTC dates.

Expiry checked

Marked expired, not yet valid, or current against your own clock.

Signature checked

Against a shared secret or an RSA public key, by the browser own Web Crypto.

Signs test tokens

HS256, HS384 or HS512 with your own payload, iat and expiry.

Nothing uploaded

A real session token can be inspected here without it leaving the tab.

About JWT Encoder and Decoder

A JWT turns up whenever you are working with authentication: a session token, an API key in bearer form, a link that logs someone in. It looks like a wall of Base64, and the quickest way to understand a bug is to see what is actually inside it. That is what this does, in your browser, the moment you paste one in.

It shows the header and the payload as readable JSON, names the signing algorithm, and turns the cryptic timestamps into real dates, then tells you whether the token has expired. If you want more than that it will check the signature, against an RSA public key, which is not a secret at all, or against a shared secret, which is. It will also sign an HMAC token with a payload of your own, which is the quickest way to get a token for exercising an endpoint.

The tool doubles as a reminder of two things people get wrong about JWTs: the payload is readable by anyone, so nothing secret belongs in it, and the token is signed but not encrypted, so being able to read it is the format working correctly. Decoding a token you hold shows you exactly what any recipient can see, which is often the point of checking.

Frequently Asked Questions

Common questions about this tool.

Yes. For RS256, RS384 and RS512 it needs only the public key, which is published on purpose and costs you nothing to paste. For HS256 and its relatives it needs the shared secret, so use a test secret rather than your live signing key. Nothing typed here leaves the tab, which you can confirm in the Network tab.

No, and that is deliberate. Signing with RSA means pasting a private key, which is the one thing that should never be typed into a browser. The signing side stops at HMAC, and verification is offered for RSA because the public half is all it needs.

The decoding happens entirely in your browser, so the token is not uploaded. That said, a token in your clipboard history or on screen is still a live credential until it expires. Decode it, learn what you need, and treat it as you would any password.

Yes, and so can anyone else. The header and payload are only Base64URL-encoded, not encrypted, so no key is needed to read them. That is why you must never put anything sensitive in a JWT payload; the signature stops it being changed but not being read.

The expiry is judged against your computer's clock. If your clock is wrong, or the token uses a timezone you did not expect, the verdict can look off. The exact expiry time is shown as a UTC date so you can check it against the real time yourself.

No. It is decoded in your browser with no server involved, which is why inspecting a real session token here is reasonable. You can confirm it in the Network tab or by working offline.
Advertisement Slot (Bottom Banner) Google AdSense Unit • Responsive Banner