Online encryption tools
This category groups 6 online encryption tools built on the browser Web Crypto API: symmetric AES-256-GCM encryption with PBKDF2 key derivation, RSA key pair generation, HMAC authentication codes, bcrypt password hashes, and secret generation for signing JWT tokens. Neither your text nor your keys ever leave your machine.
They are aimed at everyday backend and DevOps work: preparing a secret before a deployment, verifying the HMAC signature a Stripe or GitHub webhook sends, generating a key pair for SSH access, checking that a bcrypt hash matches the expected password, or encrypting a note before storing it in a service with no end-to-end encryption. Each page details the algorithm, the recommended key sizes and the bad practices worth avoiding.
Tools in this category
AES Encryption
Encrypt and decrypt text with AES-256 algorithm
RSA Key Generator
Generate RSA public and private key pairs
HMAC Generator
Generate HMAC message authentication codes
Bcrypt Generator
Generate and verify password hashes with Bcrypt
Text Encryptor
Encrypt and decrypt text with custom password
JWT Secret Generator
Generate secure secret keys for signing JWT tokens
Frequently asked questions
Is it safe to encrypt sensitive information in the browser?
These tools use the native Web Crypto API, the same audited cryptographic implementation professional applications rely on, and all computation is local. For long-lived production secrets or nation-state level threats it is still preferable to generate the key material with OpenSSL or ssh-keygen on a machine you control.
Which algorithm should I use to store passwords?
Never a general purpose hash such as bare MD5 or SHA-256. Use a function designed for passwords: Argon2id as the modern recommendation, or bcrypt and scrypt, which build in automatic salting and an adjustable cost factor. The bcrypt generator in this category lets you try different cost factors before you settle on one for production.
When should I use symmetric encryption instead of asymmetric?
AES, the symmetric option, is fast and suitable for large volumes when both parties already share a password. RSA, the asymmetric option, is slow and size limited, but it lets anyone encrypt with the public key while only the private key holder can decrypt. In practice the two are combined: RSA protects an AES key and AES encrypts the actual payload.