Does decoding a JWT verify it?

No. Decoding only reads the base64url header and payload. Signature verification must happen with the issuer’s key in your application.

Is my token sent anywhere?

No. Decoding runs in the browser and the token stays on your device.

Can it decode a Bearer token?

Yes. The decoder accepts a token with an optional Bearer prefix.

JWT decoder for header, payload and claims

How to use this tool

Paste a JWT or include a Bearer prefix.
Review the decoded header and payload.
Check exp, iat and nbf values, then verify the signature in your own application.

Worked example

Tool Kumar decodes this unsigned example token into header, payload, signature and claims.

Input · example.jwt

eyJhbGciOiJub25lIiwidHlwIjoiSldUIn0.eyJzdWIiOiIxMjMiLCJuYW1lIjoiQWRhIiwiaWF0IjoxNTE2MjM5MDIyfQ.

Output

{
  "header": {
    "alg": "none",
    "typ": "JWT"
  },
  "payload": {
    "sub": "123",
    "name": "Ada",
    "iat": 1516239022
  },
  "signature": "",
  "claims": {
    "iat": "2018-01-18T01:30:22.000Z"
  }
}

Options and edge cases

The decoder accepts JWS compact tokens with three parts.
It does not verify the signature or fetch a key.
Numeric date claims are shown as readable ISO times in the decoded view.

Private by default

Your document stays in this browser. Tool Kumar parses, converts and creates downloads on your device, with no account or upload step.

JWT decoder questions

Does decoding a JWT verify it?: No. Decoding only reads the base64url header and payload. Signature verification must happen with the issuer’s key in your application.
Is my token sent anywhere?: No. Decoding runs in the browser and the token stays on your device.
Can it decode a Bearer token?: Yes. The decoder accepts a token with an optional Bearer prefix.