Generate strong random passwords with your browser's cryptographic random source, with length, character-set and look-alike controls — and nothing is ever stored. Free, no sign-up — runs locally in your browser.
Random, and nothing kept
A password generator has one job — unpredictability — and one
duty — amnesia. The unpredictability here comes from
crypto.getRandomValues, your browser's cryptographic
random source, sampled without modulo bias, so every character in
the pool is equally likely. The amnesia is a design choice you can
verify: most tools on this site keep a draft of your input in
local storage for a week, and the privacy policy lists which ones.
This page is written the other way. It never writes the settings
or the generated passwords to storage — close the tab and they are
gone, which is exactly right for a secret. The trade-off is real:
generate, copy, and put the password wherever it belongs (ideally
a password manager) before you navigate away.
How to use it
- A password is generated as soon as the page opens. Adjust the length slider and character sets and it regenerates instantly; the strength reading under it updates too.
- Tick Exclude look-alikes if the password will be read aloud or typed by hand — I, l, 1, O and 0 are the usual suspects.
- Use the batch to make several at once and copy the one you prefer; each row has its own copy button.
- Store the result in your password manager immediately. Nothing on this page will remember it for you — that is the point.
Reading the strength meter
The meter translates the settings into entropy: the number of
bits an attacker would have to search, on average half of
2bits guesses for a password drawn this way. The labels
are deliberately conservative and are always shown as words, never
colour alone — Weak under 40 bits,
Fair to 60, Strong to 80,
Excellent beyond: at 80+ bits, brute force stops
being the realistic risk and phishing, reuse and the service's own
breach become it. Note what the meter does not know: it rates the
recipe, not the individual password. A generated password is
random by construction, so for this tool's output the recipe is
the honest thing to rate — unlike a human-chosen password, where
the same arithmetic flatters badly.
Frequently asked questions
Are these passwords actually random?
Yes — every character is drawn from your browser's cryptographic random source (crypto.getRandomValues), the same source browsers use for security-sensitive work, with rejection sampling so no character is favoured by modulo bias. That is the important difference from toy generators that shuffle a wordlist or use Math.random(), whose output can be predicted by an attacker who sees a few samples. Each selected character set is guaranteed to appear at least once, and the result is then shuffled so that guarantee does not fix any positions.
Is it safe to generate a real password on a web page?
On this page, the generation happens entirely on your device: nothing you generate is sent anywhere, and — unlike most tools on this site — nothing is stored either. There is deliberately no "saved draft" here: not the settings, not the output. That said, the strongest workflow is a password manager with its own built-in generator, because it also stores the result encrypted and fills it in for you. Use this page for one-off secrets you will immediately put into a manager, a router, or a sticky note inside a locked drawer.
What does the strength reading actually measure?
It shows the entropy of a password of that length drawn from the selected character sets: length × log₂(pool size), in bits. Under 40 bits is crackable by a determined attacker with commodity hardware; 60–80 bits is a solid password; beyond 80 bits, the limiting factor stops being the password and becomes everything else (reused credentials, phishing, the site's own storage). The number describes the generator's output space, not a guarantee about any single password — a 16-character password that spells a sentence is weaker than its bit count suggests, which is why this tool never produces sentences.
Why exclude ambiguous characters?
Because some secrets still get read aloud, typed off a screen, or copied from paper: at small sizes I, l and 1 (capital i, lowercase L, one) and O and 0 are genuinely indistinguishable in many fonts. Excluding them removes five characters and costs almost no entropy at sensible lengths — a 16-character password without them still clears 90 bits — while removing an entire class of "it says invalid password and I don't know why" failures.
How long should a password be?
Length beats complexity almost everywhere: each added character multiplies the search space by the whole pool size, while swapping a letter for a symbol only helps if the attacker did not expect it — and they all expect it now. Sixteen characters from the full set is a good default for accounts; use 20+ for anything guarding money, email (your reset hub) or a password manager itself, and let the batch mode make several so you can pick one you can live with.
Dev