DevTools Logo

Client-Side File Encryptor

Client-Side File Encryptor

AES-256-GCM file encryption with PBKDF2 — the key and the file never leave your device

File & password

Cipher algorithm

Hardware-accelerated authenticated encryption

Operation

Examples

Cloud hardening

Input
tax-return.pdf · passphrase from a password manager
Output
tax-return.pdf.dte — ciphertext only in the sync folder

The provider stores bytes it cannot read; share the passphrase by a different channel.

About this tool

Real cryptography, zero servers: AES-256-GCM authenticated encryption with a PBKDF2-SHA256 key stretched at 250,000 iterations, a fresh 16-byte salt and 12-byte IV per file. The Web Crypto engine in your browser does the work; the file and password never leave the tab.

Encrypted files are self-describing .dte containers (magic header + salt + IV + ciphertext with GCM tag), so decryption needs nothing but the password. Authentication means a wrong password or a flipped bit fails loudly — never silent corruption.

How to use this tool

  1. Pick a file

    Anything local; the tool flags files that already look pre-encrypted.

  2. Set a strong passphrase

    Type and confirm — there is no recovery mechanism by design.

  3. Encrypt

    Download the .dte file; nothing was uploaded at any point.

  4. Decrypt later

    Switch modes, pick the .dte, re-enter the same password, download the original.

Use cases

Cloud backups

Encrypt sensitive documents before they sync to shared storage.

Safe attachments

Send ciphertext by email; deliver the password by voice or messenger.

Cryptographic parameters

ParameterValue
CipherAES-256-GCM (authenticated)
Key derivationPBKDF2-SHA256, 250,000 iterations
Salt / IV16 bytes / 12 bytes, random per file
ContainerDTE1 magic + salt + IV + ciphertext + GCM tag

Common mistakes

Mistake:Reusing an everyday password

Fix:The passphrase is the entire security model — generate and store one properly.

Mistake:Losing the password and expecting recovery

Fix:No escrow exists by design; a password manager entry prevents the tragedy.

Frequently asked questions

Is browser-based encryption actually secure?

The cryptography is the real thing: AES-256-GCM authenticated encryption with keys derived by PBKDF2-SHA256 at 250,000 iterations. Files are processed locally by the browser's Web Crypto engine and never uploaded — the main risk is your password strength, not the math.

What happens if I forget the password?

Nothing can be recovered. PBKDF2 derivation means the key exists only when the correct password is entered; there is no backdoor, no escrow, no reset. Store the passphrase in a password manager.

Why did decryption fail with a clear error instead of a file?

That's GCM authentication doing its job. A wrong password or a single flipped byte makes the authentication tag invalid, so the tool refuses to produce corrupted output instead of silently failing.

Is there a file size limit?

The whole file is processed in memory, so practical limits depend on your device. Up to ~200 MB is comfortable on most machines; the tool warns above that. No artificial cap is enforced.

References & standards