Text & Data

How Strong Is My Password? Entropy, Length, and Passphrases

How strong your password is depends on one thing: how many guesses an attacker would need to find it. If a computer or dice chose your password at random, you can work that out exactly. The formula is length × log2(alphabet size), and the result is measured in bits of entropy. If you made the password up yourself, it is almost certainly weaker than that formula suggests, because attackers guess the way people think.

In practice, a long random password or a random passphrase of six or more words is strong, especially when it's stored in a password manager and backed by multi-factor authentication. A short password stuffed with symbols to pass a website's rules usually is not.

This guide shows the math with worked examples. It includes an entropy table you can compare your own setup against, and it explains what current NIST guidance says about password rules.

How strong is my password? It depends on how it was made

Two passwords can look equally messy and still differ hugely in strength. kX9#vQ2m from a random generator and P@ssw0rd both have 8 characters with mixed case, digits, and a symbol. The first is one of about 6 quadrillion equally likely options. The second is a well-known entry in leaked-password lists and is among the first things guessing tools try.

You can't judge strength by looking at the characters. It comes from the process that produced them. So the first question is not "does it have a symbol?" but "how many other passwords could this process have produced, and were they all equally likely?"

  • Randomly generated: you can calculate strength exactly with the entropy formula below.
  • Human-chosen: you can only estimate it. Real attacks on human-chosen passwords succeed far faster than the formula predicts.

Password entropy: the formula for random passwords

Entropy, in this context, measures how unpredictable something is. Each bit doubles the number of possibilities, so a password with n bits of entropy is one of 2^n equally likely options.

For a password where every character is picked independently and uniformly at random:

Entropy (bits) = L × log2(N)

Here L is the length and N is the number of possible characters (the alphabet size). The values of log2(N) for common alphabets:

  • Digits only (10): log2(10) ≈ 3.32 bits per character
  • Lowercase letters (26): ≈ 4.70 bits
  • Lowercase + digits (36): ≈ 5.17 bits
  • Upper + lowercase + digits (62): ≈ 5.95 bits
  • All 94 printable ASCII characters except the space: ≈ 6.55 bits

Worked example 1: an 8-character "complex" password

  1. Alphabet: all 94 printable ASCII characters, so log2(94) ≈ 6.555.
  2. Length: 8.
  3. Entropy: 8 × 6.555 ≈ 52.4 bits.
  4. Possibilities: 94^8 ≈ 6.1 × 10^15.

Worked example 2: a 12-character lowercase password

  1. Alphabet: 26 letters, log2(26) ≈ 4.700.
  2. Length: 12.
  3. Entropy: 12 × 4.700 ≈ 56.4 bits.
  4. Possibilities: 26^12 ≈ 9.5 × 10^16, about 16 times more than example 1.

The all-lowercase password wins, as long as both were generated randomly.

Turning bits into guessing time

Guessing time depends on the attacker's speed. That speed ranges from a handful of guesses per minute against a login page with rate limiting, to enormous rates against a stolen database protected by a weak hash (a scrambled, one-way stored form of the password). To get a feel for the numbers, take a hypothetical 10 billion (10^10) guesses per second in an offline attack:

  • 52.4 bits: 6.1 × 10^15 ÷ 10^10 ≈ 610,000 seconds, about 7 days to try everything (3.5 days on average)
  • 56.4 bits: 9.5 × 10^16 ÷ 10^10 ≈ 9.5 million seconds, about 110 days (about 55 days on average)
  • 95.3 bits (16 random characters from 62): 4.8 × 10^28 ÷ 10^10 ≈ 4.8 × 10^18 seconds, roughly 150 billion years (half that on average)

The exact rate matters less than how fast the numbers grow. Each extra bit doubles the work.

Password entropy table

Bits of entropy for passwords generated uniformly at random. Values are rounded to one decimal place.

Length Digits (10) Lowercase (26) Letters + digits (62) All printable ASCII (94)
8 26.6 37.6 47.6 52.4
12 39.9 56.4 71.5 78.7
16 53.2 75.2 95.3 104.9
20 66.4 94.0 119.1 131.1

