How this password generator works
Choose a length between 4 and 128 characters, tick the character groups you want, and the page builds the password in your browser with crypto.getRandomValues(), the cryptographically strong random source of the Web Crypto API. Each character is picked from the allowed pool with a fresh 32-bit random value, so the choice is uniform for practical purposes. The password appears in the box above and nowhere else: there is no form submission and no request to our server, which also means we cannot recover a password you did not save.
The function most tutorials reach for, Math.random(), is a pseudo-random generator whose output can be predicted from earlier values. MDN's reference says plainly not to use it for anything related to security. This page does not use it.
Two details worth knowing. The symbol group is the 26 characters !@#$%^&*()_+-=[]{}|;:,.<>?, so with all four groups ticked the pool holds 94 characters. If you untick every group, the page falls back to lowercase letters rather than producing nothing.
What the strength meter measures
The meter is an entropy estimate, not a crack-time prediction. It multiplies the length by log2 of the pool size and colors the bar by the result: Weak below 40 bits, Fair from 40, Strong from 60, Very Strong from 80. It assumes the password really was drawn at random. Judge a password you made up yourself by the same arithmetic and the answer is meaningless: "Password123!" scores like a random 12-character string, yet it sits in every attacker's wordlist.
Why letters and digits alone can rate Very Strong
Symbols add less than most people expect. Moving from 62 characters (letters and digits) to 94 adds about 0.6 bits per character; one extra character adds about 6. Twenty characters of letters and digits come to about 119 bits, comfortably Very Strong, which is handy when a site rejects symbols. If a site caps you at 8 characters, the meter says Fair even with every group ticked, and two-factor authentication matters more for that account than anything you can do with the password.
Password entropy in plain words
Entropy counts how many different passwords the generator could have produced, written as a power of two. A password with 40 bits of entropy is one of about a trillion equally likely possibilities, and every extra bit doubles that number. The formula this page uses is bits = length x log2(pool size): lowercase letters alone give about 4.7 bits per character, letters and digits about 5.95, and all four groups about 6.55. The table shows where common settings land.
| Length | Character groups | Pool | Entropy | Meter |
| 8 | All four | 94 | 52 bits | Fair |
| 12 | Lowercase only | 26 | 56 bits | Fair |
| 12 | All four | 94 | 79 bits | Strong |
| 16 | Letters and digits | 62 | 95 bits | Very Strong |
| 16 | All four | 94 | 105 bits | Very Strong |
| 20 | All four | 94 | 131 bits | Very Strong |
How long an attacker would need depends on things the meter cannot see: whether the site stores passwords with a slow, salted hash or a fast one, how many guesses per second the hardware manages, and whether the password was leaked in plain text somewhere. That is why this page reports bits rather than years. Developers who store passwords should follow the OWASP Password Storage Cheat Sheet; a plain digest such as the one from our MD5 hash tool is not suitable for the job, and encoding a password with the Base64 tool hides nothing, because anyone can reverse it.
How long should a password be? What NIST says
The United States federal guidance on passwords is NIST Special Publication 800-63B. Its current revision tells services to require at least 15 characters when the password is the only factor, at least 8 when a second factor is also used, and to accept at least 64 characters so that people can use passphrases. It also tells them not to impose composition rules such as "one uppercase, one symbol", not to force routine password changes, and to check new passwords against lists of known compromised ones. Length and unpredictability are what count; forced symbol rules add little and push people towards predictable patterns.
For a password you will keep in a manager rather than remember, length costs nothing: set the slider to 20 or more and take whatever the site accepts. Use a different password for every account, because stolen lists are routinely tried against other sites; keep them in a password manager such as Bitwarden, 1Password or KeePass; and turn on two-factor authentication wherever it is offered. If you need to hand a Wi-Fi key to a guest in the same room, the QR code generator turns the text into a code they can scan instead of retyping.