Create strong, random, secure passwords — generated privately in your browser.
Strength comes from entropy — the number of possibilities an attacker must search. Entropy depends on how long the password is and how large the character set it was drawn from, and length matters far more than complexity.
Adding one character to a password multiplies the search space by the size of the character set. Adding symbols only increases the per-character value from about 5.95 bits to 6.55.
| Password | Entropy | Search space |
|---|---|---|
| 8 chars, all types | 52 bits | 4.5 x 10^15 |
| 12 chars, lowercase only | 56 bits | 9.5 x 10^16 |
| 12 chars, all types | 79 bits | 4.8 x 10^23 |
| 16 chars, all types | 105 bits | 3.7 x 10^31 |
| 20 chars, lowercase only | 94 bits | 2.0 x 10^28 |
Notice that a 20-character all-lowercase password is far stronger than a 12-character one using every symbol on the keyboard. This is why modern guidance — including NIST's — favours long passphrases over short strings of punctuation, and explicitly discourages mandatory complexity rules, which push people toward predictable substitutions like P@ssw0rd!.
A practical baseline is 16 random characters for important accounts and 12 as an absolute minimum. Where a passphrase is easier to handle, four to six random words drawn from a large dictionary provide comparable strength — but the words must be chosen randomly, not by you, since human-chosen words cluster heavily.
Brute force is rarely how accounts are compromised. The realistic threats are:
Summer2026! falls almost instantly despite meeting most complexity requirements.Generating strong passwords is only useful if you can have a different one everywhere, which nobody can do from memory. A password manager stores them, fills them in, and — importantly — will not autofill on a lookalike phishing domain, which makes it a defence against phishing as well as a convenience.
The pattern that works: one long, memorable passphrase for the manager itself, random generated passwords for everything else, and two-factor authentication on the accounts that matter. An app-based authenticator or a hardware key is meaningfully stronger than SMS, which is vulnerable to SIM swapping.
These passwords are generated locally using crypto.getRandomValues(), the browser's cryptographically secure random source. Nothing is transmitted, logged or stored — you can verify this in your browser's Network tab. This distinction matters: a generator that produced passwords on a server would mean your password had travelled across a network and existed in someone else's memory before you ever used it.
Generators built on Math.random() are not suitable for passwords. That function is fast but predictable, and its output can be reconstructed from a handful of observed values.
Length, by a wide margin. A 20-character lowercase password has more entropy than a 12-character one using every symbol available. This is why NIST now recommends long passphrases and discourages mandatory complexity rules.
Sixteen random characters for important accounts, twelve as a minimum. If you prefer a passphrase, four to six randomly chosen words give comparable strength — but the words must be picked randomly, not by you.
Not on a schedule. Forced rotation makes people choose weaker, predictable variations. Current guidance is to use a long unique password per site and change it only when you have reason to believe it has been exposed.
No. They are generated in your browser using crypto.getRandomValues(), a cryptographically secure source. Nothing is transmitted or stored, which you can confirm in your developer tools Network tab.
Yes, if the words are randomly selected from a large list and there are enough of them. Six random words from a 7,776-word list give about 77 bits. A phrase you invented yourself is far weaker, because human word choice is highly predictable.