Webhook HMAC Signer
Sign and verify GitHub, Stripe, and Slack webhook signatures locally.
OpenPaste a token and read its claims as formatted JSON, with the dates already converted.
Paste the full header.payload.signature string.
Header and payload appear as formatted JSON.
iat, nbf and exp are shown in local time.
Empty the field before you step away.
A support ticket says "token expired", but the time on the claim does not match what you expect. JWT Decoder splits the token into readable header and payload JSON and turns iat, nbf and exp into local timestamps so you can see what the client actually holds.
The decoder splits the token at its dots, Base64URL-decodes the first two segments and prints the header and payload as indented JSON in two panels. If the payload contains iat, nbf or exp, a summary underneath converts them from Unix seconds to your local date and time and labels exp as expired or valid by comparing it with your computer's clock. It also reports the length of the signature segment. Decoding happens as you type, and Clear empties the field.
Decoding is not verification. Anyone can create a token with any claims, so never let decoded values make a security decision on their own. Check HS256 signatures with JWT signature verification, and run a security review of the header and claims when you are assessing how tokens are issued. When exp and the user's experience disagree, clock skew or a time zone mix-up is a common cause, and the expiration checker prints the same claims in UTC with a seconds countdown.
The token is decoded in this tab with the browser's built-in Base64 functions; the guide to decoding JWTs safely explains why that matters for production tokens.
Keyboard shortcut
See claims and expiry without guessing from opaque strings.
Confirm exp/iat against local time when users report lockouts.
Inspect header alg, then move to JWT Verify for HS256.
Answers for this tool. For site-wide help, open the FAQ hub.
The payload is decoded with the browser's atob function, which returns raw bytes rather than UTF-8 text. ASCII claims display correctly, but accented or non-Latin names can look scrambled even though the token is fine. JWT Claims Viewer decodes UTF-8 properly.
It only means the expiry time is still in the future on your clock. The signature, issuer and audience are not checked by this page.
No. A JWE has five segments and an encrypted payload, so there is no readable JSON to show without the decryption key. Only signed tokens decode here.