🔒  100% client-side · Your data never leaves this browser · No uploads, no tracking

💡 Why this exists

Debugging auth failures means inspecting JWTs — but pasting tokens from production into an online decoder leaks real credentials to a third-party server. CapabilityBase decodes in your browser, with zero network calls: check exp, iat, iss and claims without ever uploading the token.

Capability Info

IDjwt.decode
Version1.0.0
Statusstable
CategorySecurity / Auth
Contractdeterministic, no side effects, local, no AI
RuntimeBrowser, Node, Edge, Worker
Consumesjwt
Producesjson

What JWT Decode Reveals

✅ Header

alg (HS256 / RS256), typ, kid — identifies signing algorithm

✅ Claims

exp, iat, nbf, iss, sub, aud, jti extracted and explained

✅ Expiry

Remaining validity computed live — expired tokens flagged in red

✅ Signature

Length and raw payload shown (verification requires the signing key)

⚠️ Signature verification needs the secret/public key and is intentionally not performed — decoding alone never validates authenticity.

AI is probabilistic. Your tools shouldn't be.

Frequently Asked Questions

Is my JWT sent to a server?

No. Decoding happens 100% in your browser with zero network calls — safe to inspect production tokens that must never be uploaded.

Does it verify the signature?

No — signature verification requires the secret or public key, which the tool intentionally never asks for. It decodes header/payload and computes expiry, but cannot confirm authenticity.

What claims does it extract?

exp (expiry with live remaining time), iat, nbf, iss, sub, aud and jti are parsed and displayed alongside the full header and payload JSON.

Can AI agents call it via URL?

Yes — pass ?input=<token> or ?jwt=<token> and the page decodes automatically, making it usable as a deterministic tool by scripts and agents.

Tools we recommend

Deploy this tool on Vercel · Ship faster with Cursor · Your static site on Cloudflare

Copied to clipboard!