Frequently asked questions
Is my token uploaded anywhere?
No. The JWT is decoded entirely in your browser and is never sent to a server, so even sensitive tokens stay on your device. It works offline once loaded.
Does it verify the signature?
No. It decodes and shows the header and payload, but it does not check the signature, so a token that decodes is not proven to be authentic. Treat decoding as inspection only.
What do exp, iat and nbf mean?
They are standard time claims: exp is when the token expires, iat is when it was issued, and nbf is the earliest time it is valid. They are shown as readable dates with an expiry status.
Is it safe to paste a real token here?
Because everything stays in your browser, the token is not transmitted. Still, treat live tokens with care and avoid pasting them on shared or untrusted devices.
Why does my token fail to decode?
A JWT has parts separated by dots, encoded with base64url. If the token is truncated or altered, the parts cannot be decoded and a clear message is shown.