Password Strength Explained: Entropy, Length, and Why Symbols Matter Less Than You Think

"P@ssw0rd!" looks like a strong password. It has the capital letter, the symbol, the number — everything the signup form demanded. A modern cracking rig burns through it in under a second. Meanwhile four plain words glued together with dashes could outlive the person typing them. Password strength has almost nothing to do with how clever a password feels, and everything to do with one number: entropy.

Entropy, without the math phobia

Entropy (in bits) is just a guess counter: on average, how many tries does an attacker need? The formula is one line — length × log₂(pool size). Each lowercase letter adds about 4.7 bits. Using all 94 printable characters gets you about 6.6 bits per character.

Here's the part people miss: doubling the length doubles the entropy, and doubling the entropy doesn't double the attacker's work — it squares it. Length is the big lever. Symbols are the garnish.

• 8 chars, full 94-char set: ≈ 52 bits — falls to a determined attacker with good hardware
• 12 chars, full set: ≈ 79 bits — safe against everyone short of nation states
• 16 chars, full set: ≈ 105 bits — brute force is done. Not happening.
• 8 chars, lowercase only: ≈ 38 bits — hours, maybe less
• "P@ssw0rd!": ~0 effective bits — it's literally in the dictionary files attackers load first

Why human-invented passwords fail the math

That formula assumes randomness. Humans don't do randomness — we do patterns. Capitalize the first letter. Number at the end. Swap a→@, o→0, s→$. Attackers have watched billions of leaked passwords and their tools try exactly these shapes: "Summer2026!", "Qwerty123!", your pet's name plus your birth year. A hand-crafted password carries drastically less entropy than naive math suggests. Random generation isn't a nice-to-have here. It is the security.

How many bits is enough?

Depends who gets to guess. Online attacks — someone typing guesses into a login form — die to rate limiting: five tries, locked account. Even 40–50 bits survives that forever. Offline attacks are the nightmare: a leaked database of password hashes, attackers trying trillions of guesses per second against it on their own hardware. There you want 80+ bits, which means roughly 12–13 random full-set characters, or 16 if you'd like margin for the future.

The one exception: passphrases

One password can't live in a manager — the manager's own master password. That's where passphrases shine. Grab five random words from a 7,776-word list (Diceware style) and you've got ≈ 65 bits; six words, ≈ 78. "glacier-marble-trumpet-window-spoon" crushes most human passwords while actually being typeable. Your fingers will thank you.

Generating them properly

Not all randomness is equal. Math.random()-based generators are predictable in principle. Proper generators pull from the OS's cryptographic source. Our Password Generator uses crypto.getRandomValues() — the same CSPRNG your browser trusts for TLS — runs entirely on your device, and shows a live strength meter as you play with length and character sets.

• 16+ characters, all character sets, for anything touching money or identity
• One password per site. Reuse turns one breach into all the breaches.
• A 5–6 word passphrase as your manager's master password
• 2FA everywhere it's offered — it catches you when a password inevitably leaks

Stop trying to be clever

The whole discipline fits in a sentence: long, random, unique, managed. Let a generator make them, let a manager remember them, keep one good passphrase in your actual head. That's less work than the mental gymnastics of inventing "clever" passwords — and it's the only version that actually holds.