Back to the tool

How to Choose a Passphrase for Full Disk Encryption

Choosing a passphrase for full disk encryption is the one place where an awkward, unmemorable-looking string actually pays off. The threat model is nothing like a website login: whoever steals your laptop gets to guess your passphrase offline, with no rate limiting and no lockout, for as long as they want.

That changes the math completely. A website password gets a few thousand guesses before the site locks the account. A stolen SSD gets millions of guesses per second, limited only by the attacker's hardware and the key derivation function that LUKS or BitLocker applies before each guess. So the passphrase guarding your whole drive has to be stronger than anything you use on the web. The upside, and it is a real one, is that you only have to type it once per boot. You can afford a longer phrase than you would ever use for email.

What the two big tools actually accept

On Windows, BitLocker offers a password protector for manually encrypted data partitions that requires a minimum of about 8 characters, and it generates a 48-digit numerical recovery key (eight groups of six digits) as the failsafe. On Linux, LUKS gives you 8 passphrase slots on LUKS1 and 32 on LUKS2, and LUKS2 runs your passphrase through Argon2, a deliberately slow key derivation function that makes each offline guess expensive. The details differ, but both tools are built around the same assumption: the passphrase is the only thing standing between your data and someone with a copy of the raw disk.

Here is my opinion, and I will not soften it. For full disk encryption, generate six random words from the EFF diceware list and learn to type them. Six words is roughly 77 bits of entropy, since each word contributes about 12.9 bits. That is serious overkill for anything rate-limited, and it is exactly right for a secret an attacker can hammer at offline forever. Four words (about 52 bits) is fine for accounts. Six is for the disk.

Why length costs you less here than anywhere else

Think about how often you actually type each credential. Your email password gets typed dozens of times a week, on phones, at borrowed laptops, in a hurry. Your disk passphrase gets typed once, on a real keyboard, at boot time, when you are sitting still and can afford ten seconds. It is the cheapest place in your entire security setup to spend characters, and it protects the most.

The other reason people under-protect their disks is that they reuse. They use the password manager's master password, or some remembered "strong" password they use in a few places, because typing two long secrets felt silly. Do not do this. Your disk passphrase and your password manager master password should be different random phrases. If one leaks, the other still holds, and honestly the separation forces you to treat both with the respect they need.

The recovery key is half the job

Strong passphrases create a new risk, which is you. Forget a LUKS passphrase with no header backup and the data is gone; nobody at the Linux Foundation can recover it. Lose the BitLocker recovery key and the 48 digits are your only way back in. I have seen more people locked out of their own drives than broken into, and it is not close.

So the setup has two steps, and people keep skipping the second. First, generate the six-word phrase here and memorize it by typing it a few times a day for a week. Second, before you forget that it matters, write the recovery key on paper and store it somewhere that is not the encrypted laptop. Not in a note on the encrypted laptop. A drawer, a safe, a trusted person's house. This sounds obvious and it is the step everyone rationalizes away.

One thread I will leave open, because I do not have a clean answer: BitLocker offers to back up your recovery key to your Microsoft account, which is undeniably convenient and undeniably a third party holding the keys to your drive. Some people consider that a backdoor and keep their key on paper; others consider a paper key in a drawer the greater risk. I have read the arguments and I am genuinely split. The one choice I cannot defend is having no backup at all, and that is the one most people make by default.

Frequently asked questions

Can I use the same passphrase for disk encryption and my password manager?

No. Your disk passphrase and your password manager master password should be different random phrases. If one is compromised, the other still holds, and you change your most critical credential far less often when they are separate.

What happens if I forget my full disk encryption passphrase?

Without the passphrase or a recovery key, the data is gone for good. That is the entire point of the encryption. LUKS and BitLocker both warn about this because the recovery options have to be set up before you need them: back up your LUKS header, and store the BitLocker 48-digit recovery key somewhere that is not on the encrypted drive.

Is four words enough for LUKS or BitLocker?

Four random words from a 7,776-word list carry about 52 bits of entropy, which is plenty against online guessing. But a stolen laptop allows offline guessing, and LUKS passphrases are hardened by a key derivation function, so cracking speed varies by hardware. Six words (about 77 bits) is the safer margin for something that guards every file you own.

Should I add numbers and symbols to a disk encryption passphrase?

Two extra words beat any amount of symbol-sprinkling. Each additional random word multiplies the attacker's work by 7,776; bolting a "!" on the end multiplies it by almost nothing, because cracking rules try that first.

Related reading: How Many Words Does Your Passphrase Need? Entropy Math, Worked Out · Diceware Passphrase vs Random Password: Which Wins? · Passphrase and Password Manager: How to Set Them Up Together · The Password Manager Emergency Sheet · Can I Reuse the Same Passphrase for Multiple Accounts?

Try the tool

Generate six random words and use them as-is. Generate a passphrase here, offline, in your browser. Nothing is sent anywhere.

Get new free tools by email

Want the next guide in your inbox? I publish one practical guide per new tool. Subscribe to the free newsletter on Substack. No spam, unsubscribe anytime.