Crypto tools
91 toolsEncrypt, decrypt, sign, verify, hash and derive keys in your browser, through Web Crypto and audited libraries such as noble, scure and age for the algorithms Web Crypto does not cover. Keys are generated in the page and never leave it. The classical ciphers here are puzzle tools with no security value, and each one says so on its own page.
Encrypt & decrypt12
Keys & signatures17
Password hashing7
One-time codes3
Hashes & checksums11
Classical ciphers41
Questions
Where do my keys go?
Nowhere. Keys are generated inside this tab, by Web Crypto or by an audited JS library where the algorithm needs one, and stay in page memory. Nothing is transmitted, and nothing is stored after you close it. Save the key yourself if you need it again, because this site cannot give it back to you.
Is browser crypto safe to rely on?
The algorithms are either the browser's own Web Crypto implementation, the same one used by HTTPS in that browser, or an audited library such as noble or age for the algorithms Web Crypto does not offer. The weak point is the environment: a compromised machine or a hostile extension sees what the page sees. For high-value keys, use dedicated offline tooling.
What can I decrypt a file with?
The matching tool on this site. AES-GCM decrypt reads what AES-GCM encrypt produced, RSA-OAEP decrypt reads what RSA-OAEP encrypt produced. Each tool page names its pair, and the format is the standard one, so other implementations of the same algorithm can read it too.
Are the classical ciphers secure?
No, and every one of them says so on its own page. Caesar, Vigenere, Bifid, substitution, XOR with a repeating key and the rest are puzzle tools. They are here for CTFs and teaching. Use AES-GCM encrypt for anything real.
Which password hash should I use?
Argon2 for new work, with bcrypt and scrypt available where an existing system needs them. Plain hashes like MD5 or SHA-256 are the wrong tool for passwords, no matter how many times you apply them, because they are built to be fast.