Password security guide
This guide explains practical habits that reduce risk for most people. It complements the CryptoPass generator and our technical overview on How it works.
Start with the real problem: reuse and theft
Most account takeovers do not happen because someone "guessed" a 16-character password. They happen because the same password was reused across sites, leaked in a breach, phished, or stored somewhere unsafe. A password generator helps with randomness and length, but your overall posture still depends on storage, recovery options, and how you respond when a breach is announced.
Prefer a password manager
Humans are bad at memorizing dozens of unique, high-entropy strings. Password managers reduce reuse by generating and filling unique passwords per site. Choose a reputable manager, protect the vault with a strong master password or passkey where supported, and keep backups of your recovery key in a safe place.
If you are not ready for a manager, a written list in a physically secure location can be better than reusing the same short password everywhere—but it does not scale well and is harder to keep current.
Length usually beats "clever" rules
Long passwords drawn from a large alphabet (letters, digits, symbols) generally resist guessing and offline cracking better than short passwords with substitutions like "P@ssw0rd!". Modern guidance from standards bodies emphasizes length and unpredictability over gimmicks.
Passphrases—sequences of random words—can be strong if they are truly random and long enough. A famous approach is Diceware-style selection. Avoid famous quotes, song lyrics, or predictable patterns; attackers try those early.
Understand entropy without overfitting
Entropy is a way to describe how unpredictable a password is relative to an attacker's model. If you generate passwords using a cryptographically secure random source, each additional bit of entropy roughly doubles the work for an idealized attacker under that model. Real attackers are messier: they use dictionaries, breach lists, and site-specific policies. Treat entropy as a helpful guideline, not a guarantee.
Two-factor authentication (2FA) is a safety net
Even strong passwords can be phished or leaked. A second factor—an authenticator app, hardware security key, or passkey—reduces the damage from many real-world attacks. Where available, prefer phishing-resistant options (passkeys and security keys) over SMS when the threat model matters.
Recovery matters as much as the password
Attackers reset accounts through email, SMS recovery, and weak security questions. Use a strong email password (or passkey), lock down recovery phone numbers, and remove unused recovery methods. If you use a manager, understand what happens if you lose access to the vault.
Safe habits when generating passwords in a browser
- Generate secrets only on devices you trust.
- Be cautious with browser extensions that can read page content or clipboard history.
- Clear clipboard after copying if your OS does not do it automatically.
- Avoid generating highly sensitive secrets on shared computers.
When random strings are the wrong tool
Some systems need API keys, signing keys, or encryption keys with specific formats. Use the right tool for the job (for example, platform key management) rather than stretching a general password generator beyond its intended use.
What this site does not promise
CryptoPass aims to follow good practices for client-side randomness, but no web app can promise perfect security against every adversary. Your browser, operating system, malware, and physical access all matter. If you need enterprise-grade controls, work with qualified security professionals.