Security and Encoding

Encode text, check hashes, and inspect tokens on your device.

What this category covers

Encoding and hashing run with browser APIs. JWT pages decode the token and do not call the result verified.

URL and HTML encode and decode are inverses, so the reverse step is listed separately from ordinary next edits. The JWT decoder shows header and payload JSON plus exp, nbf, and iat against a clock you can see. It does not invent a valid signature. HMAC and the SHA-2 hashes use Web Crypto. Hash Generator also offers legacy SHA-1 and MD5 for checksums and existing systems. Those two are cryptographically broken and are not for new passwords, signatures, or authentication.

Generated identifiers and random strings use the browser’s cryptographic random source. The values are not sent to analytics. The guide on JWT decode versus verify explains why a decoded token is still unverified.

All security and encoding

Browse the full catalog