The quick answer
Use at least 16 characters for important accounts and never fewer than 12 anywhere. For anything you must memorize, use a passphrase of 5–7 random words instead — length without the pain. Every additional random character multiplies an attacker's work; complexity rules barely do.
These numbers assume the password is randomly generated or built from random words. A human-invented 20-character password can still be weak — length necessary, but not sufficient, if the content is predictable.
Recommended length by account type
| Account | Minimum | Recommended | Why |
|---|---|---|---|
| Primary email | 16 | 20+ / 6-word passphrase | Resets everything else you own |
| Password manager master | — | 6–7-word passphrase | The one secret that guards all others |
| Banking / payments | 16 | 20+ random | Directly tied to money |
| Work / admin / cloud infra | 16 | 20+ random + hardware key | Targeted attacks happen here |
| Social media & shopping | 12 | 16 random | High breach frequency |
| Wi-Fi password | 16 | 20 random | Offline cracking of captured handshakes |
| Forgettable forum signup | 12 | 16 random (manager) | Reuse — not weakness — is the danger |
If this sounds exhausting, it is — which is why a password manager does the remembering, and our generator does the inventing.
Why length beats complexity
Entropy (a password's guess-resistance in bits) grows multiplicatively with length and only additively with character-set size: one extra random mixed-character adds ~6.6 bits, while forcing a symbol into an 8-character password adds ~2 bits total and typically just produces Password1!. Full math with worked tables: How Password Entropy Works.
Online vs offline attacks change the math
- Online guessing (through a login form) is throttled to a few attempts per second — even ~40 bits survives for years, and 2FA closes the door.
- Offline cracking (attacker stole the database) runs up to ~10¹¹ guesses per second against fast hashes. This is the scenario length defends against — and the one our checker estimates for.
How to actually handle long passwords
- Memorize one long passphrase (your manager's master password).
- Let the manager generate 16–24-character random passwords everywhere else.
- Use the passphrase generator for anything you type often, like Wi-Fi.
- Add 2FA so a single password failure is never fatal.
Frequently asked questions
Is an 8-character password still okay?
No. An 8-character password using every character type has ~52 bits of entropy if perfectly random — crackable offline in hours to days — and human-chosen 8-character passwords are far weaker. Treat 12 as the floor and 16 as the standard.
Is a 20-character password overkill?
For randomly generated passwords it's free — a manager types it for you — and it pushes entropy past ~130 bits, into "physically infeasible" territory for any offline attack. Overkill in the best way.
Does adding a symbol matter more than adding two characters?
No. Two extra random characters from a mixed pool (~+13 bits) beat the first symbol's pool expansion (~+0.6 bits per character). Symbols help, but length helps more.
How long should my Wi-Fi password be?
At least 16 random characters. WPA2 handshakes can be captured near your home and cracked offline at full GPU speed, so Wi-Fi needs the same treatment as an important account.
What if a site limits me to 12 characters?
Use all 12, make them fully random with every character type, make that password unique, and turn on the strongest 2FA the site offers. Also consider telling the site their limit is a security smell.
Apply what you learned with our zero-telemetry tools and references:
Put it into practice: run your next password through the local checker — it never leaves your browser.