Security Basics
How Long Should a Password Be in 2026?
July 29, 2026 · 8 min read
If you could improve your password security by changing only one thing, make your passwords longer.
For years, websites pushed mixtures of uppercase, lowercase, numbers, and symbols. Those rules were well-intentioned, but modern guidance—including NIST SP 800-63B-4—puts length and randomness ahead of cosmetic complexity.
A longer, randomly generated password expands the search space for attackers. Even with powerful GPUs, a few extra random characters can turn hours of cracking work into centuries.
The Short Answer
For most people using a password manager, these defaults work well in 2026:
Recommended password lengths in 2026
| Account type | Recommended length |
|---|---|
| Everyday online accounts | 16–20 random characters |
| Banking, email, password manager | 20–24 random characters |
| Master password (memorised) | 5–7 random words (passphrase) |
| API keys, tokens, generated secrets | 32+ random characters |
If a password manager stores the secret for you, there is little downside to going longer than a site’s minimum. Generate the longest password the service accepts—within reason—and keep it unique. For API keys and similar secrets, our API key generator defaults to 32+ characters.
Why Length Matters More Than Complexity
Every additional random character multiplies the number of possible passwords. Security professionals call that the search space.
Many people assume swapping letters for symbols is enough: Password123! or P@ssw0rd!. Attackers have seen those patterns millions of times. Modern password-cracking tools try predictable substitutions automatically.
A genuinely random string such as rQ7vL2!mX8@dP4#z has no meaningful pattern to exploit. The strongest passwords are not clever—they are unpredictable.
Complexity Helps, But Randomness Wins
Composition rules (uppercase, lowercase, numbers, symbols) can widen the alphabet. They only help when the password is generated randomly.
Humans are poor random generators. Passwords that pass complexity checks often still follow familiar shapes: CompanyName2026!, Summer2026!, Liverpool#1, BlueCar99$. To cracking software, those are early candidates—not unique inventions.
That is the same conclusion as our guide to secure passwords in 2026: length, randomness, and uniqueness beat cosmetic tricks.
Online Attacks vs Offline Attacks
Required length also depends on the attack model.
Online attacks hit the login page. Rate limits, CAPTCHAs, lockouts, and MFA slow attackers down. A reasonably strong unique password is hard to brute-force through the front door.
Offline attacks are far more dangerous. After a breach, attackers can test billions of guesses against stolen password hashes with GPUs. Here, length becomes critical: every extra random character multiplies the work. Try our crack-time simulator to see how length changes estimated offline cracking time.
How Much Difference Does One Character Make?
Suppose each character can be one of about 90 printable symbols. Adding one random character multiplies the search space by roughly 90—not a small bump.
Four extra random characters multiply possibilities by about 90⁴, or more than 65 million times. That exponential growth is why longer beats clever substitutions—and why password strength checks reward length so heavily.
Should You Use a Passphrase Instead?
Sometimes. Random character strings are ideal when a password manager remembers them.
When you must type a secret yourself—master password, disk encryption, device login, recovery credentials—a passphrase of several unrelated random words is usually better.
For example: planet museum bicycle velvet coffee orange. That is easier to remember than Q8!wL9#xTp3@Jv2% while still providing strong security when the words are chosen randomly, not invented as a sentence or lyric.
Aim for 5–7 random words, matching our broader 2026 guidance. You can generate one locally with our passphrase generator, or build one with Diceware / our manual roller if you prefer transparent dice rolls.
Does Every Website Support Long Passwords?
No. Many modern services accept 64 characters or more, but legacy systems still cap at 16, 20, or 32 characters. Those limits are usually software history, not security features.
Use the longest password the service accepts. If a site truncates silently or rejects long secrets, prefer a unique random password at the maximum length it allows, and enable MFA.
What About Passkeys?
Where passkeys are available, prefer them. They resist phishing, do not rely on typed secrets, and use public-key cryptography.
Passwords are not disappearing overnight. Millions of sites and internal systems will keep using them. Knowing how long a strong password should be remains essential.
Practical Recommendations
- Use a password manager for everyday logins.
- Generate 16–20 random characters for ordinary accounts.
- Use 20–24 random characters for email, banking, and other high-value accounts.
- Never reuse passwords.
- Enable multi-factor authentication whenever possible.
- Use a randomly generated passphrase (5–7 words) for secrets you must remember.
- Prefer passkeys when a service supports them.
- Change a password after compromise or reuse—check for leaks when you are unsure—not on a fixed calendar schedule.
Frequently Asked Questions
Is a 12-character password still secure?
A randomly generated 12-character password is much stronger than most human-made passwords. With a manager, 16–20 characters costs almost nothing and gives a larger margin against offline cracking.
Is a 20-character password overkill?
Not if a manager stores it. Moving from 12 to 20 characters barely changes usability and substantially increases resistance to offline attacks—especially for email and banking.
Should I change my passwords regularly?
Routine rotation is outdated. Change passwords when there is a reason: reuse, a breach, phishing, malware, sharing, or a notice from the service.
Which is more important: length or symbols?
If both passwords are random, symbols can widen the alphabet. In practice, adding length usually helps more than packing clever substitutions into a short password.
What does NIST say about length?
NIST SP 800-63B-4 requires at least 15 characters for centrally verified single-factor passwords and discourages mandatory composition rules. MFA-only passwords may be shorter (floor of 8), but that is a minimum for systems with another factor—not a target for manager-generated secrets. See also our 2026 password security guide.
The Bottom Line
The strongest passwords are not the ones that look complicated—they are the ones with the most randomness.
For nearly every online account in 2026, a 16–20 character randomly generated password in a password manager is an excellent default. Use 20–24 for high-value accounts. For secrets you must remember, choose a random passphrase instead of inventing something clever.
The goal is not a password that looks secure. It is one an attacker cannot realistically guess.
Related reading
- What Makes a Password Secure in 2026?
- Diceware Explained: Origins, Security, and How to Roll Your Own Passphrase
- Passkeys: The Next Frontier in Passwordless Authentication
- Where Password Randomness Comes From
- Password Reuse: Why Even One Repeat Can Compromise Everything
- How Hackers Crack Your Passwords (and How to Stop Them)
Generate a longer password
Create a long, random password or passphrase locally in your browser with passwords.lu—nothing is sent to a server.