Passphrase Strength Calculator

Why passphrases beat passwords

A passphrase is a short sequence of ordinary words — "correct horse battery staple" is the famous example — and it beats a traditional password for a reason rooted in mathematics, not fashion. Password strength comes from entropy: the number of equally likely possibilities an attacker must try. A password's entropy grows with its character set and length, but humans are terrible at generating random characters and worse at remembering them, so real passwords cluster around predictable patterns that attackers exploit. A passphrase's entropy grows with its word count and its wordlist size, and because words are memorable, a passphrase can carry far more entropy than a password a human will actually remember. Four random words from a 7,776-word list carry about 51.7 bits of entropy — stronger than most eight-character passwords people actually use, and dramatically easier to recall.

The memorability advantage is not a soft benefit; it is a security feature. A password that cannot be remembered gets written down, reused across sites, or reset constantly — each of which creates vulnerabilities worse than the password's theoretical weakness. A passphrase that can be remembered gets used correctly: unique per site, never written down, never reused. Security systems fail at the human layer far more often than at the mathematical layer, and passphrases are designed for the human layer. That is why standards bodies and security teams increasingly recommend passphrases, and why password managers now generate word-based passphrases alongside character-based passwords.

How the calculation works

Enter the number of words in your passphrase and the size of the wordlist they were drawn from. Entropy in bits equals word count multiplied by the base-2 logarithm of the wordlist size: each word contributes log2(wordlist) bits, because choosing one word from a list of N possibilities is equivalent to log2(N) coin flips. The classic Diceware list has 7,776 words, contributing about 12.93 bits per word; a smaller list of 2,048 words contributes exactly 11 bits per word. Crack time is then estimated by dividing the total number of possibilities, 2 raised to the entropy, by an assumed attacker speed of one billion guesses per second — a generous rate representing well-resourced offline attacks against a stolen hash. The result is the time an attacker needs on average to try half the possibilities, which is the standard convention for such estimates.

Two warnings matter enormously. First, the calculation assumes the words were chosen randomly. Words you picked yourself — a lyric, a quote, a sentence from a book — carry far less entropy than the formula claims, because attackers try common phrases first. Only dice rolls, a trusted generator, or a password manager produce the randomness this maths assumes. Second, the one-billion-guesses-per-second rate assumes an offline attack against a weak hash; online attacks against a service with rate limiting are vastly slower, while attacks against a poorly stored hash can be faster. Treat the crack time as an order-of-magnitude guide, not a guarantee, and prefer a margin of safety: aim for at least 60 bits for important accounts and 80 or more for master passwords and encryption keys.

Reading your results

Worked example: four words from a 7,776-word list give 51.7 bits of entropy, and at one billion guesses per second the crack time runs into millions of seconds — roughly six to seven weeks of continuous guessing, which is a meaningful barrier for an ordinary account but not a fortress. Six words from the same list give 77.5 bits, pushing the crack time into millions of years, which is effectively uncrackable by brute force. Three words from a 2,048-word list give exactly 33 bits, crackable in under ten seconds at the assumed rate — a vivid demonstration that short passphrases from small lists are barely better than weak passwords. Word count is the dominant lever: each additional word multiplies the attacker's work by the full wordlist size.

Common mistakes that destroy passphrase entropy

The fatal mistake is choosing words yourself. Human-chosen words are predictable: they follow grammar, they come from songs and sayings, and they reuse familiar names. An attacker with a dictionary of common phrases will crack "blue sky happy dog" far faster than the formula suggests, because the effective wordlist is not 7,776 words but the few thousand phrases humans actually pick. The second mistake is reusing one passphrase across sites: a breach anywhere exposes everywhere. The third is modifying a passphrase predictably — capitalising the first word, adding "123" at the end — which attackers already model. Randomness must come from a generator or dice, the passphrase must be unique per important account, and the strongest passphrase in the world still deserves two-factor authentication alongside it.

Building a passphrase you will actually use

• Generate six words with dice or a trusted password manager — never pick them yourself.
• Join them with spaces or hyphens; separators add negligible entropy but aid memory and typing.
• Picture a vivid, absurd scene linking the words — memory loves images, not lists.
• Type the passphrase ten times over two days; muscle memory will carry it thereafter.
• Store it in a password manager as backup, and protect the manager itself with your strongest passphrase plus a hardware key.

Passphrases, passwords, and the right tool for each

Passphrases suit anything a human must type or remember: master passwords, device unlock, Wi-Fi, and accounts without a manager at hand. Random character passwords suit everything else — individual website accounts stored in a manager, where memorability is irrelevant and maximum entropy per character wins. The two are complements, not rivals: use a strong passphrase for the vault, and let the vault hold long random passwords for everything inside it. That architecture gives you the best of both worlds — one memorable secret of genuine strength, guarding hundreds of secrets you never need to remember at all. Calculate the entropy, choose the word count honestly, generate randomly, and never reuse the result.

Storing passphrases safely

A strong passphrase still needs a safe home. The best home is a reputable password manager, protected by your strongest passphrase and a second factor such as a hardware security key. The manager generates, stores, and fills unique passphrases and passwords for every account, so you only need to remember one master secret — which is exactly the job a passphrase does best. Choose a manager with a long track record, independent security audits, and end-to-end encryption, meaning the provider itself cannot read your vault. Enable its emergency-access feature, naming a trusted person who can request access after a waiting period, so your accounts are recoverable if something happens to you. A passphrase memorised but never backed up is a single point of failure; a passphrase stored in a manager with emergency access is a system.

For passphrases you must remember without a manager — device unlock codes, for instance — use memory techniques rather than writing them down. Link the words into a vivid, absurd mental image and rehearse it: picture the scene, say the words aloud, and type them several times over the first two days. Spaced repetition does the rest: recall after one day, after three days, after a week, and the passphrase moves into long-term memory. Avoid the tempting shortcuts that undermine security: never reuse the passphrase elsewhere, never store it in an unencrypted note or photo, and never share it over chat or email, even with someone you trust — if they need access, share through the manager's secure sharing feature instead. A passphrase is only as strong as its storage, and a little care here protects all the entropy you calculated.