Handy Devtools
Back to tools

JWT Decoder

Decode and inspect JWT claims without verifying signatures.

Processed locally in your browser
Signature not verified
Decoded content may be forged. Do not use this output to establish identity or authenticity.

229 bytes · limit 1 MiB · never stored

Header

{
  "alg": "HS256",
  "typ": "JWT"
}

Payload

{
  "iss": "devtools.local",
  "sub": "sample-user",
  "aud": "developers",
  "iat": 1704067200,
  "exp": 4102444800,
  "jti": "sample-only"
}

Registered claims

iss · Issuerdevtools.local
sub · Subjectsample-user
aud · Audiencedevelopers
exp · Expiration time41024448002100-01-01T00:00:00.000Z UTC · 1/1/2100, 12:00:00 AMNot expired
iat · Issued at17040672002024-01-01T00:00:00.000Z UTC · 1/1/2024, 12:00:00 AM
jti · JWT IDsample-only

About this tool

Decode the header and payload of compact three-segment JWS tokens. Encrypted five-segment JWE tokens are rejected.

How to use it

  1. Paste a non-sensitive token.
  2. Inspect the decoded header, payload, and registered claims.

Registered claims and time

  • exp, nbf, and iat are NumericDate values measured in seconds since the Unix epoch. Status is compared with this browser’s clock.
  • iss, sub, aud, and jti describe issuer, subject, audience, and token identity, but their presence is not proof they are trustworthy.

Safe token handling

  • Production JWTs can contain credentials or personal data, so prefer synthetic tokens and avoid sharing real tokens. Decoding is performed locally and input is not saved.

Frequently asked questions

Is decoding the same as verification?

No. Anyone can construct a JWT payload. Verification checks the signature and expected issuer, audience, algorithm, and time constraints using trusted configuration.

What is the difference between JWS and JWE?

Compact JWS has three segments and signs content; compact JWE has five segments and encrypts content. This tool only decodes three-segment tokens.

Related developer tools