Hacks VitaeAll tools
Hacks Vitae Tools
Precision · Instant · Private

Make a strong password here, not on a server

Pick a length, press the button, and copy the result. The randomness comes from your browser's own cryptographic generator, and the password is never sent anywhere. Below: what the current NIST requirements say, including two that many sign-up forms do not follow.

SYSTEM ● ONLINE · LOCAL COMPUTE · ZERO UPLOAD
UNIT // PASSWORD.GENLIVE
Generated password
—
16
Length
0
Entropy bits
—
Strength
What it does

One password, made here, kept here

// In short

Each character is drawn from the pool you switch on, using crypto.getRandomValues. The W3C describes that interface as “a cryptographically strong pseudo-random number generator seeded with truly random values”. Nothing is uploaded, nothing is logged, and closing the tab is the end of it — so copy the password into a password manager before you leave.

What the rules actually say, and who they are written for

NIST’s current guidance is worth reading because it is more specific than the advice that circulates. In SP 800-63B-4 the requirements are addressed to the services that check your password rather than to you, and section 3.1.1.2 says they “SHALL require passwords that are used as a single-factor authentication mechanism to be a minimum of 15 characters in length”. A password used only alongside a second factor may be shorter, but still “a minimum of eight characters”.

Two of the other requirements are the interesting ones, because plenty of sign-up forms do the opposite. Services “SHALL NOT impose other composition rules (e.g., requiring mixtures of different character types)”, and they “SHALL NOT require subscribers to change passwords periodically” — though a verifier must force a change where there is evidence the secret has been compromised. They “SHOULD permit a maximum password length of at least 64 characters” too.

NIST writes these guidelines for US federal systems, and says the publication “may be used by nongovernmental organizations on a voluntary basis”. We are not telling you what any particular service must do.

FAQ

Frequently asked questions

NIST SP 800-63B-4 (3.1.1.2) tells services to require at least 15 characters where the password is the only factor, and at least eight where a second factor is also used. Anything this tool produces at 16 or more clears both.
Not for strength, and the current guidance tells services not to demand them: they “SHALL NOT impose other composition rules (e.g., requiring mixtures of different character types)”. Adding length does more than adding a character class. Some forms still insist, which is why the switches are here.
crypto.getRandomValues, the browser's cryptographic generator, which the W3C describes as “cryptographically strong”. Not Math.random, which is not meant for this.
No. It is made in the page and exists only there. Nothing is uploaded, and nothing survives closing the tab — copy it somewhere first.
The current guidance says services “SHALL NOT require subscribers to change passwords periodically”, while requiring a change when there is evidence of compromise. Advice elsewhere still differs, so this is one to decide with whoever runs the account.
Worth knowing

Length beats character variety, and the maths says so

// Answer

Drag the slider to 20 or more and stop worrying about the other switches. Every extra character multiplies the search space by the size of the pool; turning on a whole extra character class multiplies it only once. Length is the lever with compound interest.

The numbers are arithmetic, not opinion. With all four sets on, the pool is 87 characters: 26 uppercase, 26 lowercase, 10 digits and 25 symbols. Each character therefore carries log2(87) = 6.44 bits. With only lowercase on, the pool is 26 and each character carries 4.70 bits. That 1.74 bits is the entire difference between the two extremes.

Sets switched onPoolBits per characterA 16-character password
a-z264.7075 bits
a-z, 0-9365.1783 bits
a-z, A-Z525.7091 bits
a-z, A-Z, 0-9625.9595 bits
All four876.44103 bits

Read the first and last rows together: 22 lowercase letters carry 103 bits, the same as 16 characters drawn from all four sets. Six extra keystrokes replace every symbol, digit and capital. So when a password feels unwieldy, drop the symbols and add length rather than the other way round.

Worked example

Crack times, with the assumption stated out loud

Every "time to crack" figure rests on a guess rate that usually goes unmentioned. Here is ours, and it is an assumption rather than a measurement: assume an attacker who already has the stolen password hash and can test 1012 candidates per second offline, finding it on average halfway through the space — so 2n-1 guesses for an n-bit password.

Length (all four sets)EntropyAverage time at 1012 guesses/second
6 characters39 bitsabout 0.3 seconds
8 characters52 bitsabout 38 minutes
12 characters77 bitsabout 2,400 years
16 characters103 bitsabout 1.6 × 1011 years
20 characters129 bitsabout 1.1 × 1019 years

