How to Create a Strong Password That Holds Up
What makes a password strong in 2026: NIST length rules, why forced resets are out, how passphrases and password managers work, and how to estimate entropy.
Short answer
A strong password is long, random, and used for one account only. Aim for 15 or more characters or a passphrase of five to six random words, and let a password manager generate and store it.
Key takeaways
- NIST SP 800-63B-4 sets a 15-character minimum for passwords used on their own and tells sites to stop forcing composition rules and scheduled resets.
- Randomness matters more than symbols: five words picked at random from a 7,776-word list give about 65 bits of entropy.
- A password manager makes unique passwords practical, and reuse is the habit that turns one breach into many.
Most password advice you grew up with (swap letters for symbols, add a capital, change it every three months) has been dropped by the people who write the federal standard. The current rules are simpler and easier to live with: make it long, make it random, never reuse it. This guide shows how to do that and how to check the math yourself.
What does NIST say makes a strong password?
NIST now treats length and uniqueness as the main measures of password strength, and it tells websites to stop forcing complexity rules and scheduled resets.
The relevant document is NIST Special Publication 800-63B-4, finalized in July 2025. It is written for organizations that run login systems, but its requirements show what good practice looks like for everyone. The key points:
- A password used as the only factor must be at least 15 characters. One used alongside a second factor can be as short as 8.
- Sites should allow at least 64 characters and accept spaces and Unicode.
- Sites shall not impose composition rules, such as "one uppercase, one number, one symbol."
- Sites shall not require periodic changes, but must force a change if there is evidence of compromise.
- New passwords are checked against a blocklist of common, expected, or already-breached passwords.
- Password managers, autofill, and pasting should be allowed.
Composition rules were dropped because people respond to them predictably. "Password1!" satisfies every old checkbox and sits near the top of every attacker's guess list. Forced rotation produced the same pattern: "Summer2025!" became "Autumn2025!".
How do you measure password strength?
For a randomly generated password, strength in bits equals the length multiplied by log2 of the number of possible characters.
This number is called entropy. Each extra bit doubles the number of guesses an attacker needs to try every option. The formula is:
bits = length x log2(character set size)
| Password type | Character set | Length | Approximate entropy |
|---|---|---|---|
| Lowercase letters only | 26 | 12 | 56 bits |
| Upper, lower, digits | 62 | 12 | 71 bits |
| All printable ASCII | 94 | 12 | 79 bits |
| All printable ASCII | 94 | 16 | 105 bits |
| Random words, 7,776-word list | 7,776 | 5 words | 65 bits |
| Random words, 7,776-word list | 7,776 | 6 words | 78 bits |
Here is the worked example for the 16-character row. log2(94) is about 6.55, and 16 x 6.55 is about 104.9, so roughly 105 bits. That is 2^105 possible passwords, a number large enough that brute force is not a realistic attack.
The catch: this math only holds when a computer or dice did the choosing. A 16-character password you invented ("MyDogRex2019!!ab") has far less real entropy, because attackers model the way humans build passwords. Our password strength checker estimates entropy and guessing time in your browser without sending anything over the network, which makes it a good way to see the gap.
Are passphrases better than complex passwords?
A passphrase of five or six randomly chosen words is as strong as a shorter jumble of symbols and much easier to type and remember.
Diceware-style lists contain 7,776 words, one for every combination of five dice rolls. Each randomly chosen word adds about 12.9 bits (log2 of 7,776). Five words land near 65 bits, six near 78. A phrase like "orbit candle mossy tractor jigsaw plume" is long enough to clear NIST's 15-character minimum many times over and is something you can type on a phone keyboard without hunting for symbols.
Two rules keep a passphrase honest:
- Let randomness pick the words. Song lyrics, quotes, and "correct horse battery staple" are in cracking dictionaries.
- Do not trim it to fit a short limit. If a site caps passwords below 15 characters, use a random character password from your manager there instead.
Passphrases work best for the handful of secrets you must actually remember: your password manager's master password, your computer login, and possibly your phone backup.
How should you store and manage passwords?
Use a password manager to generate a unique random password for every account, and remember only one strong passphrase that opens it.
Reuse is the bigger risk for most people. When one site leaks its login database, attackers try the same email and password on banks, email providers, and shopping sites. This is called credential stuffing, and a unique password per site makes it useless.
Password managers built into browsers and operating systems, as well as standalone apps, can all generate random passwords, fill them only on the matching website, and warn you about reused or breached entries. Practical setup steps:
- Pick one manager and import any passwords saved in your browsers.
- Create a master passphrase of six random words.
- Turn on two-factor authentication for the manager account. See two-factor authentication methods compared for which method to choose.
- Change your email password first, since email resets everything else, then work through banking and shopping accounts.
When should you change a password?
Change a password when you have a reason to think it was exposed, not on a calendar schedule.
Good reasons include a breach notice from the service, a warning from your password manager that the password appears in a known leak, a sign-in alert you did not trigger, or having typed it into a page you later realized was fake. If that last one happened, read how to spot a phishing email so it does not happen twice.
For accounts that offer it, the longer-term fix is to stop relying on passwords at all. Passkeys use public-key cryptography, cannot be phished the way a typed password can, and are already supported by major platforms; passkeys explained covers how they work. Until every site supports them, a long, random, unique password stored in a manager is the setup that holds up.
Frequently asked questions
How long should a password be in 2026?
NIST's current guidance (SP 800-63B-4, published July 2025) requires at least 15 characters when a password is the only factor and at least 8 when it is part of multi-factor authentication. Sites should accept at least 64 characters, so longer is fine.
Do I need to change my passwords every 90 days?
No. NIST says verifiers shall not require periodic password changes. You should change a password when there is evidence it was exposed, such as a breach notice or a login you do not recognize.
Is a passphrase really as strong as a random password?
It can be, if the words are chosen at random rather than picked by you. Six random words from a 7,776-word list give about 77 bits, comparable to a 12-character password drawn from all printable keyboard characters.
Are password managers safe to use?
For most people they are far safer than reusing passwords or keeping them in a notes file. Protect the manager with a long master passphrase and turn on two-factor authentication or a passkey for the account.
Sources
- NIST SP 800-63B-4: Authentication and Authenticator Management
- NIST CSRC: SP 800-63B-4 publication page
Research-based: Technorat does not claim hands-on testing. See how we research. Spotted an error? contact@technorat.com