← Home

JWT Debugger

Contact us
✓ Valid JWTHS256● Active — expires in 483840h 0m 0s
Json Web Token
Decoded
HEADER
{
"alg":"HS256"
"typ":"JWT"
}
PAYLOAD
{
"sub":"u_9f3a2b1c"
"iss":"auth.example.com"
"aud":"api.example.com"
"name":"Jane Smith"
"email":"jane@example.com"
"roles":[
"editor"
"viewer"
]
"iat":1741737600
"exp":1741824000
}
Verify Signature
Secret KeyEnter the HMAC secret to verify
Verification Function
( base64UrlEncode(header) + "." + base64UrlEncode(payload), "your-256-bit-secret" ) === YzUvWb8eLkp_W-6DtHoltJX086n-zqo7fiKb7RhIRt8

What is a JWT?

A JSON Web Token (JWT) is a compact, URL-safe token defined by RFC 7519. It encodes claims as a JSON object that is digitally signed, making it tamper-evident. JWTs are widely used for authentication and information exchange.

  • Header — token type (JWT) and signing algorithm
  • Payload — claims (user data, expiry, issuer, etc.)
  • Signature — ensures the token hasn't been tampered with

Standard Claims

  • iss — Issuer: who created the token
  • sub — Subject: who the token is about
  • aud — Audience: intended recipients
  • exp — Expiration Time: Unix timestamp after which the token is invalid
  • nbf — Not Before: Unix timestamp before which the token is not valid
  • iat — Issued At: when the token was created
  • jti — JWT ID: unique identifier for the token

Signing Algorithms

  • HS256 / HS384 / HS512 — HMAC + SHA. Symmetric: same secret signs and verifies. Simple but secret must be shared.
  • RS256 / RS384 / RS512 — RSA + SHA. Asymmetric: private key signs, public key verifies.
  • ES256 / ES384 / ES512 — ECDSA. Asymmetric with smaller signatures than RSA.
  • PS256 / PS384 / PS512 — RSA-PSS. Randomized RSA variant with stronger security properties.