About this tool
This tool decodes a JSON Web Token in your browser, showing its header, payload claims and time-based fields such as expiry. Developers use it when debugging sign-in flows, API authorization errors or token lifetimes. A JWT is a compact string of three Base64url-encoded parts, header, payload and signature, separated by dots; the first two are readable JSON that anyone holding the token can decode.
How it works
Paste a compact JWT to decode its Base64url header and payload locally. An optional Bearer prefix is removed, so you can paste a whole Authorization header value. Copy either JSON section, or reset to clear the input.
Time claims exp, nbf and iat are shown in UTC and your local time. The expiry status updates every second using your device clock, so you can watch a short-lived token approach its expiry while testing. If your device clock is wrong, the status is wrong too, even though the decoded claim is correct.
Example
The built-in example is an unsigned token. Its header decodes to {"alg":"none","typ":"JWT"}, and its signature segment is empty, so the token ends with a dot and carries nothing to verify.
The payload has sub set to demo, iat set to 1703980800 (31 December 2023 at 00:00 UTC) and exp set to 1893456000, meaning 1 January 2030 at 00:00 UTC. The token counts as expired from that instant onward. It is only demonstration data, not an authentication credential.
Assumptions and limits
This tool decodes only; it never verifies signatures, issuer, audience or permissions, and it cannot decrypt JWE tokens. Tokens must have three parts with JSON object header and payload, up to 100,000 characters. Time claims are read as Unix seconds against your device clock, with no clock-skew allowance. Nested tokens are not decoded.
Frequently asked questions
Does decoding verify a JWT signature?
No. Anyone can construct readable claims, including a future expiry. Verification requires an appropriate trusted key, an allowed algorithm, and checks of issuer, audience and application policy. This decoder performs none of those checks.
Which tokens and expiry values are supported?
Three-part compact tokens with JSON objects are supported, including unsigned examples with an empty final segment. Encrypted five-part JWE and nested JWT payloads are unsupported. Time claims must be numbers in Unix seconds, not milliseconds or numeric strings. Missing exp means expiry is unknown, not unlimited validity.
Is it safe to paste a JWT into an online decoder?
A live token can grant access until it expires, so treat it like a password. This decoder runs locally and does not upload, save or put the token in the URL, but avoid pasting production tokens on shared devices.
Are JWTs encrypted?
Usually not. A standard signed JWT (JWS) is only encoded, so its payload is readable by anyone, and the signature only detects tampering. Do not put secrets in a JWT payload unless you use encryption (JWE).
What do exp, iat and nbf mean?
They are registered claims from RFC 7519: exp is the expiration time, iat is when the token was issued, and nbf is the time before which it must not be accepted. Each is a NumericDate, the number of seconds since 1 January 1970 UTC.
Link with your values
Add these parameters to this page’s address to open it with the values filled in, for example to share a calculation or to link to it from an AI assistant. The result is calculated in the browser: the page HTML shows an example for the default values, and the tool sets the data-url-params attribute once the link’s values are applied.
| Parameter | Value | If omitted |
|---|---|---|
tokenJWT token | not accepted in links: enter it on the page |
Links cannot carry this tool’s input, so there are no examples: enter it on the page.
Write decimals with a point. Encode a space as %20, + as %2B, # as %23 and & as %26.
Result elements: [data-result-block="jwt"]