WordPress
Password generator and strength checker
Use this password generator to make strong random passwords or passphrases, see how long they would take to crack, and make the WordPress hash of a password when you need one.
- Exact entropy
- EFF passphrases
- WordPress 6.8 hashes
Free, no sign-up. It runs in your browser, so nothing you type is sent to this site.
Nothing you enter leaves your browser.
This tool runs in your browser and needs JavaScript. Turn JavaScript on and reload the page.
Password generator
Your passwords
Strength of each one
Check your own password
It is checked in this browser and never sent anywhere. The checker, zxcvbn, is downloaded the first time you type here. It looks for words, names, dates, keyboard patterns and swaps such as @ for a, and only the first 256 characters are checked.
WordPress password hash
The hash WordPress 6.8 and later store for a password, made here in your browser. You need it only to set a password straight in the database, for example when you are locked out and cannot use email or WP-CLI.
Type a password, or press Hash next to a generated one.
WordPress uses PHP’s default cost, which went from 10 to 12 in PHP 8.4. Either one works on any PHP version; if it differs from the server’s, WordPress quietly updates the hash the next time the user logs in.
What PHP’s password_hash() makes on its own. WordPress still accepts it, and other PHP software uses it, but plain bcrypt reads only the first 72 bytes of a password.
WordPress hash (WordPress 6.8 and later)
Plain bcrypt hash
Set it in the database
Password do’s and don’ts
This advice follows NIST SP 800-63B-4 (opens in a new tab), the United States government’s digital identity guidelines, published in July 2025.
Do
- Choose length over complexity. Every extra character multiplies the work for an attacker. NIST asks sites to require at least 15 characters when a password is the only thing protecting an account, and to accept at least 64.
- Use a passphrase for passwords you have to remember. Six random words are stronger than a short jumble and far easier to type. The words must be picked at random, not chosen by you.
- Use a different password for every site. When one site is breached, attackers try the same email and password everywhere else.
- Keep them in a password manager. It remembers and fills them for you, so each one can be long and random. You then need to remember one strong passphrase.
- Turn on two-factor sign-in or passkeys. An authenticator app, a security key or a passkey stops most account takeovers even when a password leaks. Passkeys also cannot be phished. WordPress supports two-factor sign-in through plugins.
- Change a password when it may have leaked, for example after a breach notice, and on every site where you used it.
Don’t
- Don’t reuse passwords, or make small changes to an old one such as Summer2025! to Summer2026!. Attackers try those changes first.
- Don’t use personal details such as names, birthdays, pets, teams or your site’s name. They are easy to find and are the first things tried.
- Don’t rely on swaps and patterns such as P@ssw0rd or qwerty123. Cracking tools know them all.
- Don’t change strong passwords on a schedule. NIST says sites should not force regular changes, because people then pick weaker, predictable ones. Change them when there is a reason.
- Don’t share passwords by email or chat, and don’t keep them in a plain text file. Use your password manager’s sharing feature instead.
- Don’t use security questions as a backup if you can avoid it. If a site insists, give a random answer and keep it in your password manager.
How strength is worked out
Generated passwords. The generator knows exactly how many passwords it could have made, so the strength is exact: the entropy in bits is log2 of that number. A 20-character password from all 94 characters has about 131 bits, and six words from 7,776 have about 77.5. With “at least one of each”, the passwords that miss a kind are not counted. The times assume an attacker who knows your settings and needs, on average, half of the possibilities. With the hyphen separator, four hyphenated words in the list (such as t-shirt) could in rare cases read as two words; that takes far less than a hundredth of a bit off the figure.
Your own password. Nobody can know how a person chose a password, so the checker estimates it. zxcvbn looks for the patterns attackers try first and counts the guesses they would need. A low score is a reliable warning; a high score is a good sign, not a guarantee.
The four times. Online with login limits assumes 100 guesses an hour, and online without limits 10 a second. A stolen database with a slow hash such as bcrypt, which WordPress uses, assumes 10,000 guesses a second, and with a fast hash such as MD5, 10 billion a second. These are rough figures. Real attackers, hardware and server settings can be much faster or slower, so read the times as a comparison, not a promise.
When to use the WordPress hash
WordPress never stores your password. It stores a hash: a one-way fingerprint that it can check a typed password against. A hash is not encryption: nobody can turn it back into the password, not even WordPress, and the same password gives a different hash every time because of the random salt.
WordPress 6.8 and later hash a password with bcrypt, after first running it through HMAC-SHA-384 so that passwords longer than bcrypt’s 72-byte limit keep all of their strength. These hashes start with $wp$2y$. Older hashes that start with $P$ (phpass) or plain bcrypt hashes that start with $2y$ still work, and WordPress updates them when the user next logs in.
Use the hash only when you cannot set the password the normal way. Try these first: the Lost your password link, Users in the dashboard, or WP-CLI with wp user reset-password your-username --show-password, which sets a new random password and shows it to you. To set a hash by hand, back up the database, then run the SQL above in phpMyAdmin, Adminer or the MySQL client. Change wp_ to your table prefix (it is in wp-config.php) and your-username to the login name. Log in to check it works. If the site uses a persistent object cache such as Redis, flush it too, or WordPress may keep using the old hash for a while.
Is this private?
Yes. Everything happens in your browser: the random numbers come from its secure random number generator, and the checker and the hash run on your device. Nothing you type or generate is sent to this site or anywhere else, nothing is saved in the browser, and no password is ever put in the page address. The fields are marked so browsers do not save or suggest what you type, and Reset clears everything. Copied passwords stay on your clipboard until you copy something else.
What you can do
-
Random passwords from 8 to 128 characters
-
Passphrases from the EFF large wordlist
-
Exact entropy and time-to-crack estimates
-
A zxcvbn check of a password you type
-
The WordPress 6.8 password hash and SQL to set it
-
Do’s and don’ts based on NIST SP 800-63B-4
How to make and use a strong password
-
Choose a password or a passphrase
Pick a random password for anything a password manager fills in, or a passphrase of random words for a password you have to type or remember. Set the length or the number of words.
-
Check the strength
The meter and the times show how strong each one is. Type your own password into the checker to see how an attacker would guess it and how to improve it.
-
Save it and turn on two-factor sign-in
Save the password in your password manager, use it on one site only, and turn on two-factor sign-in or a passkey where the site offers one.
Strong passwords without the guesswork
This free password generator draws every character or word with your browser’s secure random number generator, with no bias towards any choice. Because the generator knows how many passwords it could have made, it shows the exact entropy in bits. The checker for your own password uses zxcvbn, which estimates the guesses an attacker would need from the patterns people use.
Length beats complexity
NIST SP 800-63B-4 asks for at least 15 characters when a password is the only thing protecting an account. It says sites should not force a mix of character types or regular changes, and should let you paste from a password manager. A long random password or a six-word passphrase does more than any mix of symbols.
On a WordPress site, also refresh the login keys with the WordPress salt key generator after a security problem, and check your security headers with the HTTP header checker.
Frequently asked questions
Is this password generator safe to use?
Yes. Passwords are made in your browser with crypto.getRandomValues, the browser’s secure random number generator, and are never sent to this site or anywhere else. Nothing is saved, and Reset clears every field. Copied passwords stay on your clipboard until you copy something else.
How long should a password be?
Use at least 15 characters for a password that protects an account on its own, as NIST SP 800-63B-4 recommends, and 20 or more for accounts kept in a password manager. A passphrase of six random words is a good choice for a password you have to remember.
What does entropy in bits mean?
It measures how many passwords the generator could have made: each extra bit doubles the number. A 20-character password from all 94 keyboard characters has about 131 bits, and six words from the 7,776-word EFF list about 77.5 bits.
How accurate are the crack times?
They are estimates for comparison. Generated passwords use their exact entropy, and a typed password uses zxcvbn’s estimate of the guesses needed. The four speeds, from 100 guesses an hour to 10 billion a second, are typical figures; real attackers and servers vary a lot. A low result is a reliable warning, and a high one is a good sign, not a guarantee.
What is the WordPress password hash for?
WordPress stores a hash of each password, not the password itself. You need one only to set a password directly in the database, for example when you are locked out and cannot use the lost password link or WP-CLI. WordPress 6.8 and later hash with bcrypt after an HMAC-SHA-384 step, and these hashes start with $wp$2y$. A hash is not encryption and cannot be turned back into the password.
Does an older WordPress site accept the new hash?
No. Hashes that start with $wp need WordPress 6.8 or later. For an older site, tick the box for a plain bcrypt hash: older versions check it through PHP’s crypt(), and WordPress 6.8 and later accept it too and upgrade it the next time the user logs in.
Related tools
-
Salt keys
New (added recently)Generate new WordPress keys and salts for wp-config.php, with an optional WP_CACHE_KEY_SALT.
-
Generate a wp-config.php with database settings, new salt keys and explained options.
-
Build explained WP-CLI commands for installing and maintaining WordPress.
-
Check a URL’s HTTP response headers and redirect chain.