Compare two JWTs claim by claim to see what differs between environments or before and after a change — decoded only, with signatures never verified.
Waiting for two tokens
Both are decoded. Neither is verified.
Waiting for two tokens
Paste the token that works and the one that does not.
JWT Claim Comparison runs entirely on your device — no token is ever uploaded, logged or stored, and nothing here verifies a signature.
You’re on the Free plan. Compare plans
The question this answers is "why does this token work in staging and not in production", and the answer is almost always one claim — a different `aud`, a missing scope, an `iss` that does not match what the verifier expects.
Claims are compared by name, with the ones that differ brought to the top. Standard claims carry their meaning alongside, because `aud` and `iss` are the two that cause the most confusion and the most rejected requests: `aud` is who the token is for, and a verifier that checks it will reject a token minted for a different service even though everything else about it is correct.
Timestamps are shown as dates rather than as the raw epoch seconds, and read against the current clock. `nbf` in the future is usually clock skew between the issuer and the verifier, which is a different problem from an expired token and needs a different fix.
Neither token is verified. Both are decoded, and a token that differs in its signature while matching in every claim will look identical here — which is correct, because the signature is not a claim.
Nothing is uploaded, logged or stored. Both tokens live in the page and are gone when the tab closes.
No. Both tokens are decoded, not verified. Two tokens with identical claims and different signatures look the same here, because the signature is not a claim and checking it needs the key.
Names who the token is for. A verifier that checks `aud` rejects a token minted for another service even when it is otherwise perfectly valid — a common cause of a token that works in one place and not another.
Usually clock skew between the issuer and the verifier. It is a different failure from expiry and needs a different fix — syncing clocks, or a small leeway in the verifier rather than a longer token lifetime.
`iat` is when the token was issued, so two tokens minted at different moments differ there and nowhere else. That difference is expected and is not the reason one of them is rejected.
No. They are decoded in your browser, never logged, and never written to browser storage.