Strong password generator (browser only)

Generate a strong, random password with optional upper case, digits, and symbols. Uses crypto.getRandomValues when available.

Result will appear here.

How to use this password

Save it in a password manager (Bitwarden, 1Password). Do not paste it into chat or email. Length matters more than characters — 16+ is recommended.

Why length beats complexity

A password's strength comes from its length times the number of possible characters. Going from 8 to 16 characters multiplies the search space far more than adding exotic symbols does. A random 16-character password mixing lower, upper, digits and symbols is beyond any realistic brute-force attack today, while "P@ssw0rd!" — symbols and all — falls in seconds because it follows a pattern attackers try first. Randomness and length are what matter; this tool provides both.

How random is this generator?

On modern browsers the tool uses crypto.getRandomValues, the browser's cryptographically secure random number generator — the same source used for HTTPS keys. If that API is unavailable, it falls back to Math.random and tells you so in the output. The generator never sends the password anywhere; it exists only in your browser tab.

Do's and don'ts

FAQ

Are generated passwords stored anywhere?

No. Generation happens in your browser; nothing is transmitted or saved. If you close the tab, the password is gone unless you copied it.

What length should I choose?

16 is a good default; 20+ for high-value accounts. Beyond that, usability in password managers matters more than extra characters.

Why can't I use only symbols or only digits?

You can — uncheck the other sets. But single-set passwords are weaker at the same length, so the tool requires at least one set to be selected.

People also use this for…

Every tool below is also 100%% local: no upload, no account, no server copy — the same privacy guarantee you get on this page.

How to generate a password

  1. Set the length. Sixteen characters is a good default; twenty or more for anything that protects money or identity.
  2. Tick the character sets you need: upper case, lower case, digits, symbols. Most sites require at least three of the four.
  3. Click Run and copy the result straight into your password manager — do not retype it, and do not paste it into a chat window.
  4. Generate a fresh one for every account. Reuse is the single biggest password risk, far bigger than any question of complexity.

Where the randomness comes from

The generator draws from crypto.getRandomValues, the browser's cryptographically secure random number generator, which is seeded from your operating system's entropy pool. That is categorically different from Math.random, which is a fast but predictable algorithm unsuitable for secrets. In practical terms: an attacker who watches a hundred passwords from this page still cannot predict the hundred-and-first. Generation happens entirely on your device — nothing is sent anywhere, nothing is logged, and there is no record of what was generated once you close the tab.

How strong is "strong"?

Password strength is measured in bits of entropy, roughly length × log2(character set size). A 12-character password from letters and digits is about 71 bits; 16 characters from all four sets is about 104 bits. Anything above roughly 80 bits is beyond brute-force reach with current hardware. Notice that length does more work than symbols: adding four characters buys far more security than swapping in punctuation. If a site rejects your symbols, generating a longer letters-and-digits password is not a downgrade.

Sensible rules around generated passwords

Troubleshooting

FAQ

Can I generate the same password again?

No, and that is by design. If a password could be regenerated from a seed you remember, so could anyone else's guess at that seed.

Is it safe to use on a work computer?

Yes — the password never touches the network, so nothing appears in proxy logs or browser history beyond the page visit itself.

Should I change passwords regularly?

Current guidance says no: change them when there is a breach or a reason to suspect one, not on a fixed calendar. Length and uniqueness matter far more.