Generate passwords and API tokens from your browser's cryptographic random source. Choose the length and character sets. Nothing is stored, logged or sent.
Ready
Generated on your device with the browser's cryptographic random source.
Generating in your browser…
The random source is a browser API, so the first value appears as soon as this page loads.
The randomness is real. Values come from crypto.getRandomValues, the browser’s cryptographic source, sampled so that every character in the pool is equally likely. If that source were unavailable the tool would stop rather than quietly use an ordinary random number generator.
The entropy figure is arithmetic, not a score. It is the size of the space this generator draws from. It says nothing about whether a password has been reused, breached, or typed into the wrong site.
Length beats complexity. A longer password from a smaller alphabet is usually stronger than a short one studded with symbols, and far easier to live with.
Use a password manager. Generating a good password is the easy part; storing it somewhere you will not lose it, and not reusing it, is the part that actually protects an account.
Password Generator runs entirely on your device — nothing is uploaded or stored.
You’re on the Free plan. Compare plans
Every value this tool produces comes from crypto.getRandomValues, the cryptographic random source built into your browser. That distinction is the whole point of the tool. Math.random is a fast pseudo-random generator seeded from a small internal state; given enough output, its future values can be predicted, which makes it unsuitable for anything an attacker would want to guess. If the secure source were unavailable, this tool stops and says so rather than quietly falling back — a generator that degrades silently is worse than one that refuses, because the output looks identical either way.
Random characters also have to be drawn without bias. The naive approach — take a random byte and take it modulo the alphabet size — makes the first few characters of the alphabet slightly more likely than the rest, because 256 does not divide evenly by, say, 62. This generator discards values that fall outside a whole number of alphabet lengths and draws again, so every character is equally likely.
The entropy figure shown beside each value is arithmetic, not a judgement. It is the base-two logarithm of the number of values this generator could have produced with the current settings: 128 bits means one of roughly 3.4 × 10³⁸ possibilities. It is a property of the generator, not of your account, and it says nothing about whether a password has been reused, phished or typed into the wrong site.
Length does more work than complexity. A sixteen-character password drawn from lowercase letters alone has more entropy than an eight-character one studded with symbols, and it is far easier to type on a phone. Symbols are worth having, but not at the cost of a password short enough to brute-force.
Nothing generated here is kept. There is no history, no localStorage, no download, and no analytics parameter carrying a value — the only thing measured is that a button was pressed. Reloading the page replaces the value and no record of the previous one exists anywhere.
crypto.getRandomValues, the browser's cryptographic random number generator, which draws from the operating system's entropy pool. Characters are selected by rejection sampling so that no character is more likely than another. Math.random is never used.
No. Nothing is written to localStorage, no history is kept, no download is offered and no value is ever sent to analytics or any server. The password exists in the page and nowhere else, and reloading replaces it.
Sixteen characters is a sensible minimum for an account that matters, and twenty or more for anything holding money or administrative access. Where a service imposes a maximum, use the maximum it allows.
They widen the alphabet, which helps, but far less than adding characters. Going from twelve to sixteen characters buys more than adding symbols to twelve. Symbols also get mangled by badly written forms, so a longer password from a simpler alphabet is often the better trade.
The number of bits needed to describe one value drawn from this generator's possibility space. Around 128 bits is comfortably beyond brute force with any foreseeable hardware. It measures the generator's output space, not whether a password is safe in practice.
A password is drawn from readable characters for a human to type. A token is a given number of random bytes rendered as hex, Base64url or alphanumerics — the right shape for an API key, a session identifier or a webhook secret, where nobody has to read it aloud.
Yes. Generating a strong password is the easy part. Storing it so you do not lose it, and never reusing it across sites, is what actually protects an account — and no generator can do that part for you.