Passphrase vs Password — When Memorable Beats Random Characters

Updated September 18, 2026 · ~8 min read · by Samuel Yoo

A passphrase and a random password are both secrets. They are not the same job. One is a sequence of words you can type and remember. The other is a dense character string a password manager stores and fills. Both can be strong if the bits are actually random. Both fail if you invent them yourself or reuse them.

This page is mode choice, not length policy. For how many bits is enough, use How long should a password be?. That guide owns the thresholds. This one owns when to pick words vs characters — then generate either in the browser.

Two different jobs

A random password is a string drawn from a character set: letters, digits, symbols. Something like kP3@x9Vz!Q7mN4wR. You do not memorise it. A manager autofills it. Strength is length × bits per character, assuming every character was equally likely.

A passphrase is a sequence of randomly chosen words, often with a separator: cyber-bonsai-anchor-cinder-emerald. You can read it, say it, and type it on a phone. Strength is word count × bits per word — not how “complex” the words look.

The useful contrast:

• Random characters pack more entropy into fewer keystrokes.
• Words pack less entropy per character, but each unit is something a person can hold in working memory.

Neither mode is “more secure” in the abstract. A six-word generated passphrase can beat an eight-character human password. A 16-character all-charset random string can beat a four-word phrase from a small list. Mode is not a substitute for length.

A phrase you invent — song lyric, pet names, your own “correct horse…” twist — is not a generated passphrase. If you pick the words, entropy is whatever your habits allow. Generate first. Memorise second.

If a site still forces a capital, a digit, a symbol, and a 90-day rotation, that is policy theater. It usually shrinks the space people actually use. See why password rules make things worse. Generate in the right mode; satisfy a dumb filter with a toggle if you must.

Entropy in plain English

Entropy here means: how many equally likely secrets could this generator have produced? Each extra bit doubles that space. The meter on this site shows bits, not a vague “weak / medium / strong” label.

Words. This site’s passphrase list has 256 words. log₂(256) = 8 bits per word if every word is equally likely. That is the math the passphrase generator and the home hub use:

Five words ≈ 40 bits. Six ≈ 48 bits. Those numbers assume the generator picked the words — not you.

Diceware, as a comparison only. The EFF large wordlist has 7,776 words, about 12.92 bits per word (log₂(7,776)). Four EFF words sit near 52 bits. This tool does not ship that list. A 256-word list keeps the page small; you add a word or two here to land in the same neighborhood.

Characters. For a uniformly random password:

entropy ≈ log₂(charset size) × length

With all printable charsets (about 94 symbols: lower, upper, digits, punctuation) that is ≈ 6.55 bits per character — the same figure as the length guide tables. A 16-character all-charset password is then about 105 bits. Lowercase-only is closer to 4.7 bits per character; you need more length for the same bits.

This page will not invent GPU guesses-per-second or “cracked in N hours” headlines. Offline risk is dominated by how the server hashes the secret. If you store passwords, pick a slow salted KDF — start at the hash function guide. That decision tree is already written. This page does not redo it.

When a passphrase wins

Use words when a person has to produce the secret from memory or type it often. Passphrases win on usability when you must type.

• Password-manager master password. You type this to unlock the vault. If you cannot remember it, the vault is gone. On this 256-word list, five or six generated words (40–48 bits) is the usual fit.
• Laptop or desktop login. Same daily typing. A random 20-character string is miserable on a login screen.
• Disk unlock / full-disk encryption. Forget it and the data is gone. Memorability is part of the security model, not a convenience extra.
• Wi-Fi you share aloud. cyber bonsai anchor cinder can be read to a guest. kP3@x9Vz!Q7m cannot.
• Phone keyboards. Words are fast. Symbols hide behind extra keyboards.

Do not stretch a three-word phrase to cover a high-stakes vault because it “feels long.” Add words, or switch modes.

Do not write the master passphrase on a Post-it, in an unlocked notes file, or in a plaintext document synced to the cloud. That turns a 40-bit secret into something anyone who sees the paper or the file already has. If you need a fallback, keep it in a password manager locked by a different secret you actually remember — not a sticky note on the monitor.

A short story helps memory (“the cyber bonsai dropped an anchor in cinder”). Extra capitals or two appended digits mostly pass a dumb policy filter; they do not replace a sixth word. Real strength still comes from word count and a random draw.

When a random password wins

Use random characters when a manager stores the secret and you almost never type it. Random wins on entropy density when a manager stores it.

• Every ordinary website login. Generate 16+ characters, all charsets, save in the manager, done. You are not trying to remember kP3@x9Vz!Q7mN4wR. You are trying to make each site a unique, high-density secret.
• API tokens and service secrets. Treat them like keys. Prefer 32+ random characters. Do not reuse across services. Rotate when you can.
• Anything you will paste, not recite. High bits per character, no need for English words.

If you type a “random” password every day, you picked the wrong mode — switch that one secret to a passphrase. If you invent a “memorable” password for a shopping site, generate random and let the manager fill it.

Reuse is the failure mode that beats both. One leaked hash plus a reused secret is every account that shared it. Unique per site; manager for the many; passphrase for the few you type.

How long that random string should be is the other page: How long should a password be?. This page only picks the shape.

Generate either client-side

Use the password generator — switch Random vs Passphrase and watch the entropy meter. Prefer the passphrase page when you are building a master password. Generation uses crypto.getRandomValues in your browser; nothing is uploaded and there is no signup.

Pick the mode for the job, then set length or word count until the meter matches the length guide for that threat — not a feeling about how “random” the string looks.

Related: why password rules make things worse if a policy is pushing P@ssw0rd1!. Server-side storage still starts at which hash function.