Password Generator for creating strong, cryptographically secure passwords and memorable passphrases. Adjustable length, character sets, entropy meter, crack-time estimate, and bulk generation. Uses the Web Crypto API. Nothing is uploaded, logged, or stored. Free, private, no signup.
- Passwords are generated locally in your browser using the Web Crypto API (
crypto.getRandomValues). Nothing is transmitted, logged, or stored. - Because nothing is stored, you must save each password yourself. Refreshing the page will clear the output.
- We recommend storing generated passwords in a dedicated password manager (Bitwarden, 1Password, KeePassXC), not in a browser's built-in store or a text file.
- Enable two-factor authentication (2FA) on every account that offers it. A strong password alone is not enough if the service is breached.
- Never reuse a password across multiple sites. If one service is breached, every account with the same password is at risk.
- Your preferences (length, character sets, options) are remembered locally so you do not have to reconfigure each visit. No password or history is ever written to storage.
Generate a password to see it appear here.
x7K!pQ2#mW9@vR4$. It is strong but hard to remember and hard to type on a phone.A passphrase is a longer sequence of random words, for example
correct-horse-battery-staple-42. Each word contributes about 8 to 13 bits of entropy, so a 6-word passphrase is typically stronger than an 8-character password while being easier to remember and easier to type.Use a passphrase when you need to memorise a password (for example, for your password manager's master password). Use a random password for everything else, stored in the manager.
Below 40 bits is weak. Crackable in minutes with consumer hardware.
40 to 60 bits is fair. Crackable in hours to weeks.
60 to 80 bits is good. Beyond the reach of casual attackers.
80 to 100 bits is strong. Requires nation-state resources.
100+ bits is very strong. Practically unbreakable with current technology.
This tool calculates entropy from the actual character set and length, or from the number of words for passphrases.
Online attack assumes 1,000 guesses per second. Real-world online attacks are usually much slower, due to rate limiting.
Offline fast hash assumes 1010 guesses per second. This models an attacker who has stolen a database of SHA-1 or MD5 password hashes and is using a dedicated GPU rig.
Offline bcrypt assumes 105 guesses per second. This models the same scenario against a database hashed with bcrypt at cost factor 12, the modern recommended practice.
Bitwarden is open source, free tier available, cloud or self-hosted.
KeePassXC is fully offline, open source, no cloud.
1Password is commercial with excellent UX and family plans.
Proton Pass is open source and included with Proton accounts.
Avoid browser-only password stores (Chrome, Edge, Safari) for your primary vault. They are convenient but less portable, less audited, and harder to back up. Avoid text files, sticky notes, and email drafts entirely.
haveibeenpwned.com. If it has, change the affected passwords immediately, especially on any account that shares the password with a financial, email, or identity service.
Tip: press ⌘/Ctrl + Enter to generate from the Password or Passphrase panel.
A 20-character password is now the practical floor
The old advice was 8 characters with mixed case, digits, and symbols. That advice is out of date.
NIST SP 800-63B recommends a minimum of 8 characters but encourages longer ones. Modern security guidance pushes toward 16 or 20. Length beats complexity every time.
This generator defaults to 20 characters. The slider goes to 128.
Length beats complexity. Here is why.
An 8-character password with all four character sets gives you roughly 52 bits of entropy. A 16-character password with only lowercase letters gives you 75 bits.
The second one is stronger. It is also easier to type on a phone.
Attackers do not try every possible string. They try common patterns, dictionary words, and known substitutions. A long random string with no pattern defeats all of those tactics at once.
Passwords vs passphrases
A password is a short, random string like x7K!pQ2#mW9@vR4$. It is strong. It is also hard to remember and awkward to type.
A passphrase is a longer sequence of random words like correct-horse-battery-staple-42. Each word adds 8 to 13 bits of entropy. Six words from a 400-word list carry about 52 bits.
Use a passphrase for anything you need to memorise. Your password manager's master password is the obvious example.
Use a random password for everything else. Store it in the manager.
Entropy tells you the real strength
Entropy is measured in bits. It is the base-2 logarithm of the number of possible passwords.
Below 40 bits is weak. Consumer hardware cracks it in minutes.
40 to 60 bits is fair. Hours to weeks of cracking time.
60 to 80 bits is good. Beyond the reach of casual attackers.
80 to 100 bits is strong. Requires nation-state resources.
100+ bits is very strong. Practically unbreakable with current technology.
The entropy meter updates on every generation. You see the exact bit count for your settings.
Crack-time estimates at three attack speeds
A single crack-time number is meaningless without knowing how fast the attacker is. This tool shows three scenarios side by side.
Online attack assumes 1,000 guesses per second. That models a remote attacker trying to log in through a web form. Rate limiting makes real attacks much slower.
Offline fast hash assumes 10 billion guesses per second. That models an attacker who has stolen a database of SHA-1 or MD5 hashes and is using a GPU rig.
Offline bcrypt assumes 100,000 guesses per second. That models the same attacker against a properly hashed database. bcrypt at cost factor 12 slows them down by 100,000 times.
The same 12-character password can show "5 minutes" under offline fast hash and "8 months" under bcrypt. The hashing on the server side matters as much as your password.
Bulk generation and CSV export
Need to set up 25 accounts in one go? Generate 50 passwords at once. The batch view shows all of them with individual copy buttons.
Switch the output format to CSV and you get a site,username,password file. That imports directly into Bitwarden, 1Password, and most other password managers.
Every password in a batch is checked for duplicates. A collision would be astronomically unlikely, but the check runs anyway.
Rejection sampling avoids a subtle bug
Many password generators use a naive method to map random bytes to characters. That method introduces modulo bias. Certain characters become slightly more likely than others.
The bias is small. It is also real, and it reduces the effective entropy of every password.
This tool uses rejection sampling. It discards random values that would introduce bias and redraws until it gets an unbiased one. The result is a genuinely uniform distribution.
What this tool does not do
It does not store, sync, or remember your passwords. It is a generator, not a manager.
It does not integrate with any external service. Nothing leaves your browser.
Session history is in-memory only. Refreshing the page clears it. Nothing is written to localStorage, cookies, or disk.
Your preferences (length, character sets, options) are saved locally so you do not have to reconfigure every visit. No password or history entry is ever saved.
Store passwords correctly
Use a dedicated password manager. Bitwarden, 1Password, KeePassXC, and Proton Pass are the standard choices.
Avoid browser-only password stores for your primary vault. They work, but they are harder to back up and less portable across devices.
Avoid text files, sticky notes, and email drafts. Those are the first places attackers look.
Enable 2FA on every account that offers it. Prefer app-based codes or hardware keys over SMS. SMS is vulnerable to SIM-swapping.
Privacy and speed
Every password is generated with crypto.getRandomValues from the Web Crypto API. Randomness comes from your operating system's cryptographically secure source.
No uploads. No accounts. No ads inside the tool.
Generate as many passwords as you want. Nothing is transmitted. Reloading the page clears everything.
Frequently Asked Questions
Are the passwords generated by this tool secure?
crypto.getRandomValues), which sources randomness from the operating system's cryptographically secure random number generator. It applies rejection sampling to avoid modulo bias, a subtle statistical flaw that makes some naive generators slightly predictable. Nothing is transmitted, logged, or stored anywhere. Passwords exist only in the current browser tab's memory.