VeraCrypt review — encrypted containers and disk encryption
VeraCrypt is free, open-source and independently audited encryption for Windows, macOS and Linux: encrypted containers that mount as a drive, or complete partitions and USB drives.

VeraCrypt review
VeraCrypt is free, open-source and independently audited encryption for Windows, macOS and Linux: encrypted containers that mount as a drive, or complete partitions and USB drives.
Who is this for? Anyone who wants to encrypt sensitive files on Windows, macOS or Linux — in a container or on a full drive. System disk encryption is already covered for most users by BitLocker or FileVault; VeraCrypt adds value for standalone containers, USB drives and hidden volumes.
Two use cases
Encrypted container (recommended for beginners): VeraCrypt creates a file on your drive — say documents.hc. That file is an encrypted vault. You open it with VeraCrypt, enter your password, and it appears as a regular drive in your file explorer. Everything you store in it is automatically encrypted. Unmount the container, and the files are inaccessible without the password.
Partition or drive encryption: VeraCrypt can also encrypt a complete partition or external storage medium (USB drive, external disk). Useful for external drives with sensitive data that you travel with. Note: this formats the drive and erases what is on it; only Windows can encrypt an NTFS partition with its files in place.
Note: VeraCrypt can also encrypt the system drive, but only on Windows 11 and Windows 10 version 1809 or later (x64, not ARM64), and it needs a VeraCrypt Rescue Disk. For system disk encryption, the built-in alternatives in the table below are simpler for most people.
Comparison with built-in encryption
| VeraCrypt | BitLocker (Windows) | LUKS (Linux) | FileVault (macOS) | |
|---|---|---|---|---|
| Open-source | Yes | No | Yes | No |
| Public independent audit | Yes (2016, 2020; see Audit) | Not possible (closed source) | None found | Not possible (closed source) |
| Hidden volumes | Yes | No | No | No |
| Containers (single files) | Yes | Via a VHD file | Yes (file via a loop device) | No (macOS has encrypted disk images in Disk Utility) |
| Cross-platform | Yes | Limited (Linux can open it with cryptsetup) | Linux | macOS only |
| Built-in | No | Windows Pro, Enterprise, Education (Home: Device Encryption on supported devices) | Most distros | macOS |
BitLocker caveat: BitLocker is closed source, and Microsoft attaches the recovery key to your Microsoft account (or work or school account) when Device Encryption switches on at sign-in. For higher-risk use, many people therefore prefer VeraCrypt or LUKS.
Sources for the table: VeraCrypt documentation, Microsoft Learn and Support (BitLocker overview and FAQ, Device Encryption), cryptsetup man page and FAQ, Apple’s Disk Utility User Guide. Checked 2026-11-08.
Hidden volumes
VeraCrypt supports hidden volumes: one container with two passwords. Password A shows innocent files. Password B shows the actually sensitive files. According to VeraCrypt’s documentation, it should be impossible for a third party to prove a hidden volume exists, provided you follow its precautions (see the VeraCrypt guide).
This is relevant for journalists and activists or people storing sensitive information in jurisdictions with compelled decryption laws. Not everyone shares VeraCrypt’s view: the cryptsetup (LUKS) FAQ argues that where authorities can demand your keys, the presence of encrypted data alone may already be enough to put you under pressure, hidden volume or not.
Audit
VeraCrypt 1.18 and its bootloaders were independently audited in 2016 by QuarksLab, funded by the Open Source Technology Improvement Fund (OSTIF). OSTIF counts 8 critical, 3 medium and 15 low/informational issues. New problems included the GOST 28147-89 cipher, outdated compression code and bootloader leaks such as keystrokes not being wiped after authentication. According to OSTIF, VeraCrypt 1.19 fixed the vast majority of them. Some issues were not fixed because the fixes were too complex, and VeraCrypt documented workarounds instead. QuarksLab names two unfixed problems inherited from TrueCrypt: an AES implementation susceptible to cache-timing attacks (fixing it needs substantial changes to the code), and keyfile mixing that is not cryptographically sound (fixing it would break TrueCrypt compatibility). QuarksLab adds that on processors with AES-NI, which almost every current PC has, VeraCrypt uses a different AES implementation that is not susceptible.
In 2020 Germany’s federal cyber security agency BSI published a security evaluation by Fraunhofer SIT of VeraCrypt 1.23 (with parts of 1.24). It found no substantial security issues and no vulnerabilities in the cryptographic algorithms. It did criticise the development practices and code quality (at the time mostly one developer, much inherited TrueCrypt code), and for that reason did not recommend VeraCrypt for sensitive data or high security requirements. Since then, RIPEMD-160 and GOST89 (both criticised in the report) were removed in 1.26, and Argon2id, the kind of state-of-the-art key derivation the report recommended, became an option in 1.26.29 (June 2026). That release also fixed a hidden-volume weakness in the Windows versions 1.26.6–1.26.28.
We found no public independent audit of a later version. The point is not that VeraCrypt is flawless, but that it is open-source, has been through real public audits, and responds to findings — more than any closed-source alternative here can show.
Installation and use
VeraCrypt is available for Windows, macOS, and Linux. Download it from the official Downloads page or the signed releases on GitHub; each download has a PGP signature, with the key and its fingerprint on the Downloads page. (The site moved from veracrypt.fr to veracrypt.io / veracrypt.jp; the old address redirects.)
- macOS: VeraCrypt needs FUSE-T or macFUSE. VeraCrypt recommends its FUSE-T version for Macs with Apple silicon.
- Linux: VeraCrypt offers packages for Debian, Ubuntu, Fedora, CentOS and openSUSE, plus an AppImage and generic installers. There is no official Flatpak, and VeraCrypt is not on Flathub (checked 2026-11-08).
Creating a container, in short (VeraCrypt 1.26.31; the VeraCrypt guide has all 12 steps, including the screens that only appear in some cases):
- Click Create Volume, choose Create an encrypted file container → Next, then leave Standard VeraCrypt volume selected → Next.
- Click Select File… and type a new filename, for example
documents.hc. Don’t pick an existing file: VeraCrypt overwrites it. - Keep the defaults under Encryption Options (AES, SHA-512), then set the Volume Size and a strong Volume Password.
- Choose the Filesystem: exFAT if the container must work on both Windows and macOS. VeraCrypt’s own default is FAT (no files over 4 GiB); if you say you will store larger files, it picks exFAT on Windows, but on macOS and Linux the system’s own filesystem (Mac OS Extended, Ext3), which the other systems can’t fully use. On Linux, exFAT is only listed if
mkfs.exfatis installed. On macOS and Linux, also choose I will mount the volume on other platforms. - Move the mouse randomly inside the wizard window, then click Format.
Using it: select a free drive letter (Windows) or slot (macOS, Linux), click Select File…, choose the container, click Mount and enter the password. When you are done, select the volume and click Unmount — always before you copy, back up or sync the container file.
Already using VeraCrypt? Update to the current release (1.26.31 as of 8 November 2026). Since 1.26, VeraCrypt no longer opens TrueCrypt volumes or volumes that use RIPEMD-160 or GOST89; the guide’s section Already using VeraCrypt or TrueCrypt? explains how to convert them.
Caveats
Windows: forensic traces. If a VeraCrypt container has been mounted on Windows, traces can remain according to VeraCrypt’s documentation: its own volume history (unless Never save history is ticked), registry entries such as shellbags, and since Windows 8 an Event 98 entry for NTFS volumes. For maximum protection: use on a live OS like Tails, which can open VeraCrypt volumes but not create them.
Forget password = lose data. VeraCrypt has no recovery option. Store passwords in KeePassXC or another offline password manager.
Strong password, slow mount. VeraCrypt intentionally uses slow key derivation (PBKDF2 with high iteration counts, and optionally Argon2id for non-system volumes since 1.26.29) to hamper brute force. Mounting can take a moment — this is a feature, not a bug.
Hidden volumes need a current release. On Windows, versions 1.26.6–1.26.28 left zeroed sectors at 128 MiB intervals when creating a hidden volume inside a container file (advisory GHSA-jjcr-75w7-58jp, CVE-2026-54073); fixed in 1.26.29. If you created such a hidden volume with one of those versions and rely on its deniability, recreate it on a current release and securely erase the old container.
Pros and cons
Pros
- Hidden volumes with two passwords — plausible deniability if compelled to decrypt, according to VeraCrypt, provided you follow its precautions
- Cross-platform: encrypted containers open on Windows, macOS, and Linux (choose exFAT)
- Open-source and publicly audited (QuarksLab / OSTIF 2016, Fraunhofer SIT for the BSI 2020); the project responds to findings
- Containers are just files — easy to back up, move, or store anywhere (unmount first)
- Intentionally slow key derivation (PBKDF2 with high iterations, optionally Argon2id) makes every password guess expensive
Cons
- On Windows, VeraCrypt history, registry entries and the event log may leave forensic traces that a container was mounted — use Tails for maximum protection
- Forgetting the password means permanent data loss — no recovery option
- The BSI’s 2020 evaluation criticised development practices and code quality and did not recommend VeraCrypt for high security requirements; two findings inherited from TrueCrypt were left unfixed in 1.19, after the 2016 audit
- System disk encryption on Windows leaves BitLocker as a simpler alternative for most users who don’t need cross-platform or hidden volumes
Conclusion
For sensitive files stored on an external drive or that you want to protect against disk seizure: VeraCrypt is the standard. Open-source, audited, cross-platform. The learning curve is low if you only use containers. For very high-risk use, weigh the BSI’s reservations about code quality.
Use VeraCrypt for files you want to store locally encrypted. Use Proton Drive for encrypted cloud storage.
Getting started
Install VeraCrypt (on a Mac with FUSE-T), create a container as in Installation and use above, store the password in your password manager, and unmount before every backup. The VeraCrypt guide has the full steps, hidden volumes, backups and the pitfalls.
Next step
Chosen VeraCrypt?
- KeePassXC review — store your VeraCrypt password offline; without this you lose the container if you forget it
Similar options
- Proton Drive review — zero-knowledge cloud storage as an alternative to local encryption
- iStorage datAshur Pro review — hardware-encrypted USB without software
Want to go further?
- Secure laptop guide — VeraCrypt as part of a secure desktop environment