- Home
- Generators & Encoders
- JWT Encoder / Decoder
JWT Encoder & Decoder
Paste a token to read its header and payload. Or fill header, payload and a secret, then sign an HS256 token. Reading a token does not prove the signature is valid. RSA keys are not accepted here.
What it is for?Decode
Encode HS256
What it is for?
Use this page when a login fails and you want to see what the token actually says: who it is for, which claims it carries, and when it expires. You can also sign a test token for a local API that uses a shared secret.
Decode is not verify
A JSON Web Token (JWT) is three pieces of text joined by dots: header, payload, signature. The middle piece is only Base64. Anyone can read it without the secret. This page shows that JSON. It does not check the signature, so a forged token still “decodes”. If the header says alg=none, there is no signature at all.
Expiry and claims
If the payload has an exp claim, the page tells you whether that time has passed and shows it in ISO 8601. exp, iat and nbf are seconds since 1970, not milliseconds. Other claims such as nbf, iss or aud are shown as they are, but not checked.
Signing
Sign token builds header.payload.signature with HMAC-SHA256 in this browser. The header is forced to alg HS256. You must type a secret; an empty secret is refused. RS256 and ES256 need a private key file. This tool does not take those files.
The secret is used as plain UTF-8 text. Some libraries expect a Base64-encoded secret and decode it first; then the signatures will not match. The new token is also copied into the decoder, so you can check the result at once.
It stays in the browser
The token and the secret are not sent to a server. They sit in this tab’s memory until you close it. Do not paste a live production secret unless you accept that.