Password Strength Meter

Entropy + pattern analysis — nothing sent
🔒 Nothing you type ever leaves this device. There's no form, no AJAX, no backend — this is plain JavaScript evaluating your password locally.
—
score out of 100
—
Length
—
Entropy (bits)
—
Character pool
—
Fast attacker (10¹⁰/s)
—
Offline KDF (10⁵/s)
—
Common pattern hits

What makes a password actually strong

Length matters more than complexity. \"ilovepizza.4ever\" beats \"Tr0ub4dor&3\" at the same total length because the former isn't in any leak dictionary. Use a passphrase: 4+ random uncommon words from a password manager's generator.

Related tools

Why "Tr0ub4dor&3" fails

Crack times assume: fast attacker (10 billion guesses/sec, leaked-database crack with GPU rigs) vs slow attacker (100K guesses/sec with proper bcrypt/Argon2 — public-facing logins). Your real security depends on the server's KDF, not just password strength.

Frequently asked questions

Is checking my real password here safe?

Yes, technically — the JS never leaves your device. But good practice is: don't paste real passwords anywhere, even offline tools. Test patterns of your passwords instead. e.g. if your password is like "FluffyKitten2015!", test with "LongAnimal2016#".

What does entropy actually mean?

Bits of randomness. Each bit doubles crack time. log2(pool_size) × length gives theoretical maximum. Real passwords are usually lower because of patterns, dictionary words, and human predictability.

How is this different from zxcvbn?

zxcvbn is a more sophisticated library (~1MB JSON) that uses leaked-password datasets. This tool uses simpler pattern detection plus tighter common-password wordlist. Both are approximations. Aim for > 70 bits entropy by this meter OR > 4/5 in zxcvbn — both are reasonable thresholds.