About

This Client-Side Encryption Suite provides a Zero-Knowledge architecture for securing sensitive data. Unlike server-side tools, your data never leaves your device unencrypted. We utilize the Web Crypto API - the browser's native, highly optimized cryptographic primitive - eliminating the need for vulnerable third-party JavaScript libraries.

The tool employs AES-GCM (Advanced Encryption Standard in Galois/Counter Mode), the industry gold standard for authenticated encryption. This ensures not only confidentiality but also data integrity. Keys are derived using PBKDF2 with 100,000 iterations of SHA-256, rendering brute-force attacks computationally prohibitive. Whether securing confidential documents for transfer or protecting personal notes, this tool guarantees mathematical security.

Formulas

The core encryption process involves deriving a cryptographically strong key from your password, then applying the AES algorithm. The final payload structure concatenates the Salt, Initialization Vector (IV), and Ciphertext.

{

Key ← PBKDF2(Password, Salt_128-bit, iter=100k)Cipher ← AES-GCM(Key, IV_96-bit, Plaintext)Payload = Salt || IV || Cipher

Authenticated Encryption (GCM):

The Galois/Counter Mode ensures integrity by computing an authentication tag T alongside the ciphertext C. If T does not match during decryption, the operation returns NULL, indicating tampering or a wrong password.

G(x) = x × H mod (x¹²⁸ + x⁷ + x² + x + 1)

Reference Data

Cipher Standard	Key Size (Bits)	Block Size	Security Level	Structure
AES-GCM	256	128	MILITARY	Substitution-Permutation + Galois Field
ChaCha20-Poly1305	256	64	HIGH	Stream Cipher + MAC
RSA-OAEP	4096	Variable	HIGH	Integer Factorization (Asymmetric)
3DES	168	64	LOW	Feistel Network (Legacy)
Blowfish	32-448	64	MEDIUM	Feistel Network

Frequently Asked Questions

No. This tool uses AES-256. There is no "backdoor" and no "password reset". Without the exact password, the data is mathematically indistinguishable from random noise and cannot be recovered by anyone, including us.

No. All encryption and decryption happen strictly within your browser's memory using the Web Crypto API. You can even disconnect from the internet after loading the page and the tool will continue to function fully.

The encrypted file includes a 16-byte random Salt (for key derivation) and a 12-byte Initialization Vector (IV) prefixed to the ciphertext. Additionally, the GCM mode adds an authentication tag (16 bytes). For very small text, this overhead is noticeable; for large files, it is negligible.

To ensure browser stability, we currently soft-limit files to 100MB. Processing larger files entirely in client-side RAM can cause browser tabs to crash depending on your device's available memory.