Skip to main content
7B BusyBoss

File Security

Encrypt, decrypt, hash, and password-protect files entirely in your browser.

7 tools · sorted by popularity

File security tools: encrypt, lock, verify

The seven file security tools here do three different jobs, and the difference matters more than the shared AES-256 label suggests. Encryption hides content so that only the password holder can read it. A password-protected ZIP does the same for a bundle of files, under the weaker key derivation the ZIP format fixes. A hash hides nothing and proves that two copies are byte-for-byte the same. All of it runs through the browser's Web Crypto API on your device; neither the file nor the password is sent anywhere.

Encryption, and its one rule

File Encrypter writes a .enc container using AES-256-GCM with a key derived from your password by PBKDF2 at 200,000 iterations and a fresh random salt per file, so the same file encrypted twice gives two different outputs. Text Encrypter does the same for pasted text and hands back base64 that survives email and chat. Both formats are specific to this site and open only in File Decrypter and Text Decrypter, which fail cleanly on a wrong password rather than producing garbage. The rule: there is no recovery. Decrypt once to confirm the password works before you delete the original.

ZIP passwords

Password-Protect a ZIP builds a WinZip-style AES-256 archive, with two catches the format imposes: the key is derived with only 1,000 PBKDF2 iterations, so password length does all the work, and file names are not encrypted, so anyone can list them. It opens in 7-Zip, WinRAR, Keka or The Unarchiver, not in Windows File Explorer or the macOS Archive Utility, which handle only the old ZipCrypto scheme. Remove ZIP Password repacks an archive without encryption when you already know the password; it does not guess or crack one.

Checksums

File Hash Generator computes SHA-1, SHA-256, SHA-384 or SHA-512 for a file you choose, to compare with the digest a publisher listed. Use the algorithm they used, which is nearly always SHA-256. A match proves you received the published bytes; it says nothing about whether those bytes are safe.