As a rough rule of thumb, 70–80 random bits is comfortably strong for an online account. For passwords a manager stores, going longer costs nothing, so there is no reason to stop there. More importantly, every figure in this table assumes true randomness. If a person picked the characters, the table does not apply.

Why length beats complexity rules

Compare the table's rows and columns. Switching a 12-character password from lowercase to all 94 characters adds about 1.85 bits per character (6.55 − 4.70), or about 22 bits in total (56.4 → 78.7). That is a real gain, and it applies to every character. But it has a ceiling.

Length grows strength without limit. The character set can only grow so far: the full keyboard tops out at about 6.55 bits per character. Adding characters is usually the easier and bigger win. For example, 16 lowercase characters (75.2 bits) come close to 12 full-ASCII characters (78.7), and 20 lowercase characters (94.0 bits) pass them easily.

Complexity rules also backfire with humans. "Must contain an uppercase letter, a digit, and a symbol" pushes people toward predictable fixes: capitalize the first letter, put a digit and ! at the end. Attackers build those patterns into their guessing rules, so the extra characters add almost nothing.

What current NIST guidance says

NIST Special Publication 800-63B, the US government's digital identity guideline, has moved firmly in this direction. In general terms, the current revision of SP 800-63B tells services to:

  • Require a minimum length (currently 15 characters when a password is the only factor, 8 when it is combined with MFA) and support passwords of at least 64 characters, instead of composition rules such as "one symbol, one digit."
  • Not force periodic password changes on a schedule, but require a change when there is evidence of compromise.
  • Check new passwords against lists of commonly used, expected, or previously breached passwords.
  • Accept spaces and a wide range of characters, and support password managers and pasting.
  • Drop password hints and security questions.

These are rules for the organizations that run login systems. Individual websites may still enforce older policies, and requirements vary by service, so you will sometimes have to satisfy a symbol rule anyway. If you do, add the symbol to a long random password, not to a short memorable one.

Random passphrases: diceware-style entropy

A passphrase is a password made of several words, such as cloak-ripen-saddle-orbit-gravy-motel. It is easy to type and remember. You can calculate its strength exactly, but only if the words were chosen at random from a known list.

Diceware is the classic method. The list has 7,776 words, one for every result of rolling five six-sided dice (6^5 = 7,776). Each word adds log2(7,776) ≈ 12.92 bits.

How to make a diceware passphrase

  1. Get a diceware-style word list with 7,776 entries. Each entry is labeled with a five-digit number made of the digits 1–6.
  2. Roll five dice (or one die five times) and write down the digits in order, for example 4-2-6-1-3.
  3. Look up 42613 in the list and write down that word.
  4. Repeat until you have the number of words you want.
  5. Keep the words in the order rolled. Do not swap one for a word you like better, because that brings back human bias.
  6. Join them with spaces or hyphens if the site allows.
Words Calculation Entropy
4 4 × 12.92 51.7 bits
5 5 × 12.92 64.6 bits
6 6 × 12.92 77.5 bits
7 7 × 12.92 90.5 bits

Six words give about 77.5 bits, roughly the same as a 12-character random password from all 94 printable characters (78.7 bits). At the hypothetical 10 billion guesses per second, 7,776^6 ≈ 2.2 × 10^23 possibilities would take about 2.2 × 10^13 seconds, or around 700,000 years, to exhaust.

These numbers assume the attacker knows your word list and the number of words. Diceware's security never depends on keeping the method secret. It comes only from the random rolls. A phrase you invent yourself, like a song lyric or words you picked because they felt random, does not get these numbers.

Physical dice are the most transparent source of randomness. Software generators are fine if they use a cryptographically secure random source. The article on how random number generators work explains why that distinction matters.

Why human-chosen passwords are weaker than the formula suggests

The entropy formula assumes every possible password is equally likely. Human choices are nothing like that. Attackers don't try aaaaaaaa, aaaaaaab, and so on. They start with what people actually use:

  • Breached-password lists. Huge numbers of real passwords have leaked over the years, and the most common ones are tried first.
  • Dictionaries and names. Words, pets, sports teams, places, and years.
  • Mangling rules. Capitalize the first letter, add digits or ! at the end, swap a→@, o→0, s→$.
  • Keyboard patterns. qwerty, 1qaz2wsx, and similar walks.

