Inspect copied bearer tokens from API requests, logs, or auth middleware.
JWT encoder / decoder
Decode JWT headers and payloads, inspect common claims, and create signed or unsigned tokens with custom header, payload, and secret input.
About this tool
Use this JWT encoder and decoder to inspect token headers and payloads, review claims, and generate signed or unsigned JWTs in the browser.
Decode header and payload claims without sending the token to a server.
Review issued-at and expiry claims when debugging session problems.
Works instantly
Paste your input and get the result immediately — no page reload, no waiting, no configuration needed to get started.
Your data stays private
All JWT Encode/Decode processing runs locally in your browser. Nothing you paste is sent to a server or stored anywhere.
Focused workspace
A dedicated page for JWT Encode/Decode means a clean, distraction-free workspace you can bookmark and come back to anytime.
These answers explain common jwt encode/decode tasks, expected input formats, and edge cases so both visitors and search engines can understand what this tool does.
Does this JWT inspector verify the token signature?
No. This tool decodes the token header and payload for inspection. It does not validate the signature or confirm that the token was issued by a trusted source.
Can this tool create a signed JWT?
Yes. The encoder can generate JWTs using HMAC algorithms such as HS256, HS384, and HS512 when you provide a secret. It can also create unsigned tokens when the header alg is set to none.
What parts of a JWT does this tool show?
It shows the decoded header and payload, plus common summary fields such as algorithm, issuer, subject, audience, and time-based claims when they are present.
Can I inspect expired JWTs?
Yes. Even an expired token can still be decoded and inspected. The decoded payload helps you review the exp, iat, and nbf claims when debugging auth issues.
Should I paste production secrets into a JWT tool?
Only if you trust the tool and your environment. This app runs in the browser, but sensitive tokens should still be handled carefully and only when necessary.