Skip to content
HashlLab

JWT Decoder

Inspect JSON Web Token headers and claims, check expiry and verify HMAC signatures.

In browserOpen

About this tool

  • Runs entirely in your browser. Nothing you enter is uploaded.
  • Decoding does not prove authenticity. Verify the signature before trusting any claim.

How it works

The token is split into header, payload and signature, decoded from Base64URL and shown as formatted JSON. Time claims are converted to dates; unsigned tokens (alg “none”) are flagged.

Questions about JWT Decoder

Help center
Can HashlLab verify a JWT signature?

Yes, for HS256, HS384 and HS512, using the shared secret. Tokens signed with public-key algorithms such as RS256 or ES256 are decoded and their claims shown, but the signature is not verified.

Is it safe to paste a production token?

The token is decoded in your browser and not sent anywhere. Still, tokens are credentials: avoid pasting them on shared computers and prefer short-lived tokens when debugging.

Why is a token with alg “none” flagged?

An unsigned token can be forged by anyone. Servers must never accept it, and its presence usually means a misconfiguration or an attack attempt.