Skip to content
32 characters

32-character password generator

This generator creates a random 32-character password using uppercase and lowercase letters, numbers, and symbols — 205.6 bits of entropy drawn from 8.0 x 10^61 possible combinations. Effectively a key, not a password. For machines only.

Very strong205.6 bits of entropy

Offline attack on a fast hash: 10^43 years

Beyond the reach of brute force. Your risk is now phishing and reuse, not guessing.

32

This page is fixed at 32 characters. Use the main generator to change it.

Include

Generated in your browser with crypto.getRandomValues. Nothing is sent to a server, logged, or stored.

Entropy
205.6 bits
Possible passwords
8.0 x 10^61
GPU, fast hash
10^43 years
GPU, PBKDF2 600k
10^48 years

Is 32 characters enough?

Thirty-two random characters carries more entropy than a 128-bit encryption key, which is the standard the entire internet's transport security rests on. No amount of extra length makes it meaningfully safer.

Compared with a 24-character password, this is roughly 2992179271 million times more work for an attacker — the cost of guessing grows by a factor of 86 for every single character you add.

When to use a 32-character password

Signing secrets, webhook tokens, seed values, and anything that lives in an environment variable rather than a human's memory.

What to watch out for

If a human has to handle a 32-character secret regularly, the process is wrong, not the password. Put it in a secrets manager.

How long this password survives each attack

"Time to crack" is meaningless without naming the attack. The same password fails in an afternoon or outlives the sun depending on how the website stored it. These are average times — half the keyspace — for this password:

Estimated average crack time by attack scenario for this password configuration
Attack scenarioGuesses / secondAverage time
Throttled login form10010^52 years
Stolen database, unsalted fast hash100 billion10^43 years
Stolen database, PBKDF2 with 600,000 iterations~167,00010^48 years

The third row is why key stretching matters so much. MoolKey runs PBKDF2 at 600,000 iterations for the same reason: it costs you a fraction of a second and costs an attacker a factor of 600,000.

You still have to keep it somewhere

A 32-character random string is not memorable, and pretending otherwise is how people end up with a sticky note. Either store it in a password manager, or use a generator that can recreate it on demand from one phrase you already remember — which means there is no stored copy for anyone to steal.

32-character password questions

Is a 32-character password strong enough?
A random 32-character password using uppercase, lowercase, numbers, and symbols carries 205.6 bits of entropy. Effectively a key, not a password. For machines only. Against an offline attack on a fast hash at 100 billion guesses per second, the average time to crack it is 10^43 years.
How many 32-character passwords are possible?
With a pool of 86 symbols there are 8.0 x 10^61 possible 32-character passwords. That figure only protects you if your password was chosen at random from all of them — a password you invented sits in a far smaller set that attackers search first.
How long does it take to crack a 32-character password?
It depends entirely on how the site stored it. On a rate-limited login form at 100 guesses per second: 10^52 years. Against a stolen database of fast hashes on a GPU cluster: 10^43 years. Against a properly stretched PBKDF2 hash with 600,000 iterations: 10^48 years.
Is this 32-character generator safe?
Yes. It runs entirely in your browser using crypto.getRandomValues, the cryptographic random source provided by your operating system. No password is transmitted, logged, or stored. You can disconnect from the network and the generator still works.

Make one account easier today.

Start with the password you keep reusing or the bank card that still shares a PIN. MoolKey is free, and you do not need to move everything at once.

Free forever Works offline Phone or computer