How Strong Is Your Password? Entropy Explained Without the Math Degree
Password strength as bits of entropy: length vs character variety, why dictionary words beat complex short strings, and a realistic cracking-time table.
Password advice is full of folklore. The measurable truth is one number: entropy in bits. Understanding it explains why a short symbol-studded password can lose to four random words — and why length quietly dominates.
Entropy: the count of possibilities
Each character drawn randomly from N options adds log2(N) bits. Lowercase letters add about 4.7 bits per character, full printable sets about 6.5. A 16-character random password from the full set carries roughly 100 bits — beyond any brute force budget on Earth.
Length beats complexity
A 20-character lowercase password (~95 bits) beats an 8-character symbol-laden one (~52 bits). Adding patterns adds nothing when the guesser knows the pattern; only randomness adds entropy.
Crack-time reality check
| Password | Entropy | Offline crack (GPU rig) |
|---|---|---|
| 8 chars, lowercase | ~37 bits | seconds |
| 8 chars, full set | ~52 bits | weeks |
| 16 chars, full set | ~103 bits | centuries+ |
| 4 random words | ~50 bits | months |
For anything real, generate 16-24 characters with the Password Generator — it uses the browser cryptographic RNG and never transmits results.
Why reuse is the bigger risk
Most account takeovers come from leaked password databases elsewhere, not brute force. A unique high-entropy password per site caps the blast radius; pair it with hashing hygiene — a system that hashes passwords with plain SHA-256 instead of a slow KDF is doing it wrong, as the hash guide explains.
Related guides
How to Decode a JWT: Reading Header, Payload and Signature
Decode any JWT by hand or with a browser tool: how the three parts are encoded, which claims matter (sub, exp, iss, aud) and why decoding is not verification.
Read guide →2026-10-07UUID v4 and v7: The Complete Guide for Databases and APIs
What a UUID actually encodes, v4 vs v7 trade-offs for database indexes, how unique is truly unique, and why UUIDs are not secrets.
Read guide →2026-10-05SHA-256 for Developers: Checksums, HMAC and What Hashing Cannot Do
When to use SHA-256 (and when not to), how HMAC adds a secret, why password hashing needs bcrypt or Argon2 instead, and how to verify checksums quickly.
Read guide →Try these tools
Password Generator
Generate cryptographically strong passwords with adjustable length and character sets, ambiguous-character filter and entropy readout. Five candidates at a time, 100% offline.
Open tool →SHA-256 Generator
Compute the SHA-256 digest of any text instantly — with SHA-1, SHA-384 and SHA-512 alongside. Uses WebCrypto when available, with a pure-JS fallback. Includes HMAC demo mode.
Open tool →