Read the claims.
Keep the context.
Inspect a compact token’s header and payload locally. Decoding does not validate a signature or claims.
JWT inspector
01 / INPUT TO OUTPUTA clearer view starts here.
Your result will appear here.
Same device. A little less friction.
Less context switching.
More getting it done.
One focused workbench. Six useful tools.
Your data stays in session memory until you clear it.
Bring your input
Paste test data or open a local UTF-8 file.
Make it make sense
Choose the rules. Run the tool. Inspect the result.
Take your work with you
Copy or download only when you’re ready.
At this desk: JWT inspector
Accepts three-part compact JWTs with Base64url JSON objects. Header and payload are decoded with original number tokens preserved. Five-part encrypted tokens are unsupported.
All output is UNVERIFIED. No signature, key, algorithm, issuer, audience, or time-claim validation occurs. Never authorize access from these decoded claims.
Avoid pasting live credentials. No automatic persistence; Clear session removes application references, input fields, results, and running jobs. Downloaded files remain yours to remove.
Clear session removes application references, not downloaded files or browser/OS memory. Ordinary application asset requests still reach the host. There is no analytics, content persistence, or processing service.