JWT Decoder

Decode JSON Web Tokens and verify HS256 or RS256 signatures, in your browser.

Encoding and decoding Runs in your browser: nothing you enter is sent to a server.

    Header

    –

    Payload

    –
    Verify the signature

    About the JWT Decoder

    A JSON Web Token (JWT) has three Base64URL-encoded parts: a header (algorithm and type), a payload (claims such as subject, issuer and expiry) and a signature.

    The decoder shows header and payload, translates time claims into readable dates, and warns about risky settings such as alg "none" or missing expiry. You can verify HMAC (HS256/384/512) and RSA (RS256/384/512) signatures with your secret or public key; everything happens in your browser.

    How to use it

    1. Paste the token.
    2. Read the decoded header, payload and the warnings.
    3. Optionally enter the secret or public key to verify the signature.

    Frequently asked questions

    Is a JWT encrypted?

    Usually not. A signed JWT (JWS) is only encoded: anyone can read its payload. Never put secrets or personal data into it unless you use an encrypted token (JWE).

    Is it safe to paste a token here?

    The decoder runs entirely in your browser and sends nothing to a server. Still, treat valid production tokens like passwords: prefer expired or test tokens.

    What is the "alg: none" attack?

    Some libraries accepted tokens with alg set to "none" and no signature as valid. Servers must enforce the expected algorithm and never trust the alg value from the token itself.

    All free tools