A practical guide to JWTs
What is a JWT?
A JSON Web Token, or JWT, is a compact way to carry claims between parties. A common signed token contains three dot-separated Base64URL segments: a header, a payload and a signature. The header usually identifies the signing algorithm, while the payload contains JSON claims such as an issuer, subject, audience or expiration. The signature allows a receiving application to check integrity and authenticity when it has the appropriate key and verification rules.
The header and payload are encoded, not encrypted. Anyone who has the token can generally read them. Never put passwords or private information in a JWT merely because it appears encoded. This decoder displays the first two segments as JSON objects in your browser. It does not decrypt encrypted tokens, validate claims, or verify signatures; the displayed data must be treated as untrusted.
Common developer uses
Developers inspect JWTs while troubleshooting authentication, identity-provider integrations, API authorization and session expiration. Reading a payload can help compare the expected audience or issuer with the values actually issued. It can also reveal whether a client is using an old token or whether a service is receiving a claim with an unexpected name.
Paste a three-part token into the input to see its header and payload. If an exp claim is present, this page interprets it as seconds since the Unix epoch and displays the corresponding UTC time and an expired or future status. The status uses your device's clock. Absence of an expiration claim, or a future timestamp, does not establish that a token is valid or authorized.
Troubleshooting common errors
If decoding fails, check that you copied the complete compact token without a Bearer prefix, quotation marks or extra spaces inside it. The header and payload must be valid Base64URL-encoded UTF-8 JSON objects. A token with five segments may be an encrypted JWT rather than the signed three-part form supported here. Malformed JSON, invalid UTF-8 and truncated segments cannot be reliably decoded.
Unexpected expiration often comes from confusing seconds with milliseconds, an incorrect system clock, or a short token lifetime. Compare the UTC time with the issuing server's clock and refresh the token according to your application's flow. The decoder flags a nonnumeric or out-of-range exp rather than guessing its meaning.
Security and privacy
Inspecting a token is not a security check. Your application must verify the signature with a trusted key, restrict accepted algorithms, and validate the claims required by its protocol, including issuer, audience and time constraints. Never authorize access based only on decoded output. Processing here stays in your browser, but tokens remain sensitive credentials: avoid untrusted devices, extensions, screenshots and shared clipboards.