Developer Tools

JWT Decoder & Encoder

Decode any JWT, verify its HS256/384/512 signature, create your own signed tokens — even decode single-payload tokens. 100% in your browser.

Signature NOT verified automatically — decoding only reveals a token's contents. Use the signature section below with your secret to verify it, or treat the token as untrusted. Everything runs in your browser; tokens are never sent anywhere.
Paste a token — it decodes automatically as you type.

What is a JWT decoder?

A JSON Web Token (JWT) is three Base64URL-encoded parts joined by dots: a header (algorithm and token type), a payload (claims like user id and expiry), and a signature. Servers pass JWTs around for authentication, and when something goes wrong — an expired session, a wrong role, a clock-skew rejection — the fastest diagnosis is to look inside the token. This tool splits the parts, decodes the header and payload into readable JSON, translates the exp, iat, and nbf timestamp claims into human dates with plain-English validity notes, verifies HS256/384/512 signatures with your secret, and can even generate fresh signed tokens in the Create tab.

How to Use the JWT Decoder Online

  1. Paste the full JWT (header.payload.signature) — or a single base64 payload token — into the box. It decodes automatically as you type.
  2. Read the header and payload as pretty-printed JSON, with one-click copy.
  3. Check the time-claims card: expiry date, whether the token is expired, when it was issued, and whether it is not yet valid.
  4. Paste your HMAC secret in the signature section to verify HS256 / HS384 / HS512 signatures — or switch to the Create tab to build your own signed token.

JWT Decoder — Key Features

JWT Decoder — Common Use Cases

JWT Decoder — Practical Tips

Frequently Asked Questions

What are the three parts of a JWT?
Header (signing algorithm and token type), payload (the claims, like subject and expiry), and signature — each Base64URL-encoded and joined by dots. This tool decodes the first two and can verify the third.
Can this tool verify a JWT signature?
Yes — for tokens signed with HS256, HS384 or HS512. Paste your HMAC secret in the signature section and the tool recomputes the signature in your browser and tells you whether it matches. Decoding alone never proves authenticity.
Can I create a JWT here?
Yes. The Create tab lets you edit the header and payload JSON, choose HS256, HS384, HS512 or none, sign with your secret, and copy the finished token — all client-side.
What if my token has only one part instead of three?
Some services issue compact single-payload tokens that are just one Base64 string with no header or signature. This tool detects them and decodes the payload automatically.
What do exp, iat, and nbf mean?
exp is when the token expires, iat is when it was issued, and nbf is the earliest time it becomes valid — all as seconds since the Unix epoch. The tool converts them to readable dates and flags expired or not-yet-valid tokens.
Is the payload encrypted?
No. The payload is merely Base64URL-encoded, which anyone can decode — including with this tool. Never put secrets in JWT claims.
Why does my token fail to decode?
Usually it is truncated (missing a part), has whitespace or line breaks pasted in, or is not a JWT at all. The tool reports which part failed so you can fix the paste.
How do I read a JWT token?
Paste the token — the decoder instantly shows the header, payload claims and signature details.
Is it safe to paste my JWT here?
Yes — decoding and verification happen locally in your browser. Tokens are never sent to any server.