How it works:
Generate cryptographically secure passwords with customizable length and character types. Perfect for creating unique passwords for every account.
Your Password:
Generate a strong, random password and adjust its length and character types to fit a site's rules. Passwords are created locally in your browser using its secure random generator — nothing is sent anywhere or saved.
Why password strength is really about entropy
A password's real strength is its entropy — how many equally-likely possibilities an attacker would have to try, measured in bits. Every additional random character multiplies the possibilities, so entropy grows with both the size of the character set and, more powerfully, the length.
This is the key insight: length beats complexity. A 16-character password drawn from the ~94 printable ASCII characters has roughly 104 bits of entropy — far beyond what any brute-force attack can reach. A short but "complex" password like P@ss1! has very little, because it's short and follows a guessable pattern.
When and why you'd use it
- New accounts — a unique, random password per site so one breach can't unlock the others.
- Rotating a leaked password — replace one that showed up in a breach.
- Keys and passphrases — API keys, Wi-Fi passwords, database credentials.
Worked examples
Frequently asked questions
Are the passwords stored or sent anywhere?
No. Each password is generated on your device using the browser's built-in cryptographic random generator. Nothing is transmitted, logged, or saved — close the tab and it's gone. That also means you must copy it somewhere safe before leaving.
Are they truly random?
They use the browser's cryptographically secure random source (crypto.getRandomValues) where available — suitable for real passwords, not a predictable Math.random().
How long should a password be?
16 characters or more for anything important. Since you won't memorize dozens of them, use a reputable password manager to store and autofill them.
Should I reuse a strong password across sites?
No. Reuse is the single biggest risk: one breached site exposes every account sharing that password. Use a unique one per site.