How Password Entropy Works (Why Length Beats Complexity)

Password strength is measured in bits of entropy — a logarithmic count of how many equally likely passwords an attacker must consider. Each additional bit doubles the search space: 40 bits means about a trillion possibilities; 60 bits is a million times more than that; 80 bits, a million times more again.

The formula is simple: entropy = length × log₂(pool size), where the pool is how many characters each position could be. Lowercase only gives log₂(26) ≈ 4.7 bits per character; adding uppercase, digits, and symbols raises the pool to about 90, or roughly 6.5 bits per character. Crucially, this math only holds for randomly generated passwords — a human-chosen password built from words and predictable substitutions has far less real entropy than its length suggests, because attackers guess patterns, not raw combinations.

Compare two policies. An 8-character password using all 90 symbol types: 8 × 6.5 ≈ 52 bits. A 14-character lowercase-only password: 14 × 4.7 ≈ 66 bits — over 16,000 times stronger, and far easier to type. Each extra character multiplies the search space by the whole pool size, while widening the pool only nudges the per-character exponent.

This is why modern guidance (including NIST's) emphasizes length over mandatory symbol rules. Complexity requirements mostly cause predictable patterns — the capital first letter, the trailing '1!' — which crackers try first. A long random string, or a passphrase of four to five truly random words, delivers real entropy without the theater.

What do the bits buy you? A serious offline attacker with GPUs can test billions to trillions of guesses per second against a stolen database of fast hashes. At a very aggressive 1 trillion guesses/second: 40 bits falls in about a second, 52 bits in an hour and a half, 66 bits in a couple of years, 80 bits in tens of thousands of years, and 100+ bits outlasts the solar system.

That's the worst case — sites that hash passwords properly (bcrypt, scrypt, Argon2) slow attackers by factors of thousands to millions. But since you can't verify a site's hashing from the outside, aim for strength that survives the worst case: 75–80+ bits, which the password generator on this site reads out live as you adjust length and character sets. Sixteen random characters from a full pool comfortably clears 100 bits.