Encrypt and decrypt text or files with a password, using AES-256-GCM or an AES-256-CBC format that the openssl command line can read. Everything runs on your device with the Web Crypto API, and files of any size are processed in chunks.
Choose Encrypt or Decrypt, and Text or Files.
Enter the Password, and the Confirm password when encrypting.
When encrypting, pick a Format: AES-256-GCM (the default) or OpenSSL compatible, and change the PBKDF2 iterations if you need to.
Paste the text or drop the files, then click Encrypt or Decrypt.
Copy the Base64 output, or download each result; with several files, use Download all (ZIP).
No. Encryption runs in your browser with the Web Crypto API. Passwords, keys and files are never stored or sent.
AES-256-GCM is authenticated encryption with a key derived by PBKDF2-SHA256 (600,000 iterations by default) and a random salt, so a wrong password or any change to the data is always detected. OpenSSL compatible produces the same bytes as openssl enc -aes-256-cbc -pbkdf2 (10,000 iterations by default), but CBC has no integrity check, so tampering is not reliably detected.
OpenSSL compatible output, yes: the tool shows the Matching openssl command, for example openssl enc -d -aes-256-cbc -pbkdf2 -in file.enc -out file (add -a for Base64 text). The AES-256-GCM output uses this tool's own XTENC file layout, so you need this tool to open it.
Yes. The format is detected from the file header. If the file was made without -pbkdf2, choose Legacy (-md sha256) for OpenSSL 1.1 and later or Legacy (-md md5) for older versions under OpenSSL settings, and match -iter if it was changed.
The data cannot be recovered; there is no reset or backdoor. Short passwords can be guessed by brute force, so use 12 or more characters or a passphrase.
The output file keeps the original name with .enc added, and its size is about the same as the original, so the file name and rough size remain visible. Only the contents are protected.