Change the assumed rate and every row moves with it: a rate a thousand times higher shifts each figure down a thousandfold, which is the same as losing about 10 bits of length. Note what that does and does not change. The 6-character row is hopeless under any assumption; the 20-character row is absurd under any assumption you could defend. Only the middle rows depend on the guess rate, and that is the summary of the whole argument.

Two caveats. The table assumes offline guessing against a stolen hash; an online login form with rate limiting is a far smaller problem. And it assumes the site stored your password with a slow modern hash — if it stored it in plain text, none of this was ever the weak link.

Under the hood

Where the randomness comes from, and two caveats

A generator is only trustworthy if its randomness is unpredictable. This one draws from crypto.getRandomValues, the browser's cryptographically secure source, which the W3C specification says implementations should seed with “high-quality entropy, such as from an operating-system entropy source”. It does not use Math.random, whose output is fine for shuffling a carousel but, in MDN's words, does not provide cryptographically secure random numbers. Two limitations, stated because you should not have to take the claim on faith.

1. There is a modulo bias, and it is minuscule

Each character comes from a 32-bit random value reduced with a remainder. 232 is 4,294,967,296, and 87 × 49,367,440 = 4,294,967,280, leaving 16 spare. So the first 16 characters of the pool are each produced by 49,367,441 of the possible draws while the rest get 49,367,440 — an excess of about one part in 49 million. A genuine deviation from uniform, and far too small to move any figure above.

2. No character class is guaranteed to appear

Each position is drawn independently from the combined pool, so a 16-character password with all four sets on may legitimately contain no symbol. The chance is (62/87)16 ≈ 0.0044, about 1 in 226. When a site insists on a symbol, press Generate new again. Do not hand-edit a ! onto the end: that puts a predictable character in a predictable place, which takes back some of the randomness. For the same reason, take the first result that satisfies the rules instead of scrolling for one that looks nicer — human taste is a pattern.

Reference

The exact character sets, and what the labels mean

The symbol set is precisely these 25 characters: !@#$%^&*()-_=+[]{};:,.<>?. Absent are the space, backslash, forward slash, both quote marks, the pipe, tilde and backtick — the ones most likely to be rejected by a login form or mangled by a shell. Deliberately conservative, which helps when the password must survive being pasted somewhere awkward.

There is no "avoid lookalikes" switch, so l, I and 1 can appear together, as can O and 0. Irrelevant when you paste, painful when reading a password aloud or typing it with a TV remote; for those cases, symbols off and more length.

The Strength label comes from the entropy figure alone: under 64 bits Weak, under 80 Good, under 120 Strong, 120 or more Very strong. It describes how the password was made, not how it looks — the same eight letters typed by hand carry nothing like 52 bits, because you did not choose them uniformly at random.

Limits

What this page is not

It is not a password manager and it stores nothing: no history, no list, no recovery. Reload and the password is gone for good, so open the vault entry first, then generate and paste. A strong password you cannot reproduce is an account you cannot reach.

It is not a passphrase generator either: no word list, so it makes character strings rather than four-random-words. Both are sound; this is simply not the other. Nor is it a source of key material for software — for identifiers use the UUID generator, for digests the hash generator, and in real code derive keys with a purpose-built KDF. If you want arbitrary random text with your own alphabet, the random string generator fits better. And encoding is not protection: Base64 is reversible by anyone, instantly, by design.

Privacy

Why it matters that this one runs locally

A password that crossed a network before you ever used it is not a secret. A generator that builds the string on its server puts your future credential in that server's access log, in whatever proxy sits in front of it, and permanently in the operator's backups. None of that requires bad faith — ordinary logging is enough.

Here the string is assembled by your own browser from your own machine's entropy. The script has no fetch, no XMLHttpRequest and no beacon, and the proof takes ten seconds: load the page, turn off your Wi-Fi, keep generating. What still leaves the page is what you do next — copying puts the password on the system clipboard, where other apps may be able to read it (phones restrict this more than desktops), and it stays on screen until you navigate away. Paste it into your manager promptly, and think twice about generating one while your screen is shared. The rest of this family is on the generators page.

Sources

Where these facts come from

Last reviewed 21 October 2026

4 more

More generators tools

All 9 →

Everything here runs in your browser. Browse all the tools, or start from the home page.

Ask an assistant about this page

Opens in a new tab with this page and the question already filled in.