Paste a JSON Web Token and this decodes its header and payload locally, so the token never touches a server. It pretty-prints the JSON, summarizes the registered claims, and shows issued-at, not-before and expiry in UTC, local and relative time. Decoding isn't verification, though — it won't check the signature or prove the token is valid.
JWT Decoder runs locally using your browser's built-in cryptography, so passwords, keys and hashes are never uploaded or logged.
No. Verification requires the signing key. This tool only decodes the header and payload so you can read them.
No. Decoding happens locally in your browser and the token is never uploaded or stored.
Be careful. JWTs can contain sensitive data — only paste tokens into tools you trust, and prefer non-production tokens.
JWTs may contain sensitive information.
OomTools decodes tokens locally in your browser. Do not paste production tokens into tools you do not trust. Decoding a JWT does not verify its signature or prove the token is valid.