Password generator
Made on your device. Never sent or stored.
Strong, random passwords made on your device. Pick a length, choose the characters, copy. Nothing leaves your browser.
How this generator works
Each character is chosen with crypto.getRandomValues, the cryptographically secure random number generator built into your browser. It draws from the same operating system source used for encryption keys, so the output cannot be predicted from earlier output.
A common mistake in password generators is taking a random number modulo the size of the character pool. That makes the first few characters slightly more likely than the rest. This generator uses rejection sampling instead: a random value that would introduce that bias is thrown away and drawn again, so every character in the pool has exactly the same chance.
When "at least one of each type" is on, one character from each chosen type is placed first, the rest are filled from the whole pool, and the result is shuffled with the same secure generator. That satisfies sites with composition rules and costs a fraction of a bit of entropy.
What the strength figure means
Entropy, in bits, measures how many guesses a password could take. A password of length L drawn at random from a pool of N characters has L times log2(N) bits. Every extra bit doubles the work. Because this site generates the password itself, it knows the exact pool and length, so the figure is exact rather than a guess.
The time shown assumes the worst common case: a stolen database of fast, unsalted hashes attacked offline at 10 billion guesses a second on graphics cards. Against a site that stores passwords with a slow hash such as bcrypt or Argon2, or that limits login attempts, the same password lasts far longer.
How long should a password be?
Length matters more than anything else. NIST SP 800-63B-4, the United States federal guideline published on 31 July 2025, requires at least 15 characters when a password is the only factor, and at least 8 when it is combined with another factor. It also tells sites to stop forcing mixtures of character types and to stop forcing periodic changes. This site defaults to 16.
| Length | Letters and digits | With symbols |
|---|---|---|
| 8 characters | 3 hours | 2 days |
| 10 characters | 1 year | 39 years |
| 12 characters | 5,112 years | 297,918 years |
| 14 characters | 20 million years | 2 billion years |
| 15 characters | 1 billion years | 196 billion years |
| 16 characters | 76 billion years | 17 trillion years |
| 20 characters | 1 quintillion years | 978 quintillion years |
| 24 characters | over 1025 years | over 1028 years |
| 32 characters | over 1039 years | over 1044 years |
Read how long a password should be for the reasoning, or the full summary of the 2025 NIST password rules.
Tools on this site
Questions
Is it safe to generate a password on a website?
It is safe when the password is made on your device and never sent anywhere, which is how this site works. You can confirm it: open your browser developer tools, watch the Network tab while you generate, and you will see no requests. You can also load the page, disconnect from the internet, and it keeps working.
Do you store or log the passwords?
No. There is no account, no database and no analytics script. Your chosen settings, such as length, are remembered in your own browser storage so the page opens the way you left it. The passwords themselves are never stored.
Are symbols required for a strong password?
No. Length adds more strength than symbols do. A 16 character password of letters and digits has about 95 bits of entropy; adding symbols raises that to about 103. NIST no longer recommends forcing symbols. Use them when a site requires them, or when the length is capped.
Should I change my passwords regularly?
Not on a schedule. NIST SP 800-63B-4 says sites shall not require periodic changes, because forced changes push people toward predictable patterns. Change a password when there is a sign it was exposed, such as a breach notice.
How do I remember a random password?
You do not need to. Store it in a password manager and remember one strong passphrase to unlock the manager.
Sources
- NIST SP 800-63B-4, Digital Identity Guidelines: Authentication and Authenticator Management (final, 31 July 2025), National Institute of Standards and Technology. Checked 18 October 2026.
- SP 800-63B-4, section 3.1.1.2: Password Verifiers, National Institute of Standards and Technology. Checked 18 October 2026.
- Crypto: getRandomValues() method, MDN Web Docs. Checked 18 October 2026.