How to Create a Strong Password
- Go long before going complex - length matters more than almost anything else. A 16-character password beats a 8-character one even with fewer symbol tricks.
- Mix character types - uppercase, lowercase, numbers, and symbols each add more possible guesses an attacker has to try per character.
- Never reuse passwords - a password leaked from one breached site gets tried everywhere else instantly by attackers. Use a unique password per account.
- Avoid personal information - names, birthdays, and pet names are among the first things attackers guess.
- Use a password manager - it's the only realistic way to use a unique, high-entropy password for every account without memorizing them all.
Random Passwords vs. Passphrases
A random character password (like the default mode above) packs the most entropy per character, which is ideal when a password manager will remember it for you and you'll never type it by hand. A passphrase - several random, unrelated words strung together - is easier to remember and type correctly on a phone keyboard, at the cost of needing more words to reach the same entropy as a shorter random password.
Frequently Asked Questions
Is it safe to generate a password on a website?
It's safe here because everything runs entirely inside your own browser using JavaScript's cryptographically secure random number generator. The password is never transmitted anywhere, never logged, and never stored on any server.
What is password entropy?
Entropy measures how unpredictable a password is, in bits. Each extra bit doubles the number of guesses an attacker would need before finding the password by brute force. It depends on both length and how varied the characters are.
Should I use a random password or a passphrase?
Both are valid. Random characters pack more entropy per character for password managers; passphrases are easier for a human to remember and type, at the cost of needing more words for the same entropy.
How accurate is the estimated crack time?
It's a rough, honestly-labeled estimate, not a guarantee. It assumes an attacker already has a fast, unsalted password hash and is guessing at the rate stated next to the estimate. Real-world defenses like salting and slow hashing can make actual cracking far slower.