Folder Lock Vault: Local encrypted vaults for the folders you actually use

Protect client work, financial documents, personal archives, and other private Mac folders inside local AES-256 encrypted sparsebundle vaults. Mount a vault as a normal Finder folder when needed, then eject it to relock. No account, cloud sync, ads, or tracking. The original folder is moved to Trash only after the encrypted copy succeeds. Forgotten passphrases cannot be recovered.

I built Folder Lock Vault because I wanted a focused option between leaving private folders exposed and uploading them to a cloud service. The workflow stays familiar: choose a folder, create a password-protected local vault, use it through Finder, and eject it when finished. I would especially value feedback on where the lock, unlock, or relock flow feels unclear. Please start with non-sensitive sample files and keep a separate backup.

I m preparing the launch of Folder Lock Vault, a small macOS utility that turns a normal folder into a local AES-256 encrypted sparsebundle. It mounts as a Finder folder when needed and relocks when ejected; there is no account or cloud sync.

For people who protect client files, financial documents, or personal archives, which part matters most to your confidence in the workflow: clear confirmation that the encrypted copy succeeded, a simple mount/eject experience, better backup guidance, or very explicit passphrase-recovery warnings?

I m especially interested in practical feedback on the lock unlock relock flow. If you test it, please start with non-sensitive sample files and keep a separate backup.

Folder Lock Vault

Local encrypted vaults for the folders you actually use

Local encrypted vaults for the folders you actually use

Forum Threads

What makes a local folder-protection workflow trustworthy on macOS?

Forum Threads

What makes a local folder-protection workflow trustworthy on macOS?