Guide
Password Entropy Explained: How It's Actually Calculated
Every strength meter shows a number in bits. Here's exactly what that number means and how it's produced.
By Buğra SözeriPublished
Every password strength meter — including the one on our password generator — reports a number in bits: “71 bits,” “104 bits.” That number is entropy, and it isn’t a vibe or a marketing score. It comes from one formula, applied consistently, and once you know the formula you can predict exactly how any change to length or character set moves the number.
The formula
Password entropy in bits is:
entropy = length × log2(charset size)
Each character drawn independently and uniformly at random from a charset of size k contributes log2(k) bits, because log2(k) is exactly the number of yes/no questions needed on average to pin down one character out of k possibilities. String together n such characters and the bits simply add, giving n × log2(k). This is the same definition of entropy used across information theory, not a password-specific invention.
Worked examples
Here’s the formula applied to the character sets a typical generator offers:
| Charset | Size (k) | Bits per char | 12 chars | 16 chars |
|---|---|---|---|---|
| Lowercase only | 26 | 4.70 | 56 bits | 75 bits |
| Lower + upper | 52 | 5.70 | 68 bits | 91 bits |
| Lower + upper + digits | 62 | 5.95 | 71 bits | 95 bits |
| Lower + upper + digits + symbols | ~94 | 6.55 | 79 bits | 105 bits |
Two patterns fall out of this table. First, length dominates: going from 12 to 16 characters on the full charset adds 26 bits, while adding symbols to a 12-character alphanumeric password only adds about 8 bits. Second, the marginal value of a bigger charset shrinks — going from 62 to 94 possible characters buys 0.6 more bits per character, far less than the 1.25-bit jump from adding uppercase to lowercase-only. This is exactly why length-first advice, including our own guidance on picking a strong password, is the current consensus rather than complexity rules.
What entropy does and doesn’t measure
The formula assumes every character is drawn independently and uniformly at random — which is true for a generator using a cryptographic random source, and false for almost every password a human types from memory. Humans lean on dictionary words, keyboard patterns, and predictable substitutions, all of which an attacker’s cracking dictionary already accounts for. A password that “looks” high-entropy by naive character counting — say, P@ssw0rd123!— is trivially guessed in practice, because it isn’t actually a random draw from the full charset; it’s a well-known pattern with a few substitutions layered on. Entropy math only applies cleanly to passwords that are genuinely random, which is the whole argument for generating rather than composing them.
How much entropy is enough
NIST SP 800-63B , the federal digital-identity standard, doesn’t prescribe a bit target directly — it instead sets a minimum length (8 characters for user-chosen secrets, longer strongly encouraged) and pushes verifiers to screen against known- breached password lists rather than force arbitrary complexity rules. In practice, security teams commonly treat roughly 80 bits as the threshold where offline brute-force becomes infeasible for the foreseeable future, and 100+ bits as comfortably future-proof. Looking at the table above, that means 14+ random alphanumeric-plus-symbol characters, or a random 16-character password on any reasonable charset.
Frequently asked questions
- What is password entropy?
- It's a measure, in bits, of how many equally-likely passwords a given set of rules (character classes and length) could produce. It's calculated as length × log2(charset size). Higher entropy means more possible passwords, which means more guesses needed to find yours by brute force.
- How many bits of entropy is "secure"?
- There's no single magic number, but a common practical target for a randomly-generated password stored in a password manager is 80+ bits — enough that brute-forcing it is infeasible with any realistic hardware budget. NIST SP 800-63B focuses more on length (8+ characters minimum, longer preferred) than on hitting a specific bit count, since length is the dominant factor in the formula.
- Does adding symbols really help that much?
- It helps, but less than people expect, because it multiplies the charset rather than the length. Going from lowercase-only (26 characters) to lowercase+uppercase+digits+symbols (about 94 characters) roughly doubles the bits per character — from about 4.7 to about 6.55. Adding four more characters of length does more for total entropy than adding an entire character class.
- Is a high-entropy password guaranteed to be safe?
- No. Entropy only measures resistance to brute-force guessing against a uniformly random password. It says nothing about reuse across sites, phishing, credential-stuffing from a breached database, or a keylogger on your machine. A 100-bit random password reused on twenty sites is only as safe as the weakest of those twenty.
Sources & references
Authoritative references cited by this piece. Verified by Buğra Sözeri on the dates shown and re-checked at every deploy.
- NIST SP 800-63B — Digital Identity Guidelines (Authentication and Lifecycle Management) — Federal guidance on memorized-secret length, composition, and the entropy reasoning behind current password recommendations(as of )
- OWASP — Password Storage and Generation Cheat Sheet — Industry-reference guidance on password entropy targets and generation practices(as of )
- CISA — Secure Our World: Use Strong Passwords — US government consumer guidance on password length and strength(as of )
Related
More guides on this topic
- Negative Unix Timestamps: Dates Before 1970 ExplainedUnix time can go negative — it just counts backward from the epoch. Why some parsers reject negative timestamps, and how to convert one to a date correctly.
- Passphrase vs Random Password: Which Is Actually Stronger?Comparing the entropy of word-based passphrases against generated random strings, where each one wins, and which fits which login you actually own.
- How to Make a QR Code Menu for Your Restaurant TableA QR menu is a link to a web page, not a PDF trapped behind a code. How to build one that loads fast, updates instantly, and actually gets scanned at the table.
- Reading Timestamps in Log Files and JSON API ResponsesLog lines and JSON payloads rarely say which timestamp format they use. How to spot seconds vs. milliseconds at a glance and batch-convert a whole column.
Published September 25, 2026