Encrypt with random keys
No layer passwords to invent or remember. Save the key archive and its password; the metadata still requires a master password.
DocumentationWorks offline
Your files. Your keys. Your control.
Encrypted file containers for confidential exchange, local storage, and sending through any channel you already use.
WindowsAndroidCLI WindowsCLI Linux
Example · Pro / Max
01AES-256 GCM
02ChaCha20-Poly1305
Container master password + Encryption layers
Works offline
23Cryptographic profiles
20Encryption layers Max
.lbxOne container format across platforms
Features
What LockBox does
Encrypted file containers without disk mounting
Verify container
Check metadata, split parts, every encryption layer and file checksums. Available in Free, Pro and Max on Windows, Android and CLI.
DocumentationMulti-layer encryption
They only receive an encrypted file. Without the master password, all layer keys, and the correct order of layers, the contents and names remain inaccessible.
Create containerSplit large encrypted containers
Pro and Max can split a container into fixed-size parts. Keep the .lbx file and all .lbx1, .lbx2... parts in one folder before extraction.
Compression / Crypto padding above containerMax container browser
Max: search file and folder names on Windows and Android. On Windows, add or remove items and save a verified copy with the same passwords and keys.
Browse containerScheduled encrypted backups
Max can create LockBox containers on a schedule while the app stays open or minimized to the tray. It is useful for regular encrypted backups and safe transfer of confidential data.
LockBox for AndroidCLI automation
Use --script when the procedure has several steps. Commands run in order, stop on the first error by default, and return a process exit code for the parent script.
Full CLI documentationContainer destruction password
LockBox overwrites the container with encrypted random-looking data while preserving the original size.
How to enableSecurity
Protection you can understand.
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.
Container master password
The master password opens the encrypted metadata of the container. Metadata tells the program how many encryption layers exist and which algorithms were used.
AES-256-GCM · PBKDF2-SHA512Encryption layers
If any layer key is wrong, that layer cannot be decrypted and unpacking stops with an error. The program cannot guess or recover missing keys.
AEAD / HMACSecret handling
For automation, prefer --master-env, --master-file, --layer-env, and --layer-file. Inline secrets work, but they may be saved in shell history or process logs.
CLI documentationKnow the limits
Protect your device and keep strong keys and tested backups. Creation, browsing and extraction use temporary plaintext files. Lost keys cannot be recovered. Destruction overwrites the selected container; other copies remain, and secure erasure on SSDs or flash storage is not guaranteed.
Downloads
Your security. On your device.
One container format across platforms
Windows
The installer adds .lbx file association and Explorer folder actions while keeping LockBox per-user and admin-free.
Installer · x64 Desktop guideAndroid
Desktop-compatible encryption on your phone
Android 7.0+ Download APK Full Android instructionsCLI automation
Scheduled jobs: run LockBox after nightly build, export, or database dump scripts, then continue with upload or retention cleanup.
CLI Linux · x64 CLI documentationBefore installing, compare your download’s SHA-256 hash with the published checksum.
SHA-256 checksumsEditions
Choose your level of control.
Pro and Max are perpetual licenses for 1 device.
| LockBox | Free$0 | Pro$20 | Max$50 |
|---|---|---|---|
| Encrypt with random keys | ✓ | ✓ | ✓ |
| Encryption layers | 1 | 3 | 20 |
| Verify container | ✓ | ✓ | ✓ |
| AES / ChaCha20 / Serpent / Twofish / Camellia / ARIA | AES-128 | ✓ | ✓ |
| Compression | — | ✓ | ✓ |
| Split container | — | ✓ | ✓ |
| Crypto padding above container | — | — | ✓ |
| Browse container | — | — | ✓ |
| Scheduler | — | — | ✓ |
| Container destruction password | — | — | ✓ |
| Activation by request | Get LockBox | Pro | Max |
Encrypt with random keys
Random keys are strong, but losing the archive or its password means losing access to your data. Keep them safe and available. Memorised passwords have an advantage over secrets written down.
Random keys cannot be combined with container destruction. This option is disabled in key mode.
Full desktop instructionsVerify container
Check metadata, split parts, every encryption layer and file checksums. Available in Free, Pro and Max on Windows, Android and CLI.
Verification uses memory. No plaintext or report is saved to disk.
Full desktop instructionsWhat 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?
Random padding increases container size to obscure the payload size. These extra bytes are not encrypted or authenticated.
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 layer key during unpacking?
If any layer key is wrong, that layer cannot be decrypted and unpacking stops with an error. The program cannot guess or recover missing keys.
What is the container destruction password?
It is a Max-only pressure-safety feature. A separate password silently overwrites the container instead of opening it, with no confirmation at the metadata password step.
Protect your device and keep strong keys and tested backups. Creation, browsing and extraction use temporary plaintext files. Lost keys cannot be recovered. Destruction overwrites the selected container; other copies remain, and secure erasure on SSDs or flash storage is not guaranteed.
Support and suggestions
For support requests, ideas, and product suggestions, write to support@logidev.io.