Strong Random Passwords: Length, Entropy and Real Numbers
Short answer: a strong random password is long, not complicated. For a password a manager stores for you, make it long and truly random. Length matters more than adding symbols, and every extra bit of entropy doubles the guesses an attacker needs. A 16-character random password with all four character types is about 103 bits, and a 20-character one about 129. Generate one in the Password Generator, which picks every character with your browser's secure random number generator and sends nothing anywhere.
What entropy measures
Entropy, in bits, is how many guesses an attacker faces if they know exactly how the password was made. For a random password it is the length multiplied by the bits each character contributes, and that depends on the size of the character pool. Every extra bit doubles the number of guesses.
The generator shows an estimate under each password. As a rough guide from the tool: around 60 bits is fair for low-risk accounts, and 80 bits or more is very strong.
Real figures for typical settings
| Settings | Pool size | Approx. entropy | Rating |
|---|---|---|---|
| 12 characters, lowercase only | 26 | about 56 bits | fair |
| 12 characters, upper and lower case and digits | 62 | about 71 bits | strong |
| 16 characters, all four types | full set | about 103 bits | very strong |
| 20 characters, all four types | full set | about 129 bits | very strong |
Look at what changes the number. Going from lowercase-only to mixed case and digits adds about 15 bits. Adding four more characters adds more than that, and doing both is better still. So a long random password beats a short "complex" one.
Random password or passphrase?
- For anything a password manager stores: use a random password like the ones made here. You never need to remember it.
- For the few you must remember (your manager's master password, a device login): a passphrase of several unrelated words is easier to type and recall. Do not use a phrase from a song, a quote or your own life, and do not reuse it anywhere else.
Current NIST guidance on digital identity (SP 800-63B) points in the same direction as the numbers above: it sets minimum lengths and says systems should not impose composition rules like "one capital, one symbol", while requiring checks against lists of common and breached passwords. If a site forces odd rules on you, the generator lets you choose which character types appear.
How the generator keeps passwords unbiased
Every character type you select appears at least once, and the remaining characters are drawn uniformly from the whole pool using rejection sampling. That avoids a subtle flaw of naive code (taking a random number modulo the pool size), where some characters come up slightly more often than others.
Two practical options:
- Avoid look-alikes removes characters that are easy to confuse when read aloud or typed by hand:
0 O o 1 l I |. The pool gets a little smaller, so add a character or two. - The symbol set is limited to
!@#$%^&*()-_=+[]{};:,.?/because some sites reject quotes and backslashes.
Habits that matter more than the generator
- A different password for every account, kept in a password manager.
- Turn on two-factor authentication where you can.
- Never reuse a password after a breach notice.
- If a password was pasted somewhere it should not have been (a chat, a ticket, a repository), change it. For code and config files, see Leaked API key: what to do.
How to generate a strong random password with the Password Generator
- Open the Password Generator.
- Choose the length and the character types.
- Tick Avoid look-alikes only if you will type the password by hand.
- Read the entropy estimate and the rating. Aim for 80 bits or more for anything important.
- Copy the password straight into your password manager.
Limits to know
- The entropy figure assumes the password is truly random. A password you invent yourself, or a quote with some letters changed, is far weaker than its length suggests.
- The estimate says nothing about a site that stores passwords badly (a plain fast hash is a poor choice, as the hash comparison guide explains). That is the site's job, not yours.
- Nothing is stored, sent or logged. The password exists only on your device.
Frequently asked questions
How long should a password be? For random passwords kept in a manager, 16 characters or more. The longer, the better.
Is length or complexity more important? Length. Four extra characters add more entropy than switching from lowercase to mixed case.
What is password entropy? A measure in bits of how many guesses it would take. Each extra bit doubles it.
Is the generated password really random? It uses your browser's secure random number generator with rejection sampling, so no character is more likely than another.
Why are some symbols missing? Some sites reject quotes and backslashes, so the symbol set is limited.
Related tools and guides
- QR code error correction, size and capacity for sharing a Wi-Fi password as a QR code
- Hash Generator: never store passwords with a plain hash (see MD5 vs SHA-256 vs SHA-3 vs BLAKE2)
- UUID Generator: an identifier is not a secret (see UUID v4 vs v7 vs ULID)
- Secret Scanner
- QR Code Generator