JWT Decoder & Verifier

Decode JWT tokens to inspect header and payload claims, check expiry, and verify HS256, RS256, PS256, ES256 and EdDSA signatures with a secret, PEM or JWKS.

Runs 100% in your browser. Nothing you paste is uploaded.

Encoded token

Verify signature

alg

Header

Payload

About the JWT Decoder

Paste any JWT — an OAuth access token, an OpenID Connect ID token, or a token from your own API — to see its decoded header and payload instantly. Standard claims are explained in plain English and timestamps like exp, iat and nbf are converted to readable dates with a clear “expired” or “expires in” indicator.

To verify the signature, enter the shared secret for HMAC tokens, or paste the issuer’s public key as PEM, JWK or a complete JWKS document — the key matching the token’s kid is selected automatically.

Features

  • Instant decoding with colour-coded token parts
  • Human-readable claim names and timestamps
  • Expired / not-yet-valid detection
  • Verify HS256/384/512 with text or Base64 secrets
  • Verify RS*, PS*, ES* and EdDSA with PEM, JWK or JWKS
  • Picks the JWKS key by kid
  • Detects encrypted JWE tokens and unsigned tokens
  • Ignores a leading Bearer prefix

How to use it

  1. Paste the token into the Encoded token box.
  2. Read the decoded header, payload and the claims table.
  3. To verify, enter the secret (HS*) or paste the public key / JWKS (RS*, ES*, PS*).

Frequently asked questions

Is it safe to paste a production JWT here?

Decoding happens in your browser — the token is never sent anywhere. Still, treat live tokens like passwords and prefer expired or test tokens when sharing screens.

Can anyone read the contents of a JWT?

Yes. A signed JWT (JWS) is only Base64URL-encoded, not encrypted. Never put secrets in the payload. Use JWE if the contents must be confidential.

Where do I find the public key to verify a token?

OpenID providers publish their keys at the jwks_uri listed in /.well-known/openid-configuration — e.g. Auth0, Okta, Azure AD/Entra ID, Google and Keycloak. Paste the JWKS JSON here.

Why is my signature invalid?

Common causes: wrong secret, secret is Base64-encoded (switch the encoding), wrong key for the kid, or the token was modified. Also make sure no whitespace or line breaks were introduced when copying.

Esc