Length beats complexity
A 20-character lowercase password has more entropy than an 8-character password mixing every character class. Each added character multiplies the search space; adding a symbol class only adds a small constant factor. If a system allows long passwords, length is the cheapest security win.
| Length | Lowercase only | Full ASCII set | Realistic strength |
|---|---|---|---|
| 8 | ~38 bits | ~52 bits | Weak by modern standards |
| 12 | ~56 bits | ~79 bits | Acceptable minimum |
| 16 | ~75 bits | ~105 bits | Strong |
| 20 | ~94 bits | ~131 bits | Very strong |
| 32 | ~150 bits | ~210 bits | Overkill for most uses |
Entropy is length × log2(alphabet size). A 62-character alphabet gives about 5.95 bits per character; 95 printable ASCII characters give about 6.57.
Character sets and ambiguity
Excluding 0, O, l, 1 and I reduces the alphabet slightly but avoids transcription errors when a password is read aloud or typed from a screen. For passwords stored and pasted digitally, the exclusion is unnecessary.
- Lowercase: 26 characters, about 4.7 bits each.
- Uppercase: 26 characters.
- Digits: 10 characters, about 3.3 bits each.
- Symbols: roughly 30 characters depending on the set.
- Requiring one of each class does not add much entropy and can reduce it if the generator becomes predictable.
What makes a password generator trustworthy
The random source must be a CSPRNG. Math.random is predictable enough that an attacker who observes a few outputs can reconstruct the internal state. This tool uses the Web Crypto API, and generation happens locally — nothing is sent to a server.
For passwords you will actually rely on, prefer a password manager's generator and storage. A browser tool cannot protect a password you paste into a weak system.
Passphrases vs passwords
Four to six random words can be easier to remember and strong enough for human-managed accounts. The tradeoff is length and typing effort. For machine-to-machine secrets, a long random string is better; nobody has to type it.