Security

JWT Decoder

Paste a JWT to read its header and payload and see when it was issued and when it expires. The token never leaves your browser.

Guide: Decode a JWT: Read Claims and Verify the Signature

Ready.

Verify signature

Decoding above is not verifying. Provide the matching key and this checks the signature itself, entirely in your browser.

Accepted keys: a shared secret (or an oct JWK) for HS*, a PEM public key, a single JWK, or a whole JWKS ({"keys":[...]}) for RS*, PS*, ES* and EdDSA. With a JWKS the tool picks the key by the token's kid and alg, and tells you why if none fits.

Paste a token above, then a key here, to verify.

    Claim checks rule of thumb

    Optional. Enter what your service expects, or leave the boxes empty to skip that check. These checks read the token's claims only and say nothing about the signature.

    • Paste a token above to check its claims.

    What it does

    A JSON Web Token has three parts separated by dots: a header, a payload of claims, and a signature. The header and payload are just Base64URL-encoded JSON, so they can be read without any key. This tool decodes them and translates the iat, nbf and exp claims into dates.

    Important: decoding is not verifying

    The header and payload above are decoded, not verified: anyone can produce a token with any claims, since that part needs no key. The Verify signature section checks the signature itself for HS256/384/512, RS256/384/512, PS256/384/512, ES256/384/512 and EdDSA (Ed25519) when you provide the matching secret or public key (PEM, JWK or a JWKS). EdDSA needs a browser with Ed25519 in WebCrypto; where it is missing the tool says so and does not polyfill it. For other algorithms, or without a key, treat the decoded content as unverified and never make security decisions from it alone. JWE (encrypted tokens) is not decrypted.

    Claim checks

    The Claim checks list reports, in plain language, an expired exp, a not-yet-valid nbf, an iat in the future, a missing exp, dates written in milliseconds, and an alg of none. If you enter an expected issuer or audience it compares them, and the clock-skew box widens the time checks. The lifetime warning is a rule of thumb: tokens that live longer than the number of days you set are flagged, which is not an error in itself. When an HMAC token is checked against something that looks like a public key, the tool warns about algorithm confusion. The checks use your device clock and cannot tell whether a token has been revoked.

    Tips

    • Tokens with five parts are encrypted (JWE) and cannot be decoded without the key.
    • Avoid pasting production tokens that are still valid into any online tool. This one works offline in your browser, but treat live credentials with care.

    Example: reading a token and checking its claims

    The built-in example token has the header {"alg":"HS256","typ":"JWT"} and these claims: issuer https://example.com, audience devtoolera-demo, issued at 2023-11-14T22:13:20Z and expiring on 2100-01-01T00:00:00Z. The decoder turns the numeric dates into readable ones and shows the lifetime (exp minus iat), which is 76 years here.

    If you enter the secret example-secret in the Verify signature section, it reports “Signature verified. This token was signed with the key you provided, and the header and payload have not been altered.” The optional claim checks then add a line for each rule. With the issuer set to https://example.com, the audience set to a different value and a 30-day lifetime limit, the result is:

    • OK: not expired, and issued in the past.
    • OK: issuer matches.
    • Warning: very long lifetime, 76 years, over the 30-day threshold. Long-lived tokens are risky if stolen. This is a rule of thumb, not an error.
    • Problem: audience mismatch, expected “wrong-audience”, token has “devtoolera-demo”.

    Decoding is not verifying

    Anyone can create a token that decodes to any claims, so what you read in the header and payload is only trustworthy after the signature is checked with the right key. A verified signature proves that the token was not changed since it was signed, but it does not hide the contents: the payload is only Base64URL-encoded. To create tokens for testing, use the JWT Generator; to convert timestamps, use the Timestamp Converter.

    Frequently asked questions

    Is it safe to paste a production token here?

    The token is decoded in your browser and is not sent anywhere. Still, a live token can grant access until it expires, so prefer test tokens, and never share a real token in a chat or a ticket.

    Why does my token say “not verified”?

    Decoding needs no key, so the signature is not checked until you provide the secret or the public key in the Verify signature section.

    What does “alg: none” mean?

    It means that the token claims to need no signature. A service must never accept such a token as proof of identity.

    Which algorithms can be verified?

    HS256, HS384, HS512, RS256, RS384, RS512, PS256, PS384, PS512, ES256, ES384, ES512 and EdDSA (Ed25519), with a secret, a PEM public key, a JWK or a JWKS.

    Privacy

    This tool runs entirely in your browser. What you enter is processed on your device and is not sent to a server.

    Share this tool

    Your data is not included in this link.