How long should a password be?
· 6 min read
Key takeaways
- For random passwords, each extra character multiplies the possibilities — length matters more than symbols.
- At 10 billion guesses per second, an 8-character random password falls in about 3½ days on average; 12 characters take about 750,000 years.
- NIST SP 800-63B-4 asks for at least 15 characters when a password is the only login factor; PCI DSS v4.0 requires 12.
- Use 20 random characters for passwords in a password manager and 7 random words for a password manager's master password.
Last reviewed
"Use a long password" is the most repeated piece of security advice, and for good reason. But how long is long enough? It depends on how the password was made and what an attacker can do with it.
The short answer
- Passwords a password manager fills in: 16 random characters or more. Our generator defaults to 20 because it costs you nothing.
- Any password that is the only thing protecting an account: at least 15 characters, the minimum NIST now asks services to require in that case.
- A passphrase you must remember: at least 6 random words, and 7 for a password manager master password.
All of this assumes the password is randomly generated. Length does little for a password a person made up, as explained below.
Why length matters so much
For a randomly generated password, every extra character multiplies the number of possibilities by the size of the character set. With all 94 printable ASCII characters, that's ×94 per character, or log2(94) ≈ 6.55 more bits of entropy each time.
Compare that with adding symbols to a letters-and-digits password: the set grows from 62 to 94 characters, which adds only about 0.6 bits per character. One extra character is worth roughly ten times more than enabling symbols.
How long it takes to guess, by length
Average time to guess a random password drawn from all 94 printable characters, for an attacker who has stolen a password database and can test guesses offline against a fast hash. On average, an attacker finds the password after searching half of all possibilities.
| Length | Entropy | 10 billion guesses/s | 1 trillion guesses/s |
|---|---|---|---|
| 8 | ≈ 52 bits | about 3½ days | about 51 minutes |
| 10 | ≈ 66 bits | about 85 years | about 312 days |
| 12 | ≈ 79 bits | about 750,000 years | about 7,500 years |
| 14 | ≈ 92 bits | ≈ 109 years | ≈ 107 years |
| 15 | ≈ 98 bits | ≈ 1011 years | ≈ 109 years |
| 16 | ≈ 105 bits | ≈ 1013 years | ≈ 1011 years |
| 20 | ≈ 131 bits | ≈ 1021 years | ≈ 1019 years |
10 billion guesses per second is a conservative figure: a single high-end gaming GPU exceeds it against fast hashes such as MD5. 1 trillion per second stands for a well-funded attacker with many GPUs. Sites that use a slow password hash such as bcrypt or Argon2, or that limit login attempts, are far slower to attack; the how passwords are cracked guide compares those scenarios. Try your own numbers in the entropy calculator.
Important: these figures only hold for randomly generated passwords. A 13-character password you invented — Football2026! — can fall in seconds, because attackers guess common patterns first.
Is 8, 12 or 16 characters enough?
Is 8 characters enough?
Not on its own. Even a random 8-character password falls in days, or under an hour on a large cluster, if the site stored it with a fast hash and the database leaks. NIST accepts 8 only when the password is one part of multi-factor authentication.
Is 12 characters enough?
For a random 12-character password, yes against today's attackers: about 79 bits, or thousands of years even for a large cluster. It meets PCI DSS v4.0's 12-character minimum but falls short of NIST's 15 for single-factor passwords, so some services will ask for more.
Is 16 characters enough?
Yes. A random 16-character password has about 105 bits, which no realistic hardware can search, however the site stores it. Going further, as our 20-character default does, is free insurance when a password manager does the typing.
Pick length for the worst case
A login form that limits attempts makes even short passwords hard to guess, so online attacks rarely decide the length you need. The worst case is an offline attack on a stolen database, and you can't see how a site hashes your password. Choose a length that survives a fast hash, and you don't have to trust the site to have done its part.
Passphrases: words, not characters
For a passphrase, the number of random words is what counts, not the number of letters. Each word picked from the 7,776-word EFF list adds log2(7,776) ≈ 12.9 bits, about as much as two random characters. EFF words average about 7 letters, so passphrases are much longer to type for the same strength:
| Random words | Entropy | As strong as | Typical length with hyphens |
|---|---|---|---|
| 4 | ≈ 51.7 bits | ≈ 8 random characters | about 31 characters |
| 5 | ≈ 64.6 bits | ≈ 10 random characters | about 39 characters |
| 6 | ≈ 77.5 bits | ≈ 12 random characters | about 47 characters |
| 7 | ≈ 90.5 bits | ≈ 14 random characters | about 55 characters |
| 8 | ≈ 103.4 bits | ≈ 16 random characters | about 63 characters |
"As strong as" compares entropy with random characters from the full 94-character set (about 6.55 bits each), rounded to the nearest character. The long typed length is the price of memorability, and the reason passphrases suit the few secrets you type yourself. See password vs passphrase for when to use each.
What the standards say
- NIST SP 800-63B-4 (2025) asks services to require at least 15 characters when a password is the only authentication factor, and at least 8 when it's combined with another factor. Services should accept at least 64 characters and must check the entire password rather than truncating it.
- PCI DSS v4.0 requires at least 12 characters (8 if a system can't support 12) for accounts in payment-card environments.
- OWASP calls passwords shorter than 15 characters weak when there is no second factor, says the maximum should be at least 64 characters to allow passphrases, and warns against silently truncating passwords.
Real services vary widely. The password requirements by platform guide lists the minimums and maximums of common systems.
Length caps and truncation
Some sites set a maximum length, and a few have quietly cut long passwords short. One common technical reason is bcrypt, a widely used password hash: the OWASP Password Storage Cheat Sheet notes that most bcrypt implementations accept at most 72 bytes of input, and tells sites to enforce a 72-byte maximum when they use it. Generated passwords use plain ASCII, so one character is one byte.
Caps also exist because some hashing implementations can be slowed to a crawl by extremely long inputs, which is why OWASP suggests a maximum rather than none, but one of at least 64 characters.
What this means for you:
- A 20-character random password fits well inside bcrypt's 72 bytes and NIST's 64-character floor.
- A long passphrase may not: 9 or 10 words with separators averages over 70 characters. On a site that caps or truncates, use a random password instead.
- If a site cuts your password short without saying so, only the part that is kept protects you. Turn on two-factor authentication there.
Recommended lengths
| Use | Recommendation |
|---|---|
| Passwords in a password manager | 20 random characters (our default) |
| Password manager master password | 7 random words |
| Computer / phone login you type often | 6 random words, or 15+ random characters |
| Wi-Fi network | 20–24 random characters (max 63) |
| Phone or card PIN (with lockout) | 6+ digits |
Do longer passwords ever hurt?
Not in strength. The costs are practical: a long password is slower to type by hand, and it may run into a site's cap. A password manager removes the first problem, and the second is solved by using the site's maximum.
When you can't go long
Some sites cap passwords at 12 or 16 characters. Use the maximum they allow, keep all character types on, and turn on two-factor authentication — the second factor matters more when the password can't carry the weight on its own.
Generate a strong password · Generate a passphrase · How to create a strong password
Sources
Keep reading
- Strong password examples (2026)What strong passwords and passphrases look like, why you should never reuse a published example, and fresh ones generated privately on your device right now.
- Diceware: make a passphrase with real diceHow to roll a Diceware passphrase with five dice and the EFF wordlist, how many words you need, how to avoid bias, and when a generator does the same job.
- How to create a strong password (2026 guide)What actually makes a password strong today: length, randomness, uniqueness, a password manager, and a second factor — with the reasoning behind each.
- Password vs passphrase: which should you use?Random passwords and random-word passphrases compared on strength, memorability, typing and site compatibility — and when to use each.