Developer tools for API debugging
Nothing leaves your browserPaste a token, a header, a webhook or a URL. The tool tells you what it is and decodes it. Then verify signatures, build headers and generate keys, all in your browser.
Try:
Waiting for input
Paste something on the left
Tokens, headers, webhooks, query strings and Base64url are recognized and decoded right here.
Everything for tokens, signatures and headers
JWT decoderDecode, verify and create JSON Web Tokens→Webhook signature verifierStripe, GitHub, Shopify, Slack, Svix and more, with the reason when it fails→HMAC generatorHMAC-SHA256 and friends, as hex or Base64, with a compare field→Base64urlEncode, decode and convert between Base64, Base64url and hex→Basic auth headerBuild or decode an Authorization: Basic header→PKCE generatorcode_verifier and S256 code_challenge for OAuth→Secret key generatorRandom keys for JWT, webhooks, Laravel, Django→URL encoding: every flavorPHP urlencode, rawurlencode, encodeURIComponent and form encoding side by side→
Built for the way you debug
Token from a requestPaste a whole
Authorization: Bearer … line or a curl command. The token is pulled out, decoded and its expiry shown. Verify it with the secret, a PEM key or the JWKS, picked by kid.Webhook that won’t verifyPaste the headers, the body and the secret. If the signature fails, the tool tries the usual mistakes (newline, re-serialized JSON, whsec_ prefix, hex vs Base64) and tells you which one it is.
From JWT to certificateAn RS256 or ES256 token is signed with a key that often comes from a certificate. Paste the certificate into the verifier, or open it in the certificate decoder to see who issued it.
Why you can paste a production token here
Tokens, webhook secrets and passwords are exactly what you should never paste into a random website. These tools are built so you don’t have to trust us:
- No server. Every tool runs as JavaScript in your browser. There is no backend that could receive your input.
- Verifiable. Each page sends a Content-Security-Policy that only allows connections to encode-decode.com and, if you accepted cookies, Google Analytics. Analytics never sees what you type. Check it in your browser’s developer tools under Network.
- Works offline. Once the page has loaded, switch off your connection and try it.
- Or don’t paste at all. Every tool shows the same steps for your terminal:
openssl dgst -hmac,base64,jq.