We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Parse JWT headers, payloads, and key information online. No installation required—just paste and decode.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
A JSON Web Token (JWT) carries a set of claims in a compact, dot-separated string. This parser accepts the three-part form used by signed JWTs: a header, a payload, and a signature segment. It decodes the header and payload into readable JSON and shows the signature text. Base64url is an encoding; readable claims are not secret merely because they came from a token.
The header often includes alg, the algorithm identifier. Payload claims may include iss (issuer), sub (subject), aud (audience), iat (issued at), and exp (expiration). Claims are optional unless an application’s own rules require them, so a missing claim can be normal. The parser also keeps custom claim names in the JSON output.
In the JWT specification, NumericDate is a number of seconds since 1970-01-01 00:00:00 UTC. The summary converts numeric iat and exp values to readable dates; the original payload remains available for comparison. String time values may also be displayed when present, but they are not the standard NumericDate form. An expiration label is only a quick reading of the supplied value against the current clock.
The token format may also be encrypted. A five-part JWE has a different structure and is outside this parser’s three-part input. RFC 7519 describes both JWS and JWE representations and distinguishes signed or integrity-protected content from encrypted content.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Copy the complete compact token, including its periods, and paste it into the input. Avoid adding quotation marks or whitespace inside the token.
Review the summary for the declared algorithm, issuer, issue time, and expiration when those fields are available. A blank summary item can simply mean that the claim was not supplied.
Compare the formatted summary with the complete Header and Payload JSON. Use the copy controls to move a field or JSON block into your debugging notes.
Use cases
See how the tool fits into real work and everyday tasks.
When an application rejects a test token, inspect iss, aud, and application-specific claims, then compare them with the values expected by the receiving service.
Check the raw iat or exp number beside its displayed date. This can reveal a seconds-versus-milliseconds mistake in a test payload.
Q&A
Find concise answers to common questions and confusing cases.
No. This page displays token contents but does not verify a signature, issuer, audience, or authorization policy. Use the verification procedure and trusted keys required by the application.
In a signed JWT, the payload is encoded for transport; signing protects integrity when correctly verified, but does not hide the claims. Do not put confidential data in a readable payload.
Five dot-separated parts are used by compact JWE, which has encrypted content. This parser handles three-part signed tokens and does not decrypt JWE.
Registered claims such as iss and exp are not automatically present in every token. The decoded JSON shows what the token actually contains.
Notes
Review scope, result limitations, and important precautions before use.
Never treat a readable token or an “active” time label as proof that a token is trustworthy. The page does not authenticate the signature or enforce application rules. Avoid pasting live access tokens or identity data into a shared or untrusted device; use a test token with non-sensitive claims whenever possible.
Related
Discover related tools, collections, and available API capabilities.