key

JWT Decoder

DEV

Decode JWT header and payload claims, check expiry and verify HS256 signatures.

shield_lock Private & on-device
Live workspace
Preparing…
lock Your files and text are processed in this browser and never uploaded.
In-depth guide

About JWT Decoder

JWT Decoder: Inspect a JSON Web Token Safely

A JSON Web Token is three Base64URL-encoded parts separated by dots: a header, a payload and a signature. Paste a token to decode the header and payload as readable JSON, inspect registered claims such as exp, iat, nbf, iss, aud, sub and jti, and see when the token expires relative to now.

Decoding is not verification. A readable token can still be forged or altered. For HMAC-signed tokens, enter the shared secret and choose HS256, HS384 or HS512 to verify the signature with the browser’s Web Crypto API. RS256 and ES256 tokens can be decoded here but require a public key or JWKS endpoint for proper verification.

Privacy and Security

Everything happens in this browser tab; the token and secret are never sent to a server. Avoid pasting production tokens into any page you do not trust, and never treat decoded claims as trusted identity until the signature, issuer, audience and expiry have all been validated by your application.

Answers

Frequently asked questions

Does decoding a JWT prove it is valid?

No. Decoding only converts Base64URL text into JSON. A token could be expired, forged or signed with a different key and still decode perfectly. You must verify the signature and validate the issuer, audience, expiry and not-before claims before trusting it.

Is it safe to paste a JWT into this tool?

The token is decoded locally with JavaScript and is not uploaded. That said, JWTs can contain sensitive claims, so use a test token when possible and avoid pasting long-lived production credentials into any browser tool.

Why can I not verify RS256 or ES256 tokens here?

Asymmetric verification needs the issuer’s public key or a JWKS document plus algorithm-specific handling. This tool focuses on HMAC verification, which only needs a shared secret. Use your identity provider or a JWKS-aware verifier for RS256 and ES256.

What do exp, iat and nbf mean?

exp is the expiry time, iat is when the token was issued and nbf is the earliest time it may be accepted. All three are Unix timestamps in seconds. The claims table converts them to local dates and shows whether they are in the past or future.

Quick tips

  • Use the copy button to move formatted output straight into your editor.
  • Validation errors point to the exact position in your input.
  • All formatting and checks happen locally - nothing is uploaded.