Encoding & Crypto Tools
Encode, decode, hash, sign-inspect and generate — using your browser's native crypto engine. Nothing is ever uploaded.
Base64 Encode / Decode
UTF-8 safe Base64 with URL-safe variant support.
Password Generator
Strong random passwords with charset control.
Hash Generator
MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC32 at once.
UUID Generator
Bulk-generate cryptographically random UUID v4.
JWT Decoder
Decode JWT header and payload, check expiry locally.
Encode / Decode
Escape or unescape HTML special characters.
AES-256 Encrypt / Decrypt
Password-based AES-GCM encryption, fully in-browser.
Unicode Converter
Convert text to \uXXXX escapes and back.
Gzip Compress / Decompress
Text to a real .gz file or Base64 and back — native CompressionStream, nothing uploaded.
HMAC Generator
Keyed signatures with SHA-1, SHA-256, SHA-384 or SHA-512 via Web Crypto — plus the openssl, Node and Python equivalent.
Barcode Generator
Code 128, Code 39, EAN-13, UPC-A and ITF-14 with check digits computed and verified — export crisp SVG or high-resolution PNG.
Password Strength Checker
Entropy estimate, realistic crack times and the exact patterns — dictionary words, keyboard runs, dates — that weaken a password.
TOTP Generator (2FA)
RFC 6238 two-factor codes from a Base32 secret, with a live countdown, a clock-skew check and the otpauth:// URI.
Certificate Decoder
Decode an X.509 PEM or DER certificate — subject, issuer, validity, SANs, key usage, public key and fingerprints.
Base32 Encoder / Decoder
RFC 4648 standard, base32hex and Crockford — with optional padding and a hex view for binary payloads.
Crypto-grade privacy
Hashing and encryption on this site use the browser's built-in Web Crypto API — the same primitives trusted for TLS. Your input never leaves the device: there is no server to send it to. This makes the tools safe for tokens, keys, password hashes and other sensitive material.
FAQ
Can you recover a password from a hash?
No — and no legitimate tool can. Hashing is one-way. Use the Hash Generator to verify hashes, not to crack them.
Does the JWT decoder verify signatures?
No, it decodes and displays header, payload and expiry. Signature verification requires the secret or public key and is planned as a separate tool.
Which algorithms are used for AES?
AES-256-GCM with a PBKDF2-SHA256 key derived from your password (150,000 iterations, random salt and IV per message).