How strong is strong enough?
Password strength is measured in bits of entropy: each extra bit doubles the number of guesses needed. For a random password, it’s the length × log2(number of possible characters). Crack times below assume an offline attack at 100 billion guesses a second.
| Password | Entropy | Time to crack |
|---|---|---|
| 8 characters, all sets | 52 bits | 5 hours |
| 12 characters, letters and digits | 71 bits | 5 centuries |
| 16 characters, all sets | 103 bits | longer than the age of the universe |
| 20 characters, all sets | 129 bits | longer than the age of the universe |
| 4 random words | 41 bits | 14 seconds |
| 6 random words | 62 bits | 274 days |
Length beats complexity. Adding characters adds far more strength than adding symbol types, and long passwords are easier to type than short, complicated ones.
Checking a password you already use
Entropy formulas only work for random passwords. Human-made passwords follow patterns, and attackers try those patterns first. The checker looks for them and marks each one in the password:
- Common passwords from breach lists, like
password1orqwerty. - Dictionary words, including ones with symbols swapped in (
p@ssw0rd). Those swaps are the first thing cracking tools try. - Years and dates, like birthdays.
- Keyboard runs and sequences like
qwerty,asdfand1234. - Repeats like
aaaorabcabc.
Each pattern counts as only a few guesses, so the realistic strength is shown alongside, with crack times for both an offline attack and a rate-limited online one. The check runs in your browser and the password isn’t stored or sent anywhere.
Options explained
- No look-alikes removes characters that are easy to confuse, like
l,1,I,Oand0. Useful when a password will be read aloud or typed from paper. It costs a little entropy, which the meter accounts for. - Passphrase separators, capitals and a number help meet site rules. They add little strength; adding a word adds more.
- Bulk generates a list at once, for seeding test accounts or setting up devices.
Generating passwords in code
# macOS / Linux: 24 random characters
openssl rand -base64 18
# Python
import secrets; secrets.token_urlsafe(18)
// Node.js
crypto.randomBytes(18).toString('base64url')Never use Math.random() or Python’s random module for passwords; they’re predictable. Need a random ID rather than a secret? Use the UUID generator. Hashing passwords? See the hash generator notes on why plain hashes aren’t enough.
Questions people ask
How long should a password be?
Is a passphrase as secure as a random password?
Are these passwords generated securely?
crypto.getRandomValues, the browser’s cryptographically secure random source, with no bias towards any character. Nothing is sent over the network or stored.