Developer tools
Decode JWTs, format JSON, test regex, hash files, and make QR codes.
Are tokens and files uploaded?
No. Decoding, formatting, hashing, and QR generation run in the browser. Closing the page drops the paste.
Does the JWT decoder verify signatures?
No. It reads header and payload only. Anyone can decode a JWT. Treat claims as untrusted. Encrypted JWE is rejected.
About Developer tools
Developer tools decode JWTs, format and validate JSON, test regex, compare two texts, encode Base64 including images, hash files, build color palettes, and generate QR codes.
Everything runs in the browser. Tokens, files, and hashes are not uploaded. No login.
How these tools work
Paste a token, drop a file, or type a pattern. The result stays in the page until you copy or download it. JWT decoding does not verify signatures. Hashes and QR codes are built locally.
Nothing is stored in an account. Closing the page drops what you pasted. These tools do not call a language model.
FAQs
- Are tokens and files uploaded?
- No. Decoding, formatting, hashing, and QR generation run in the browser. Closing the page drops the paste.
- Does the JWT decoder verify signatures?
- No. It reads header and payload only. Anyone can decode a JWT. Treat claims as untrusted. Encrypted JWE is rejected.
- Which hashes can I generate?
- MD5, SHA-1, SHA-256, and SHA-512 from text or files. The file is hashed in the browser.
- What can a QR code encode?
- Text, a URL, Wi-Fi credentials, or a vCard. Download PNG or SVG.
- Is Base64 for text and images the same page?
- No. Text encode and decode is one tool. Image to data URI, or data URI back to a file, is another.
- Do these tools use a language model?
- No. Only the AI writing group sends your paste to a language model.