Tools lab · Security
Free Password Generator
Generate strong, customizable passwords for secure accounts.
Generator
Configure length and character sets to generate secure, random passwords for accounts, API keys, and infra.
How this password generator works
Step 1
Set the length
Specify how many characters the password should have; longer passwords are exponentially harder to brute‑force.
Step 2
Choose character sets
Enable uppercase, lowercase, digits, and symbols to expand the character space and increase entropy.
Step 3
Generate and store
Generate the password, copy it, and save it in a password manager instead of memorising or reusing it.
Frequently asked questions
What does the password length control do?
Length sets how many characters are in the final password; each extra character multiplies the number of possible combinations, making brute‑force attacks far slower.
For regular accounts, 12–16 characters is usually enough, while critical systems like email, banking, or production infra benefit from 20+ characters.
What do the character set checkboxes mean?
Each checkbox toggles a group of allowed characters: uppercase letters, lowercase letters, numbers, and symbols; the generator builds a pool from all selected groups and draws characters from it uniformly at random.
Using at least three sets (for example lowercase, uppercase, and numbers) is a good balance between usability and strength, while adding symbols further hardens against guessing.
Why is a generator better than making my own passwords?
Manually chosen passwords often include predictable patterns, words, or dates, which attackers can target with dictionary and pattern‑based attacks.
A generator produces high‑entropy strings that are not tied to personal information, which significantly reduces the chance that automated tools can guess them.
How should these passwords be stored?
Store generated passwords in a reputable password manager instead of browsers, notes apps, or email drafts, so credentials stay encrypted and synced across devices.
Avoid reusing the same password across services; if one site leaks, reused credentials can be replayed on other logins in large‑scale attacks.
Is it okay to use different rules for different services?
Some services disallow symbols or cap length, so tailor the checkboxes and length to match each site’s password policy while staying as long and complex as allowed.
For services with strict rules, prefer maximum length with mixed character types even if symbols are not permitted, to keep overall entropy high.