JWT Tool

Generate signed JSON Web Tokens, decode their contents and verify signature and claims.

Mode
Header & claims
Secret
Token
Header
Payload

About JSON Web Tokens

A JWT is three Base64URL segments joined by dots: a header naming the algorithm, a payload holding the claims, and a signature computed over the first two parts. Anyone can read the header and payload; only the signature proves who created the token.

  • iat (issued at), exp (expiration) and nbf (not before) are Unix timestamps in seconds.
  • This tool signs and verifies with HMAC (HS256, HS384, HS512) through the browser's Web Crypto API. Signature comparison is done by crypto.subtle.verify.
  • Tokens using alg: none are always reported as invalid. RSA/ECDSA tokens can be decoded but not verified here.
  • RFC 7518 asks for an HMAC secret at least as long as the hash output (32 bytes for HS256, 48 for HS384, 64 for HS512).

Privacy

Tokens and secrets are processed only in your browser. Nothing is sent, stored or logged. Even so, avoid pasting production secrets into any web page you do not control.