Developer utility

JWT decoder

Decode a JSON Web Token: header, payload, expiry and signature verification. The token never leaves your browser

Decoding happens in the browser: the token and the secret are not sent anywhere

What a JWT consists of

  • • Header — token type and signing algorithm.
  • • Payload — the data: who issued the token, for whom, when it expires, and any application fields.
  • • Signature — the signature of the first two parts. It protects the token from forgery but does not hide its contents.
  • • JWT contents are not encrypted — anyone holding the token can read them. Do not put passwords or personal data in it.

JWT: how the token is built and how to read it

What a JWT is

A JSON Web Token is a compact way to pass information about a user between services. After login the server issues a token and the client attaches it to every request; the server does not need to store a session — verifying the signature is enough.

A token consists of three Base64URL-encoded parts: a header with the signing algorithm, a payload with the data, and the signature itself.

Common security mistakes

Storing confidential data in the token: the contents are readable without a key. Accepting tokens with the “none” algorithm — they are unsigned. Using a short or predictable HS256 secret that can be brute-forced. Issuing tokens with no expiry — a stolen token then works forever.

On the server, always verify the signature, the expiry and the iss and aud claims, and set the algorithm in code rather than taking it from the token header.

Frequently asked questions

How do I decode a JWT?+

Paste the token into the field — the header and payload are shown as JSON right away. There is no need to remove the “Bearer” prefix or surrounding quotes; the decoder strips them.

Is it safe to paste a production token here?+

Decoding and signature verification run in the browser: neither the token nor the secret is sent to a server. Still, a live token is a key to an account — do not leave it in open tabs and chats, and if in doubt revoke it and issue a new one.

Can a token be read without the secret key?+

Yes. The JWT header and payload are not encrypted, only Base64URL-encoded — anyone with the token can read them. The secret is needed only to verify or create the signature.

How do I verify the signature?+

For HS256, HS384 and HS512 enter the secret in the “Signature” block — the decoder recomputes the signature and tells you whether it matches. RS256, ES256 and other asymmetric algorithms need the issuer’s public key; the tool does not perform that check.

What do exp, iat and nbf mean?+

They are Unix timestamps: exp — when the token expires, iat — when it was issued, nbf — when it becomes valid. The decoder converts them to a readable date and shows whether the token is valid now.