Encrypted file containers without disk mounting
LockBox
Encrypted file containers for confidential exchange, local storage, and sending through any channel you already use.
- Create container
- Extract container
- Compress folder before encryption
- Crypto padding above container
What LockBox does
LockBox is a Windows desktop application that packs a selected folder into one encrypted container. The contents, subfolders, file names, and folder names are encrypted, so the output looks like one protected file rather than a readable archive.
The container can be copied to a USB drive, sent through a messenger, uploaded to cloud storage, or attached to email. Without the master password, the correct keys, and the correct order of encryption layers, outsiders cannot access the files inside.
All processing is local on the computer. LockBox does not collect, upload, or send information about your files, folders, keys, passwords, license, device, or user account.
The application does not require administrator rights. It does not mount virtual disks, install drivers, or request access to protected operating-system functions.
Multiple encryption layers can use independent algorithms and keys. With strong random keys and a protected device, brute-force decryption is considered computationally impractical even with supercomputer resources.
LockBox contains no hidden advertising, background telemetry, or secret network features. Its visible job is to create LockBox containers and open containers created by LockBox.
Free / Pro / Max
| LockBox | Free $0 |
Pro $3 |
Max $7 |
|---|---|---|---|
| PC | 1 | 1 | 1 |
| Encryption iterations | 1 | 3 | 20 |
| Compression | - | + | + |
| AES / ChaCha20 / Serpent / Twofish / Camellia / ARIA | AES-128 | + | + |
| Crypto padding above container | - | - | + |
License activation
The first 100 activations of the MAX edition are free.
Activated: 0 of 100. Remaining: 100.
FAQ
What is a LockBox container?
A container is one encrypted file that stores the selected folder, nested folders, file contents, and encrypted file and folder names.
Is it safe to publish a container publicly?
The container can be transferred through public channels because the data inside remains encrypted. Do not publish passwords or keys together with the container.
Why do I need crypto padding?
Crypto padding adds encrypted random data to make the final container larger than the real payload. It helps hide the approximate size of the original files.
What happens if someone downloads my container?
They only receive an encrypted file. Without the master password, all iteration keys, and the correct order of layers, the contents and names remain inaccessible.
Why is the master password needed?
The master password opens the encrypted metadata of the container. Metadata tells the program how many encryption layers exist and which algorithms were used.
What happens if I enter a wrong key during unpacking?
If any iteration key is wrong, that layer cannot be decrypted and unpacking stops with an error. The program cannot guess or recover missing keys.