JWT Decoder
JWT Decoder lets developers and API testers read a token's header and payload as formatted JSON in the browser. Use it to inspect claims, not to verify signatures or prove that a token is valid.
Decoding happens on your device. Still, avoid pasting live tokens from production into any website.
Paste a token to decode it.
–
–
This tool reads tokens; it does not check the signature. Only your server, with the secret or public key, can say a token is genuine.
What is the JWT Decoder?
JWT Decoder is a free tool that turns a JSON Web Token's encoded header and payload into readable JSON. It decodes the Base64URL segments locally in your browser, so the token is not uploaded for processing. Developers, API integrators and testers use it to inspect authentication data such as the issuer, audience, subject and expiration claim. A common signed JWT has three dot-separated parts: header, payload and signature. Reading the first two parts does not check the third. Use this tool for inspection, then use your application's JWT library for signature verification and claim validation. There are no subscriptions.
Who it is for: JWT Decoder is for software developers, API integrators, QA engineers, security analysts and students learning authentication.
How to use the JWT Decoder
- Tap Try with sample data to inspect a public example before using your own token.
- Paste a three-part JWT into the input, leaving out the Bearer prefix and any surrounding quotes.
- Read the decoded header and payload, checking the claim names and values you need.
- Use your application's JWT library if you need to verify the signature or decide whether to accept the token.
Why use it
- Readable token contentsInspect the decoded header and payload as formatted JSON instead of an encoded string.
- Local processingYour token is decoded in your browser rather than uploaded to a processing server.
- Inspect authentication claimsFind claims such as iss, aud and exp when they are present in the payload.
- No secret needed to decodeRead an unencrypted JWT's header and payload without supplying a signing key.
At a glance
- What you put in
- Three-part compact JWT with Base64URL-encoded JSON header and payload
- What you get
- Decoded header and payload as formatted JSON
- Limits
- Decoding only; no signature verification or encrypted JWE decryption
- Privacy
- Runs in your browser. Nothing you enter is uploaded or stored.
- Price
- Free for everyone. No subscriptions, no payments, no watermark.
- Works offline
- Yes, once the page has loaded
- Last checked
- by AK Shine
Worked example
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
{
"header": {
"alg": "HS256",
"typ": "JWT"
},
"payload": {
"sub": "1234567890",
"name": "John Doe",
"iat": 1516239022
}
}This public sample has an issued-at time of 2018-01-18 01:30:22 UTC and no exp claim; decoding it does not verify its signature.
When to use something else
- For production authentication, use a JWT library with the correct verification key, an explicit algorithm allowlist and the required issuer, audience and time checks.
- For encrypted five-part JWE tokens, use a compatible decryption tool with the required key; this decoder cannot reveal the encrypted payload.
- Prefer test tokens with dummy data, and follow your organisation's rules before pasting production credentials into any browser tool.
Questions people ask
Can I decode a JWT without a secret?
Yes, for a common unencrypted signed JWT, the header and payload are Base64URL-encoded rather than encrypted. You need the appropriate key to verify its signature, not to read those two parts.
Does decoding a JWT verify its signature?
No. A readable payload can still belong to a forged, expired or otherwise unacceptable token. Verification requires a trusted key, an allowed algorithm and checks against your application's claim requirements.
How do I check when a JWT expires?
Look for exp in the decoded payload and convert its Unix timestamp from seconds to a UTC date. At or after that time, the token must not be accepted, subject to any configured clock-skew allowance. Expiration alone does not establish validity.
What do exp, iat and nbf mean?
exp is the expiration time, iat is the issued-at time, and nbf is the time before which a token must not be accepted. These NumericDate values use seconds since 1970-01-01 00:00:00 UTC, not milliseconds. A token need not contain every claim.
Why does my JWT look malformed?
Check for a copied Bearer prefix, surrounding quotes, whitespace or a truncated token. A common signed compact JWT has three dot-separated parts with JSON in its decoded header and payload. Five parts usually indicate an encrypted JWE, which this tool does not decrypt.
Is it safe to paste an access token here?
Decoding runs in your browser without uploading the token for processing. Access tokens can still grant account access, so prefer dummy tokens and follow your security policy. Browser extensions, shared devices and clipboard history remain separate risks.
Is a JWT encrypted, or can someone read it?
A typical signed JWT is encoded, not encrypted, so anyone holding it can read its header and payload. Its signature can protect integrity when properly verified, but it does not hide the claims. Encrypted JWTs use a different structure called JWE.
Can I use JWT Decoder offline?
Yes, after the tool has been opened and made available offline, decoding can run without an internet connection. It does not fetch issuer keys or check server-side revocation.