Password Generator

Generate strong random passwords locally in your browser — length and character controls, with a live strength meter.

Click "Generate" to create a password
Strength —
16
4 16 32 48 64
16
Characters
—
Bits of Entropy
—
Character Set Size
—
Crack Time (est.)
≡ Table of Contents
  1. How This Password Generator Works
  2. The Entropy Math: Why Length Wins
  3. What Actually Gets Passwords Cracked
  4. Storing Them: The Manager Question
  5. The Bottom Line
  6. Frequently Asked Questions

How This Password Generator Works

Choose a length and which character sets to include — lowercase, uppercase, digits, symbols — and the generator assembles a random password using your browser's cryptographic random source. Everything happens locally on your device: no password is generated on, sent to, or seen by any server.

The strength meter estimates cracking resistance from length and character variety — and the honest summary of password security is: length beats cleverness.

The Entropy Math: Why Length Wins

Password strength is measured in bits of entropy:

Entropy = length × log₂(pool size)

Pool sizes: lowercase 26 → +26 upper = 52 → +10 digits = 62 → +symbols ≈ 90. What that means against a modern offline attack (~10¹¹ guesses/second):

PasswordEntropyCrack time (order of magnitude)
8 chars, lowercase38 bitsseconds
8 chars, all sets52 bitshours
12 chars, all sets78 bitscenturies
16 chars, all sets104 bitsheat death of the universe territory
20 chars, lowercase only94 bitsmillions of years

Note the last row: 20 plain lowercase letters beat 8 characters of everything. Each added character multiplies difficulty by the whole pool size — length compounds, complexity only adds.

What Actually Gets Passwords Cracked

Attackers don't iterate a–z blindly — they run dictionaries of leaked passwords, common substitutions (P@ssw0rd fools no software), keyboard walks (qwerty123), and personal data (names, birthdays, pets). Which yields the real rules:

  1. Random beats memorable-pattern — that's the entire value of a generator.
  2. Unique per site — reuse converts one breach into access everywhere ("credential stuffing"). This is the #1 practical risk.
  3. 12+ characters minimum, 16+ for anything important.
  4. No personal data, ever — it's the first thing tried.

Storing Them: The Manager Question

Random unique passwords are unmemorizable by design — the system only works with a password manager:

  • One strong master passphrase protects an encrypted vault of everything else.
  • Managers autofill only on matching domains — quietly defeating look-alike phishing sites.
  • Browser-integrated managers are fine for most people; dedicated ones add cross-device features.

For the master passphrase itself, a diceware-style phrase (4–6 random words: "copper-mango-drizzle-vault") delivers high entropy while staying typeable and memorable.

Then enable two-factor authentication on email, banking, and anything critical — it converts a stolen password from a disaster into a nuisance. Your email account matters most of all: it's the reset key to everything else.

The Bottom Line

The recipe is boring and bulletproof: generate 16+ random characters per site, store them in a manager behind one strong passphrase, add 2FA on the accounts that matter. The generator above handles step one locally and instantly — the other two are this week's best security errand.

Frequently Asked Questions

No — generation uses your browser's crypto API entirely on-device. Nothing is transmitted, logged, or stored.

12 characters minimum; 16+ for email, banking, and anything important. Length is the strongest single factor.

They help, but length helps more — 20 lowercase letters out-secure 8 mixed characters. Use both when a site allows.

Crackers try leaked lists, substitutions and patterns first — human "clever" is machine "predictable." Randomness has no pattern to exploit.

You're not — a password manager remembers them behind one strong master passphrase. That's the intended workflow.

4–6 truly random words (diceware style) — high entropy, typeable, memorable. Avoid quotes, lyrics, or personal facts.

Modern browser managers are encrypted and fine for most users — vastly better than reuse. Dedicated managers add sharing and audit features.

On evidence of breach, not on a calendar — forced rotation breeds weak patterns. Unique + long + 2FA beats scheduled changes.

Trying passwords leaked from one site on every other site — why reuse is the top practical risk and uniqueness the top defense.