Password entropy calculator
Measure a password's real strength, or the entropy of a randomly generated one.
Related tools
All Hashing & crypto tools →The Password entropy calculator turns Length of a random password, Character set into Entropy (bits), Strength, instantly and for free. For instance, with Length of a random password = 12 and Character set = Lowercase (26) it returns Entropy (bits) = 56.405 and Strength = fair.
How to use it
- Enter your values: Length of a random password, Character set.
- Read the result instantly: Entropy (bits), Strength.
Frequently asked questions
How does the Password entropy calculator work?
It takes Length of a random password and Character set and derives Entropy (bits) and Strength from them. The calculation is live as you type, so the result updates on every change.
Which values does the calculator ask for?
2 values: Length of a random password and Character set. Nothing else is required — no account, no file upload.
What does a typical calculation look like?
With Length of a random password = 12 and Character set = Lowercase (26), the calculator returns Entropy (bits) = 56.405 and Strength = fair. Those figures come from running this exact tool, so you can reproduce them by entering the same values.
How much does the result change with different inputs?
It moves a lot. Using Length of a random password = 24 and Character set = Upper + lower (52) instead, Entropy (bits) goes from 56.405 to 136.811 — which is why it is worth testing a few scenarios rather than trusting a single figure.
Which “Character set” option should I choose?
You can pick between « Lowercase (26) », « Upper + lower (52) », « Letters + digits (62) » and « + symbols (95) ». Each one changes what the calculator works out, so switch and compare — the default is « Lowercase (26) ».
What does it give for smaller values?
Scaled down to Length of a random password = 6 and Character set = Lowercase (26), Entropy (bits) comes out at 28.203. The relationship is worth checking at both ends before you rely on a single result.
When would I actually use this?
Verifying a download matches its published checksum, comparing two files without reading them, and generating a signature for an API request.
What is the most common mistake?
Hashing a password with a fast algorithm. MD5 and SHA are built to be quick, which is exactly wrong for passwords — those need a deliberately slow function like bcrypt, scrypt or Argon2.
Where do the figures come from, and how current are they?
The digests follow their published specifications and are computed by the browser's own crypto implementation where one exists, so a value can be checked against any other conforming tool.