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.
| Time claim | When (UTC) |
|---|
Enjoying WizTools123? Help keep our server infrastructure 100% free and open for everyone.
How to Use JWT Encoder and Decoder
Step by step, start to finish.
The whole thing, header.payload.signature. It is decoded the moment you paste, and reading it needs no key at all.
Both parts as formatted JSON, the algorithm named, and the issued, not-before and expiry claims turned into real dates.
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.
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.
Both shown as formatted JSON, with the algorithm named.
Issued, not-before and expiry turned from seconds into readable UTC dates.
Marked expired, not yet valid, or current against your own clock.
Against a shared secret or an RSA public key, by the browser own Web Crypto.
HS256, HS384 or HS512 with your own payload, iat and expiry.
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.