Passphrase vs Password: Which Should You Use?
The honest answer is that this is not a rivalry. A passphrase is a password built from words instead of characters, and the right choice depends on one question: will a human memorize and type this secret, or will software handle it? Get that question right and the format picks itself.
Definitions first. A password here means a random string of characters, like kV9#mQ2$xL7p. A passphrase means several words chosen at random from a large list, like plank-orbit-satchel-nimbus-quartz. Both must be generated randomly. A human-invented string of either shape loses most of its theoretical strength.
The entropy math, both ways
Entropy measures the search space in bits; each bit doubles an attacker’s work.
Random character passwords: entropy = length × log2(character set size).
| Password | Set | Approx. entropy |
|---|---|---|
| 8 chars, full ASCII (94) | 94 | ~52 bits |
| 12 chars, mixed case + digits (62) | 62 | ~71 bits |
| 16 chars, lowercase only (26) | 26 | ~75 bits |
| 16 chars, full ASCII | 94 | ~105 bits |
| 20 chars, full ASCII | 94 | ~131 bits |
Random diceware passphrases: entropy = words × log2(7776) ≈ words × 12.9.
| Passphrase | Approx. entropy |
|---|---|
| 4 words | ~52 bits |
| 5 words | ~64 bits |
| 6 words | ~77 bits |
| 7 words | ~90 bits |
Read the two tables together and the trade becomes visible. A 4 word passphrase matches an 8 character full-ASCII password. A 6 word passphrase roughly matches 16 random lowercase characters. Per keystroke, dense random characters win: that 16 character ASCII password packs 105 bits into 16 keystrokes, while a passphrase needs about 8 words and 40+ keystrokes to match it. Per unit of human memory, words win by a landslide: nobody reliably memorizes kV9#mQ2$xL7pW4tz, but five random words stick within a day or two.
Honest comparison
| Factor | Random password | Random passphrase |
|---|---|---|
| Entropy per character typed | High | Lower |
| Entropy per memorized “chunk” | Terrible | Excellent |
| Memorability | Very poor | Good |
| Typing on a phone keyboard | Painful (symbol layers) | Easy (letters only) |
| Speaking aloud (Wi-Fi guest, support call) | Error-prone | Practical |
| Typing where you cannot paste (BIOS, console, TV) | Slow, error-prone | Manageable |
| Fits short max-length fields | Yes | Sometimes not |
| Resistance to dictionary + rules attacks | Full, if machine-random | Full, if words are machine-random |
| Best storage | Password manager | Human memory |
Neither column wins outright. Each format is the right tool for a different slot.
Decision guide by use case
Manager-filled site logins: random password. Your password manager generates, stores, and types it. Memorability is irrelevant, so take the densest option: 16 to 20 random characters from the password generator. One per site, never reused.
Memorized secrets: passphrase. The password manager master password, your computer login, full disk encryption. These are the few secrets that must live in your head, and the master password in particular can face offline cracking if your encrypted vault leaks. Use 5 words minimum, 6 for the master password, from the passphrase generator. Accept the words it gives you; rerolling for nicer words leaks entropy.
Secrets spoken aloud or typed on awkward devices: passphrase. Wi-Fi passwords you read to guests, a streaming login pecked out with a TV remote, anything relayed over a phone call. otter-jigsaw-comet-birch survives being said out loud. x7$Qw!9z does not, and the failed attempts that follow cost more than the shorter length saved.
Fields with tight length limits: random password. Some legacy systems cap passwords at 12 or 16 characters. A passphrase cannot stretch out there, so use maximum-density random characters and let the manager remember them.
Shared or emergency-access secrets: passphrase. Anything a family member might need to read off paper from a safe. Words transcribe cleanly; symbol soup gets miscopied.
Unsure how a specific choice measures up? Run it through the password strength checker, which estimates guessability in your browser.
Where NIST lands
NIST SP 800-63B deliberately avoids crowning a format. What it requires and recommends supports both:
- Require at least 15 characters where the password stands alone, and 8 only when it is one factor inside multi-factor authentication. Support long ones, 64 characters or more, which makes room for real passphrases.
- Drop mandatory composition rules. A lowercase-only passphrase is fine; forced symbols add little and distort human choices.
- Screen candidates against lists of breached and commonly used passwords, which catches famous phrases and lazy patterns in either format.
- Allow paste, so password managers work, which is what makes unique random passwords per site practical at all.
The guideline’s underlying position is the same as the math’s: length and randomness are what count. Format is ergonomics.
The setup that uses both
The strongest practical arrangement is not choosing one format. It is one memorized passphrase protecting a vault full of random passwords:
- Generate a 6 word passphrase. Memorize it. This is your master password.
- Put a password manager behind it.
- Let the manager generate a unique 16 to 20 character random password for every account.
- Reserve passphrases for the handful of other secrets you must type by hand: device login, disk encryption, Wi-Fi.
One phrase in your head, hundreds of dense random strings in the vault. That is the passphrase versus password debate resolved: both, each where it belongs.
Frequently asked questions
- Is a passphrase always stronger than a password?
- No. Strength depends on entropy, not format. A 20 character machine-random password beats a 4 word passphrase. A 6 word random passphrase beats an 8 character random password. Compare the bits, not the look.
- What should I use for my password manager master password?
- A randomly generated passphrase of 5 to 6 diceware words. It is the one secret you must memorize and type often, and it faces offline attacks if your encrypted vault ever leaks, so it needs both memorability and high entropy.
- Does NIST prefer passphrases or passwords?
- NIST SP 800-63B does not pick a format. It requires systems to accept long passwords and passphrases, drops mandatory composition rules, and recommends checking choices against breach lists. Both formats qualify if they are long and random.