Password entropy, in plain English
Password entropy is the thing that actually makes a password strong, and almost nobody explains it in plain terms. Entropy measures how many guesses an attacker would need, on average, to crack your password by brute force. It is counted in bits, and every extra bit doubles the attacker’s work — so 80 bits is not twice as strong as 40 bits, it is roughly a trillion times stronger. Once you grasp that, most password advice makes sense: it is all about buying more bits with less pain.
Think of entropy as the size of the haystack your password hides in. If every character is chosen at random from the 94 printable characters on a standard keyboard, a 12-character password carries about 78 bits of entropy — a haystack of roughly 300,000,000,000,000,000,000,000 possibilities. Even at a billion guesses per second, searching it all would take longer than the age of the universe. The number looks absurd because the haystack genuinely is absurd. That is what “strong” means: a haystack nobody can finish searching.
The formula behind it is simple: entropy equals password length multiplied by the logarithm base two of the pool of possible characters. You never need to do this math yourself. Bits grow from exactly two things: how many characters you use, and how many different characters each position could be. Anything that increases neither of those adds no entropy, no matter how clever it feels. So if you have ever wondered what makes a strong password, here it is: length times pool size, with genuine randomness doing the choosing.
Why length beats complexity every time
Here is the comparison that ends the debate. An 8-character password drawn from all 94 keyboard characters has about 52 bits of entropy. Stretch it to 12 characters and you get roughly 78 bits. Reach 16 and you are near 105. Each added character multiplies the attacker’s work by up to 94 times, while bolting a symbol requirement onto a short predictable base word barely multiplies anything at all. “P@ssw0rd!” satisfies every classic complexity rule and falls in seconds; a 16-character random string satisfies none of the theater and stands for centuries.
This is exactly why NIST — the standards body behind the US federal authentication guidelines — dropped mandatory composition rules from its guidance on memorized secrets years ago. Forcing uppercase letters, digits, and symbols produced passwords that were painful to type, painful to remember, and only marginally stronger. Their guidance now says the opposite: let people choose long passwords, check new passwords against lists of known-compromised values, and stop expiring passwords on a fixed schedule. Length plus a breach check beats symbol salad, and it is not close.
Attackers are not guessing by hand. A serious offline attack — where someone has stolen a site’s password database and can test guesses without any server slowing them down — can run through billions of candidates per second on rented graphics cards. At that speed, a 40-bit password dies in minutes and a 50-bit password dies in days. But 78 bits outlasts civilization itself. The gap between weak and strong is not a gentle slope; it is a cliff, and length is what pushes you over the edge of it.
Passphrases: strong passwords people can actually remember
Random strings are wonderful and unmemorable, which is why passphrases exist. Take four or five words picked at random — not a sentence, not song lyrics, random — and you get a password that is both typeable and strong. With a word list of roughly 7,700 words, each random word contributes about 13 bits of entropy, so five words land near 64 bits and six words push past 77. That is the same neighborhood as a 12-character random password, except you can remember it after typing it twice.
The word “random” is doing all the heavy lifting in that sentence. A line from a song, a favorite quote, or words connected to your life collapses the haystack, because attackers do not guess blindly — they guess in order of likelihood. They try lyrics, sports teams, and keyboard patterns long before true randomness. Rolling dice for your word picks — the approach the EFF's Diceware guide popularised — or letting a random word generator choose them, is what keeps the haystack enormous. Predictable creativity is the enemy; mechanical randomness is the friend.
Passphrases are ideal for the handful of passwords you must carry in your head: your password manager’s master password, your email account, your computer login, your Wi-Fi. For everything else — the other hundred accounts — you should never be memorizing anything at all. Those get unique random strings generated by software, which brings us to the single most important sentence in this article: never reuse a password, because reuse turns one breach into every breach.
The ways passwords actually die
Almost nobody’s password dies by brute force. It dies by reuse. When a site you used years ago gets breached, your email and password land in a database attackers trade openly. Then comes credential stuffing: automated software trying that exact combination on thousands of other sites. If you reused the password anywhere, they walk straight in. Every clever password tip is worthless next to uniqueness — real people fall to the lazy reuse attack, not the elegant math attack.
The second most common death is personal information. An attacker targeting your account will try your name, your pet, your birth year, your team, and combinations of all of them, much of it harvested from your own social media. “Rover2019!” is not random; it is a shortlist. Keyboard walks like “qwerty123” and leet-speak substitutions like “P@ssw0rd” are on the shortlist too — attackers build guessing dictionaries from millions of real leaked passwords, so anything that has ever occurred to a human has occurred to a million humans, and it is in the dictionary.
Be skeptical of password strength meters as well. Many of them reward the old theater: they award full marks to short passwords containing a symbol and a capital letter, because they measure composition instead of entropy. A meter cannot know whether your password appears in a breach database, and it cannot measure true randomness in something you invented yourself. Treat a green bar as a hint, not a verdict. The real questions are always the same three: is it long, is it random, and is it unique to this site?
Password managers: the only sane answer to a hundred accounts
You cannot memorize a hundred unique 16-character random passwords, and you were never supposed to. That is what a password manager is for: it generates long random passwords, stores them in an encrypted vault, and fills them in for you. Your job collapses to remembering one excellent master password — a passphrase, ideally — and protecting that vault. The manager handles the haystacks; you handle the single key to the haystack warehouse.
If you have never used one, the migration takes an afternoon and the payoff is permanent. Install the manager, let it import the passwords your browser has been saving, and then, site by site, have it generate a fresh random password and store it. You do not need to convert all hundred accounts in one sitting — start with email, banking, and anything holding money or identity documents, because those are the accounts where a takeover hurts most. Every account you convert breaks one more reuse chain.
When you need a fresh password on the spot, FreeToolsBox’s Password Generator builds long random strings in one click, and the companion Password Strength Checker gives you a quick read on what you already have. Generators are also the right tool for Wi-Fi passwords, shared accounts, and one-off credentials you will paste once and never type. Let the machine do the randomness; machines are better at it than you.
Two-factor authentication: the lock on top of the lock
Even a perfect password has one weakness: it lives on somebody else’s server. If that server is breached badly — plaintext storage, weak hashing — your 80 bits of entropy mean nothing, because the attacker is not guessing at all. Two-factor authentication fixes this by demanding something beyond the password: a code from an app, a hardware key, a fingerprint. With 2FA switched on, a stolen password alone buys an attacker nothing, which makes it the highest-value security upgrade most people have not finished yet — CISA's cybersecurity guidance says as much.
Not all second factors are equal. Authenticator apps — the kind that display rotating six-digit codes — beat SMS codes, because phone numbers can be hijacked through SIM-swapping while an app on your phone cannot be reached that way. Hardware security keys beat everything, because they are phishing-resistant: the key cryptographically verifies the real site before it signs you in. Use whichever your important accounts support, in that order, and store recovery codes somewhere safe and offline.
A common worry is whether 2FA means a weak password is acceptable. It does not — the whole point is defense in depth. Some attacks bypass the second factor, some services implement it badly, and account recovery flows are often the weakest link in the chain. Keep the password strong and unique, add 2FA, and you force an attacker to defeat two independent defenses instead of one. That is the difference between “probably safe” and “annoyingly expensive to attack.”
What strong looks like in practice
Time to make it concrete. For a master password or anything you type often, use a passphrase of five or six random words — roughly 64 to 77 bits, memorable, typeable. For accounts handled by your password manager, generate 16 to 20 random characters from the full keyboard set — about 105 to 131 bits, absurdly strong, and you will never type them anyway. For shared Wi-Fi, a four-word passphrase is friendly and still near 52 bits — plenty against the neighbors.
Match the strength to the stakes, not the other way around. Your email account deserves maximum strength plus 2FA, because email is the recovery path for nearly everything else — whoever controls your inbox effectively controls your accounts. Banking, tax, health, and work accounts form the next tier. The forum account you created years ago to ask one question still deserves a unique random password — it costs nothing once the manager exists.
One more piece of NIST wisdom worth internalizing: stop changing passwords on a schedule. Forced rotation every 90 days produced “Summer2024!” becoming “Autumn2024!” — weaker passwords, written on sticky notes. Change a password when you have reason to believe it is compromised, when a service announces a breach, or when you discover you have been reusing it somewhere it should not be. Otherwise, a long, random, unique password with 2FA enabled can sit undisturbed for years.
The bottom line
Strong was never about symbols and capital letters. It is about entropy — bits of uncertainty — and entropy comes from length and randomness, full stop. A 16-character random string and a six-word random passphrase both clear the bar with room to spare, while “P@ssw0rd!” never did. The rest is logistics: unique passwords everywhere, a vault you trust, and a second factor on the accounts that matter.
If you do one thing today, make it this: install a password manager, then move your email account into it with a fresh generated password and 2FA switched on. That single move closes the two attacks that actually compromise real people — credential stuffing through reuse, and weak memorable passwords guarding the most important account you own. The rest can follow at your pace.
And the next time a site demands “one uppercase, one number, one special character,” smile, generate something 16 characters long in FreeToolsBox’s Password Generator, and let the rule be satisfied by accident. You will have obeyed the letter of their policy while quietly exceeding its intent by sixty-odd bits. That is what understanding entropy buys you: the confidence to ignore bad advice — including, especially, the advice printed on the form.