What a JWT decoder shows
A JSON Web Token (JWT) is a compact string commonly used to carry claims between systems. A signed JWT generally has three dot-separated sections: a Base64URL-encoded header, a Base64URL-encoded payload, and a signature. The header usually identifies metadata such as the signing algorithm and token type. The payload contains claims, which may describe a subject, issuer, audience, permissions, or timestamps. The signature is a separate cryptographic value used by a receiving system to detect tampering.
This inspector decodes the first two sections as UTF-8 JSON and displays the third section exactly as encoded. It also recognizes the standard exp (expiration), iat (issued at), and nbf (not before) claims when they are numeric Unix timestamps in seconds. These dates can make it easier to inspect test tokens, troubleshoot application flows, or understand which claims a service included.
How to use the inspector
Paste a compact token into the input and select Decode token, or focus the input and use the button with your keyboard. A valid input must have three dot-separated sections; the header and payload must be valid Base64URL-encoded JSON objects. The page shows each JSON object in an indented form, displays recognized timestamps as local dates, and reports whether an expiration time has passed or how long remains. If the not-before claim is still in the future, the page calls that out. Copy buttons copy the formatted header, formatted payload, or original encoded signature independently.
Empty input, malformed sections, invalid UTF-8, invalid JSON, and inputs over the size limit produce a clear error instead of partial results. The Clear button removes the token and its decoded output. The tool performs these operations in your browser without sending the token to an API or storing it.
Security limits and common uses
Decoding is not verification. Anyone can create a string with readable header and payload sections, and changing a signed token’s contents invalidates its signature. This page does not verify signatures, check keys, validate issuer or audience, enforce application rules, or prove that claims are true. Never grant access based only on what a decoded token says. The service that consumes a token must verify its signature and validate the claims it relies on. JWT payloads are encoded, not encrypted, so do not put secrets in them unless a separate encryption layer is used.
Developers commonly use a decoder to inspect a development token, check a timestamp claim, or troubleshoot claim serialization. Avoid pasting production credentials into shared or public devices, and do not share screenshots containing sensitive claims. For related browser utilities, see the Base64 Encoder & Decoder, Hash Generator, or JSON Formatter.
Frequently asked questions
Does decoding a JWT verify that it is authentic?
No. This tool only decodes the token’s Base64URL sections. It does not verify a signature, issuer, audience, or any other trust condition.
Is my token sent to a server?
No. Token parsing and date conversion happen locally in your browser. The tool does not make API calls or store the token.
Why can a decoded token still be invalid?
A readable header and payload only show that the token sections contain valid encoded JSON. A server may still reject an invalid signature, expired token, or claims that do not match its policy.
Which JWT timestamps are displayed?
The inspector recognizes exp (expiration), iat (issued at), and nbf (not before) when they contain numeric Unix timestamps in seconds.