Skip to content

JWT Decoder

Decode a JSON Web Token to read its header and payload, with exp, iat and nbf shown as dates. The signature is not verified.

Runs in your browserJWT → JSON
Loading tool…

Example

Input
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkFkYSBMb3ZlbGFjZSIsImlhdCI6MTUxNjIzOTAyMiwiZXhwIjoxNTE2MjQyNjIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
Output
Header
{
  "alg": "HS256",
  "typ": "JWT"
}

Payload
{
  "sub": "1234567890",
  "name": "Ada Lovelace",
  "iat": 1516239022,
  "exp": 1516242622
}

Claims
iat (issued at): 2018-01-18T01:30:22.000Z
exp (expires): 2018-01-18T02:30:22.000Z (expired)
sub: 1234567890

Signature: present (HS256) but NOT verified. Decoding does not prove the token is genuine.

How to use the JWT Decoder

  1. Paste or type your JWT into the input area, or open a file from your device.
  2. Adjust the options above the editor if the tool offers any.
  3. Review the JSON result, then copy it or download it as a file.

Privacy and limitations

  • Your data is processed on your device and is not uploaded to any server.
  • Encrypted tokens (JWE, five parts) cannot be decoded without the key.

Frequently asked questions

Is it safe to paste a token here?

Decoding happens entirely in your browser and nothing is uploaded. Still, treat live tokens like passwords and prefer expired or test tokens.

Why is the signature not verified?

Verification needs the secret or public key. Anyone can read a JWT payload; only the signature proves who issued it, so always verify on your server.

Browse all parsers & testers →