Skip to main content

JWT Decoder

Read a JWT’s header and payload. Decoding only: it does not verify signatures. Everything runs in your browser, so your input isn’t uploaded.

Loading tool…

How to use the JWT Decoder

  1. Paste a token. A leading “Bearer ” is fine.
  2. Read the header, the payload and the claims such as when it expires.
  3. Remember that this only reads the token: it cannot tell you whether the token is genuine.

Example

A token made up for this example. Its two readable parts decode to JSON. The signature is a placeholder, and this tool never checks it.

Token
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkphbmUgRG9lIiwiaWF0IjoxNzAwMDAwMDAwLCJleHAiOjE3MDAwMDM2MDB9.c2lnbmF0dXJlLW5vdC12ZXJpZmllZA
Header, then payload
{
  "alg": "HS256",
  "typ": "JWT"
}

{
  "sub": "1234567890",
  "name": "Jane Doe",
  "iat": 1700000000,
  "exp": 1700003600
}

About this tool

A JSON Web Token has three parts separated by dots: a header, a payload of claims, and a signature. The first two are just encoded text, so anyone can read them. This tool decodes them and explains the time-based claims.

Good to know

  • This tool does not verify the signature. A token that decodes correctly can still be forged or tampered with. Only a server holding the right key can verify it.
  • Never trust the contents of a token you haven’t verified when making security decisions.
  • Nothing is sent anywhere, but treat live tokens like passwords: prefer expired or test tokens when you can.

Related tools

Browse all tools