EN
My tools

JWT Decoder

Decode a JSON Web Token in your browser: read the header and payload as JSON, see iat/nbf/exp as dates, and optionally verify the HMAC or RSA/ECDSA signature.

Leave blank to decode without verifying.
Header
Payload
Algorithm
HS256
Signature
Not verified — paste the secret or public key to check it
Time claims (checked against now, UTC)
ClaimUnixUTCStatus
Issued at1,516,239,0222018-01-18T01:30:22.000Z
My tools →
Advertisement

A JSON Web Token (JWT) packs a header, a payload of claims and a signature into three Base64URL parts joined by dots. This decoder shows the header and payload as readable JSON, turns the time claims into dates, and can verify the signature if you paste the secret or public key. The token never leaves your browser.

How to use this tool

  1. Paste the token.
  2. Read the pretty-printed header and payload.
  3. Check the iat, nbf and exp claims against the current time.
  4. Optionally paste the HMAC secret or a PEM/JWK public key to verify the signature.

Formula

The signature is computed over "header.payload" (the first two Base64URL segments). HS256 uses HMAC-SHA-256 with a shared secret; RS/PS/ES use RSA or ECDSA with a public key.

Decoding is not the same as trusting: anyone can read a JWT. Only a valid signature proves it was issued by the holder of the key.

Example

The classic sample token decodes to a payload of { "sub": "1234567890", "name": "John Doe", "iat": 1516239022 }, and with the secret "your-256-bit-secret" its HS256 signature verifies as Valid.

Frequently asked questions

Is my token uploaded?

No. Decoding and signature checking both run in your browser using the Web Crypto API, so the token and secret stay on your device.

Why does alg "none" get a warning?

A token with alg "none" has no signature, so anyone can change its claims. Libraries should reject it; the warning is a reminder.

Which signatures can it verify?

HMAC (HS256/384/512) with the shared secret, and RSA, RSA-PSS and ECDSA (RS/PS/ES 256/384/512) with the issuer’s public key as an SPKI PEM or a JWK. Never paste a private key into a website — verification only needs the public key. A token that claims HS256 is refused when you give it a public key, because accepting that is a well-known forgery trick.

Sources

Last updated:

Cite or embed this tool
APA

kakaoCalc. (2026, November 8). JWT Decoder. https://kakao.mobile/tools/jwt-decoder/

MLA

“JWT Decoder.” kakaoCalc, 8 Nov. 2026, kakao.mobile/tools/jwt-decoder/.

Paste this code into your page. The widget runs in your visitors' browsers, shows no ads and keeps a link back to this page. Embedding terms

Advertisement