A password generator creates random credentials without predictable patterns. This tool uses browser cryptography, controls length and character sets, and does not store or send generated values. Save each password in a trusted password manager instead of reusing it.
How to Use the Password Generator
Choose a policy-compatible character set and generate locally.
- Set the Length slider from 8 through 128 characters; the default is 20.
- Enable Uppercase, Lowercase, Digits, and Symbols as required.
- Enable Exclude look-alike characters (Il1O0) when visual distinction matters.
- Set Count from 1 through 20.
- Select Generate, then review the estimated entropy in bits.
- Select Copy to copy the generated list, then keep only the password you intend to save; nothing is stored or sent.
How Cryptographically Random Password Generation Works
Secure password generation needs an unpredictable source. This tool obtains random values from crypto.getRandomValues, the browser API intended for cryptographic use. It does not use Math.random(), timestamps, or a predictable sequence. Generation occurs locally, and the resulting passwords are not stored or sent by the tool.
Mapping random numbers into a character set also matters. A simple remainder operation can favor some characters when the random range is not evenly divisible by the alphabet size. This generator uses rejection sampling: it discards values outside the largest evenly divisible range, then maps accepted values to characters. That avoids modulo bias while retaining uniform selection from the enabled set.
Browser cryptography is one part of a credential workflow. A compromised device, extension, clipboard, or screen recording can still disclose a generated value. Use a device you control and move the result directly into a reputable password manager. Never send a password through chat or reuse it as a sample.
Length, Character Sets, and Estimated Entropy
Length is the most useful control when characters are selected independently and uniformly. With an alphabet of N possible characters and a length of L, the idealized search space is N^L, and its entropy estimate is L × log2(N) bits. The displayed estimate describes the generator’s theoretical selection space, not a guarantee about every surrounding system.
Adding uppercase letters, digits, and symbols increases the alphabet, but adding more random characters often improves the search space more predictably than satisfying several composition rules at a short length. NIST guidance emphasizes allowing long passwords and avoiding arbitrary composition requirements. A site may still impose legacy rules, so choose only the sets it accepts and use the longest practical value.
Excluding I, l, 1, O, and 0 reduces transcription mistakes and slightly reduces the alphabet. Compensate with length if needed. Eight characters is available for compatibility, not as a universal recommendation. Prefer the default 20 or longer when supported, and remember that reuse or disclosure defeats the entropy estimate.
Password Managers, Unique Passwords, and Passphrases
Use a unique password for every account. Reuse turns one breach into a credential-stuffing risk elsewhere, even when the password was long and random. A password manager can generate, store, and fill unique values while protecting its vault with a strong primary credential.
For credentials you must type or remember, a long randomly generated passphrase can be easier than a dense character string. The words must come from a sufficiently large list and be selected randomly; a familiar quotation, song lyric, personal detail, or predictable substitution does not provide the same resistance to guessing. This tool generates character-based passwords rather than word passphrases.
Enable multifactor authentication, preferably with phishing-resistant methods when supported. MFA reduces some account-takeover risks but does not justify weak or reused passwords. Change a password when it is compromised or shared improperly; routine forced changes without evidence of compromise can encourage predictable patterns. Protect recovery codes as carefully as credentials.
Practical Limits and Safe Password Handling
Websites impose different maximum lengths and accepted symbols. Some silently truncate input or normalize characters, which can make a generated value fail later. Confirm the service accepts the password, store the exact accepted value, and test sign-in before closing a registration or reset flow. Do not weaken every password to satisfy one unusually restrictive system.
The clipboard is shared with the operating system and may be visible to other software. Copy only when needed, paste directly into the destination or password manager, and clear it when appropriate. Avoid screenshots, analytics fields, issue trackers, logs, URLs, and error reports.
An entropy estimate assumes independent uniform generation from the shown alphabet. It does not account for server-side hashing, rate limits, phishing, malware, recovery processes, or a breach that exposes plaintext. Services should store passwords with a salted, adaptive password hashing scheme rather than a fast general-purpose digest. The hash generator is useful for text integrity experiments, but SHA-256 and SHA-512 alone are not password-storage algorithms.
Frequently Asked Questions
What makes a password generator secure?
A suitable generator uses a cryptographically secure random source and maps values uniformly into the chosen character set. This tool uses crypto.getRandomValues with rejection sampling to avoid modulo bias. Security also depends on the device and handling: malware, exposed clipboards, reuse, screenshots, or insecure storage can compromise an otherwise unpredictable password.
How long should a generated password be?
Use the longest value the service and your password manager handle reliably. The default 20-character random password provides a substantial search space for common character sets, while longer values add margin. Eight characters is offered for compatibility, not as a general target. Follow applicable organizational policy without reducing length merely to add superficial complexity.
Are symbols required for a strong password?
Not universally. Symbols enlarge the available alphabet, but length and unpredictable generation are more important than satisfying arbitrary composition rules. Enable symbols when the service accepts or requires them. If a site rejects certain characters, generate a longer password from the accepted sets rather than manually editing a result in a predictable way.
Is an entropy estimate a guarantee of password strength?
No. The estimate describes the theoretical search space when each character is selected independently and uniformly from the enabled alphabet. It does not account for password reuse, disclosure, server storage, online rate limits, phishing, malware, or recovery weaknesses. Treat entropy as one property of the generated value, not a complete security rating.
References: MDN: crypto.getRandomValues() · NIST SP 800-63B: Authentication and Authenticator Management · OWASP Password Storage Cheat Sheet.