What encryption is used?

AES-256-GCM via the browser's Web Crypto API. Keys are derived from your password with PBKDF2 (210,000 SHA-256 iterations).

Is the password sent anywhere?

No. Encryption, decryption, and key derivation all run locally — nothing is uploaded.

The data is irrecoverable. There is no backdoor and no recovery option by design.

03·Utility/file-encryption

in-browser

⌘K

How it works

03·Utility/file-encryption

in-browser

⌘K

Drop any file to encrypt or click to browse

AES-256-GCM · max 50 MB

Files stay on your device — never uploaded

AES-256-GCM via the browser's built-in Web Crypto API. Keys come from your password via PBKDF2 (210,000 SHA-256 iterations).

No. Everything runs in your browser. The password is never uploaded or stored.

There is no recovery. AES-GCM with PBKDF2 is designed to make brute-force infeasible, so a forgotten password means the data is gone.

The .enc container format is specific to this tool. To use elsewhere, decrypt here first and re-encrypt with your other tool's format.