Take Summer2024!. By the formula it is 11 characters from 94, about 72 bits. In reality it is a season, a year, and an exclamation mark: a pattern that guessing tools try early. Its real strength is a tiny fraction of 72 bits.

Strength meters try to account for this by spotting patterns, which is why two meters can disagree about the same password. Their output is an estimate. Also avoid typing a real password you use into a website that offers to "check" it. Test the method, not the actual secret.

The second weakness is reuse. If you use the same password on two sites and one of them is breached, attackers can simply try that email and password elsewhere. This is called credential stuffing. Entropy doesn't help here at all. Only unique passwords do.

Password managers and multi-factor authentication

Nobody can remember dozens of unique random passwords, and you don't need to. A password manager generates, stores, and fills them for you. That leaves you two things to get right.

The master password

This is the one password you must remember, so make it a random passphrase of six or more words. Write it down and keep it somewhere physically safe until you know it by heart. Every other password can be long and random, for example 16–20 characters from the full 94-character set (about 105–131 bits). For one-off needs, the free password generator creates random passwords with symbols and shows how strong each generated password is.

Multi-factor authentication (MFA)

MFA means a login requires something besides the password, such as a code from an authenticator app or a tap on a hardware security key. It protects you when a password leaks anyway, through phishing, malware, or a breach at the service.

Second factor Strengths Weaknesses
SMS text code Easy, widely available Can be phished; exposed to SIM-swap attacks
Authenticator app code Works offline; not tied to your phone number Codes can still be phished on fake sites
Hardware security key Resistant to phishing because it checks the real site Needs setup and a backup method

Any MFA is better than none. Turn it on first for email, because email resets everything else, then for banking and your password manager. Which methods are available depends on the service.

Where passkeys fit

A passkey uses a cryptographic key pair; the private key stays on your device or is synced through your password manager or platform account, and you sign in with it instead of typing a password. Like a security key, it is tied to the real site, so it resists phishing. But if the account still accepts a password as a fallback, that password still needs to be strong and unique, or removed if the service allows it.

Quick reference: password strength checklist

  • Generated, not invented. Only randomly generated passwords and passphrases match the entropy math.
  • Formula: bits = length × log2(alphabet size). Lowercase ≈ 4.70, letters + digits ≈ 5.95, full ASCII ≈ 6.55, diceware word ≈ 12.92.
  • Targets: 16+ random characters for stored passwords; 6+ diceware words for anything you must remember.
  • Length first. A few extra characters can beat adding symbols: 17 random lowercase letters (79.9 bits) edge past 12 random characters from the full set (78.7 bits), and length is easier to add.
  • Unique everywhere. One account per password, kept in a password manager.
  • MFA on email first, then finance and the password manager itself. Prefer passkeys or security keys where offered.
  • Change a password when there's a reason, such as a breach notice or suspected phishing, not on a calendar.
  • Never test a real password in an unknown online checker.

Frequently Asked Questions

Is a 12-character password strong enough?

If it was randomly generated from upper and lowercase letters plus digits, 12 characters give about 71.5 bits, which is strong for most online accounts. If you made it up yourself, its real strength could be far lower, because attackers try common words and patterns first. For passwords stored in a manager, there is little cost to going to 16 or 20 characters.

Are spaces allowed in passwords and passphrases?

Many services accept spaces, and current NIST guidance encourages services to allow them. Some older systems still reject or trim them. If a site refuses spaces, join your passphrase words with hyphens or another separator. The separator adds no meaningful entropy either way.

Does replacing letters with numbers or symbols make a password stronger?

Barely. Swaps like a to @ or o to 0 are standard rules in password-guessing tools, so P@ssw0rd is guessed almost as fast as password. Adding more random characters or another random word does far more.

How often should I change my passwords?

Current NIST guidance advises against forced changes on a fixed schedule. Change a password when there is a reason: the service reports a breach, you entered it on a suspicious site, or you shared it. Your employer or a specific service may still have its own policy, so follow it where it applies.

Is a passkey better than a strong password?

For most people, yes, where a service supports it. There is no secret for you to reuse, forget, or type into a fake login page, and the key only works with the real site. Support, syncing, and recovery options vary by service and operating system, so keep a backup sign-in method set up before you rely on it.