Skip to content
Tools

JWT decoder & encoder

Decode and edit JSON Web Tokens. Signatures are not verified.

HeaderPayloadSignature
Signature verified

About the JWT decoder & encoder

This JWT decoder splits a JSON Web Token into its header, payload, and signature and shows the decoded JSON for each. Use it to inspect the claims in an access or ID token, see which signing algorithm the header declares, or check when a token expires.

How to use it

  1. Paste a token into the Encoded box. The three parts are color-coded to match the Header, Payload, and Signature legend.
  2. Read the decoded JSON in the Header and Payload fields.
  3. If the payload has an exp claim, check the status below the token, which shows Expires in or Expired with the time remaining or elapsed.
  4. Edit the Header or Payload JSON to build a new token, signed with the Secret, and use the copy buttons to copy the token, header, or payload.

Checking the signature

For HS256, HS384 and HS512 tokens, the signature is checked against the Secret field: the status shows Signature verified or Invalid signature, and changing the secret checks again without altering the token. RS, ES and PS tokens need a public key, which this tool does not take, so their signatures are not checked.

Signing

Editing the header or payload builds a new token, HMAC-signed with the Secret using the browser's Web Crypto API when the alg is HS256, HS384 or HS512. For other algorithms the signature part is left empty. A pasted token is never rewritten.

Privacy

Decoding runs in your browser, and the token you paste is not sent to a server.

Questions

Is a JWT encrypted?
A standard signed JWT (JWS) is not encrypted. The header and payload are only Base64URL-encoded, so anyone with the token can read them. Don't put secrets in the payload.
What do the exp, iat, and sub claims mean?
exp is the expiration time and iat is the time the token was issued, both as Unix timestamps in seconds. sub identifies the subject, usually the user the token was issued for.
Can I decode a JWT without the secret?
Yes. The secret or private key is only needed to create or verify the signature. Reading the header and payload requires nothing but Base64URL decoding.