JWT Decoder & Verifier

Decode JWT headers and claims, then verify a token with your key and claim settings. Inspect results locally; remote JWKS requires an explicit HTTPS request.

Token and keys are processed in this browser and are not saved automatically. Remote JWKS requires explicit HTTPS access.
Keys & Actions

Token Input & Status

Decoding reads the header and payload; it does not verify the signature. Verification uses your selected key and configured claims. This is a debugging tool, not an authorization decision.

Ready

Decoded Details

Not verified

Paste a token to decode

Keys & Actions

Verification & Decryption

Verification

Decryption

Remote JWKS

Utilities

Base64Url

PEM ↔ JWK

JWT Decoder & Verifier

Inspect a JWT while debugging authentication: read header fields such as alg and kid, inspect claims such as sub and exp, then check the signature using a key you select. Decoding reveals data but does not establish that the token is trustworthy. Verification and application authorization are separate decisions.


Use the key and claim options that match your test scenario. Remote JWKS retrieval makes an explicit HTTPS request; ordinary token and key processing happens in the browser and is not saved automatically. Sharing includes the token in the link, so anyone receiving that link can read it. Use test tokens without production secrets for examples and inspect the verification status before interpreting decoded claims.

Features

  • Read JWT header and payload data, with token structure and timeline information.
  • Verify with a selected key and configured claim checks.
  • Inspect verification diagnostics and copy or export decoded data.
  • Use remote JWKS explicitly; shared links include the token itself.

How to use

  1. Paste a test token in the token input. Inspect its decoded header and payload.
  2. Select the verification key source and the claim settings relevant to your test.
  3. Run verification and read the signature status and diagnostics separately from the decoded values.
  4. Copy or export the data you need. Check the token contents before creating a shared link.