Random passwords · UUID · random numbers

Generated with your browser cryptographic random source (crypto.getRandomValues). Nothing is uploaded and nothing is recorded.

Password generator

Waiting for input

UUID v4

A 128-bit identifier, suitable for database keys and request tracing.
—

Random integers

Distinct random integers within a range.
Results appear here.

What makes a password strong

Password strength is essentially entropy — how many guesses an attacker would need. Entropy grows much faster with length than with character variety: adding two random characters typically multiplies the search space more than forcing a symbol does. That is why length is the first thing to increase.

The single biggest real-world risk is not a short password but a reused one. Credential stuffing attacks replay passwords leaked from one service against others, so a strong password that you use twice is weaker than a modest one used once. A password manager removes the trade-off by letting every site have its own long random string.

Generators matter because humans are bad at randomness. This tool uses crypto.getRandomValues, the cryptographic random source built into the browser, rather than Math.random, which is deterministic enough to be predicted in some conditions. Generation happens on your device and the results are never sent anywhere.

A note on the “guarantee one of each class” option: it satisfies composition rules that some sites still impose, but it slightly reduces entropy because it constrains the output. Enable it only when a site requires it.

Finally, if you need an identifier rather than a secret, use a UUID v4: 122 random bits, formatted as 36 characters, with no meaningful collision risk for practical volumes.

Using passwords well

The strength number behind every generator on this page is entropy, measured in bits: multiply the length by the base-2 logarithm of the alphabet size. Sixteen characters drawn from the roughly 94 printable ASCII symbols gives about 105 bits — an astronomically large space. A typical human-chosen password (“name + pet + year, capitalised, one symbol”) lands nearer 30–40 bits, which is within reach of modern offline cracking within hours. That gap is not about the symbol; it is about who or what did the choosing.

Two corollaries explain most password policy nonsense. First, substitutions defeat no one: P@ssw0rd! is a dictionary word to a cracking tool that tries leet variants as a rule. Second, composition requirements cost memory without buying much space — adding one more random character multiplies the search space by the whole alphabet, while mandating a symbol merely excludes a fraction of short strings. Length, randomness and uniqueness are the three properties that matter, in that order.

Where the string goes after you create it is the other half of safety. A site that stores passwords properly uses a slow, salted hash designed for the job — bcrypt, scrypt or Argon2 — so a database leak does not hand out plaintext. Sites that stored MD5 or bare SHA-1 in the past saw those passwords cracked within days of each famous breach. Two habits follow from this: reuse is what turns one company’s breach into your other accounts’ breach, and two-factor authentication caps the damage of any single stolen string, because the attacker still lacks the second factor.

For the handful of secrets you must type from memory — the password manager master, the device unlock — a passphrase beats a soup of characters. Randomly selected words carry about 12.9 bits of entropy apiece from the standard 7,776-word dice list, so six of them approach 78 bits while remaining sayable and typeable. Use real randomness to pick them (humans pick shockingly unrandom “random” words), and do not stitch them with predictable leet substitutions, which give back a large share of the entropy.

The flow that survives contact with real life: generate one 20–30 character password per site with the tool above, let the manager store and fill it, and never type or read it yourself. A service that blocks pasting into its password field is signalling it does not expect real passwords — take that as a warning about its other habits too. Where a site supports passkeys or hardware keys, prefer those outright: there is no shared secret to leak in the first place, and keep the printed recovery codes somewhere physical.

Finally, the identifiers on this page are a different job. A UUID v4 has 122 random bits in the familiar 8-4-4-4-12 shape, with collision risk that stays negligible well into billions of rows — but it is an identifier, not a secret: the format is enumerable and the value often appears in logs and URLs. If a value must stay private, generate crypto-random bytes and encode them with the Base64 tool instead — and if you must compare secrets rather than store them, hashing (the calculator) is the one-way door.

About the strength badge next to the generator: it estimates entropy from length and the character classes you enabled, which is honest mathematics but blind to the dictionary. Real-world checkers go further by testing against leaked-password lists and common patterns — so a 16-character random string from this page scores higher than a 12-character “clever” one even when the clever one looks more imposing. Sensible defaults for a new account: 20 or more characters, all four classes on, look-alikes off if the site supports it — then let the manager remember it, because the string’s only job is to be unreadable, not memorable.

Frequently asked questions

Is the password generation secure?

It uses crypto.getRandomValues, the browser cryptographic random source, not Math.random. Passwords are generated on your device and never transmitted or stored.

How long should a password be?

Length matters more than character variety. 16 characters is a good default; 20 or more for anything important. A password manager lets you use long random strings without having to remember them.

Should I require symbols?

Requiring symbols makes passwords harder to type and only slightly harder to guess compared with adding two more characters of length. Length is the stronger lever; keep symbols if the service allows them.

How to generate a password

  1. Set the rules: Choose a length and tick the character types to include.
  2. Generate: Click generate to get a password that matches the rules.
  3. Copy: Copy it to the clipboard — generated locally, never uploaded.