File Encryption
& Decryption
Protect any file with military-grade encryption. AES-256-GCM, ChaCha20, RSA and more. All processing happens in your browser — zero server upload.
Drop your file here
or click to browse · Any format · Processed locally
Why Choose Our Encryption Tool
Professional-grade security. Zero compromises. Everything processed in your browser.
100% Client-Side
Your files never leave your browser. All encryption and decryption is done locally using the WebCrypto API.
AES-256-GCM
The same encryption standard used by governments, banks, and militaries worldwide. Quantum-resistant via large key sizes.
PBKDF2 Key Derivation
Passwords are never used directly. PBKDF2 with 600,000 iterations and a random salt hardens against brute-force attacks.
Completely Free
No account, no subscription, no limits. Encrypt files of any size. Unlimited operations forever.
Any File Type
PDFs, images, videos, archives, documents — any file can be encrypted. No format restrictions.
File Integrity Hashes
Compute MD5, SHA-1, SHA-256, SHA-384, SHA-512 checksums to verify file integrity and authenticity.
RSA Key Generation
Generate 2048 or 4096-bit RSA key pairs for asymmetric encryption and digital signatures.
Secure Password Gen
Generate cryptographically strong passwords, API tokens, UUIDs, and PINs using browser CSPRNG.
How File Encryption Works
Understanding the security process behind every encrypted file
When you encrypt a file, here is exactly what happens step-by-step inside your browser:
A cryptographically random 16-byte salt is generated using crypto.getRandomValues(). This ensures that even the same password produces a different key every time.
Your password is processed through PBKDF2 with 600,000 iterations of SHA-512. This takes ~1 second deliberately — making brute-force attacks 600,000× harder.
A unique 12-byte initialization vector (IV/nonce) is generated. Combined with the key, this ensures ciphertext is unique even for identical files.
The file data is encrypted using AES-256 in GCM mode, which also produces a 128-bit authentication tag to detect any tampering.
The output file contains: magic header + version + algorithm + salt + IV + encrypted data + auth tag. Everything needed to decrypt is bundled in the file.
Decryption reverses the encryption process:
The tool reads the magic header to verify it's a valid encrypted file, extracts the algorithm, salt, IV, and ciphertext.
PBKDF2 runs again with the stored salt and your provided password to reconstruct the exact same encryption key.
AES-GCM verifies the authentication tag. If the password is wrong or the file was tampered with, decryption fails immediately.
The original file is reconstructed and offered as a download with its original filename.
| Algorithm | Type | Security | Speed | Best For |
|---|---|---|---|---|
| AES-256-GCM | Symmetric | ⭐ Excellent | Fast | General purpose — recommended default |
| AES-256-CBC | Symmetric | ✅ Very Good | Fast | Max compatibility with older systems |
| AES-256-CTR | Symmetric | ✅ Very Good | ⚡ Fastest | Large file encryption (parallelizable) |
| RSA-OAEP | Asymmetric | ⭐ Excellent | Slow (key size) | Key exchange, small data encryption |
A 5-word passphrase (e.g. "correct horse battery staple purple") is stronger than a complex 8-character password. Target 20+ characters.
We never store your password. If you lose it, your file cannot be recovered. Store it in a password manager like Bitwarden or 1Password.
AES-256-GCM provides both encryption AND authentication — it detects any tampering automatically. It's the gold standard.
Your RSA private key should never be shared or stored online. Keep it in a secure offline location.
Frequently Asked Questions
Everything you need to know about file encryption