Why this matters
Password length is often treated as a box to fill until a strength meter turns green. That model confuses three different things: how many guesses an attacker can make, how much entropy the password contains, and whether a person can use the password reliably. A long password is not automatically strong. A short password can still be strong if it is generated from a large random space, while a long password can be weak if it follows a predictable pattern or has already appeared in a breach.
Modern password guidance has moved away from rigid composition rules, such as requiring one uppercase letter, one number, and one symbol. Current NIST guidance emphasizes length, screening against commonly used and breached passwords, and avoiding arbitrary periodic changes when there is no evidence of compromise. For single-factor authentication, the recommended minimum is 15 characters; 8 characters may be sufficient when the password is used as part of multi-factor authentication. These are floors, not ideal targets, and organizations or services may impose stricter requirements.
Each additional independent character expands the search space. If a password is selected uniformly from an alphabet of 62 possible characters, every extra character multiplies the number of possible strings by 62 and adds about 5.95 bits of theoretical entropy. That calculation is illustrative rather than a claim about the exact output of the password-generator in this guide, because its character set is not specified. A passphrase works similarly: if each word is selected independently from a 7,776-word list, four words represent about 51.7 bits and five represent about 64.8 bits, even though a human may remember the words far more easily than an equivalent random string.
The process
- Identify how the password will be used. Decide whether it protects an account with multi-factor authentication or serves as the sole factor. If it is the only factor, treat 15 characters as a baseline and choose a longer target, such as 20 or more, when the service accepts it.
- Choose a length before choosing decorative characters. A practical baseline is 20 characters for an important account protected only by a password. For a less critical account, the baseline can be shorter, but avoid dropping to the minimum merely to satisfy a meter.
- Open password-generator and set the requested length. Enter the desired value in the control labeled Length: characters. The tool generates random values using a secure random source and performs its processing locally in the browser, so the generated value does not require submission to a backend.
- Prefer a memorable structure when that is what you need. A sequence of several unrelated words is generally easier to recall than a short scrambled string, provided the words are not a familiar quotation, song lyric, or predictable substitution of names and dates. The generator described here produces random passwords; it is not documented as a passphrase generator, so create a passphrase yourself only if that suits your workflow.
- Test a short draft with password-strength when useful. Type or paste the candidate into the field labeled Password. The assessment updates locally and does not use a backend. This tool has a published limit of 12 characters, so it cannot provide a complete assessment of a final password that is longer than that.
- Do not treat a passing meter as the final decision. A meter can help expose an obvious weakness, but it cannot establish that a password is unique, has not been exposed, or is safe for a particular service. Check for reuse and choose a value that does not resemble any password already used elsewhere.
- Generate the final value when randomness is the priority. Set Length: characters to the selected target, obtain the generated password, and use the page’s available copy-to-clipboard control if you need to transfer it. The generator supports copying to the clipboard; it does not download files or upload anything.
- Store and use the password consistently. Place it in a trusted password manager, enter it only into the intended service, and enable multi-factor authentication where available. Do not rotate it on a fixed schedule merely because the calendar changed; investigate a rotation when there is evidence of exposure or compromise.
Worked example
Suppose you need a password for an important email account that does not offer multi-factor authentication. Because this password will be the primary barrier, begin with the 15-character single-factor minimum rather than treating 8 characters as an acceptable goal. Since length is inexpensive in a password manager, select a 20-character target. Open password-generator, enter 20 next to Length: characters, and use the random result as the final candidate. Its randomness comes from a secure random source, and the operation occurs locally in the browser.
Before accepting the final value, consider whether you also want a memorable fallback for less critical accounts. A phrase such as “Copper-Harbor-Lunar-Pencil” contains several unrelated words and may be easier to remember than a random character sequence. That convenience does not make every phrase secure: the words should be selected independently, not assembled from the account holder’s name, workplace, birthday, or a well-known phrase. If you want a rough strength check, enter a draft no longer than 12 characters into Password on password-strength. Remember that the final 20-character password exceeds that tool’s published input limit and therefore cannot be fully evaluated there.
Use the copied 20-character result only for the email account. Store it in a password manager, enable the service’s additional verification option if one is available, and avoid reusing it elsewhere. If the service reports that the password has appeared in known exposure data, generate a replacement rather than adding a predictable suffix such as a year. Length helps against guessing, but it cannot repair reuse or exposure.
Common mistakes
- Using the minimum length for every account. A 15-character password that meets the single-factor baseline may still be less appropriate for a high-value account than a longer, unique password. The minimum is a floor rather than a universal optimum.
- Assuming every added character adds the same practical protection. Adding a random character to an otherwise random password expands the search space. Adding a predictable “!” or a birth year to a known password pattern may mostly satisfy a visual rule without addressing the real weakness.
- Building a long passphrase from predictable material. A quotation, keyboard pattern, sequence of family names, or phrase formed from account details may contain far less entropy than its character count suggests. Word count alone does not establish strength.
- Replacing a compromised password with a minor variation. Password123!, Password123@, and Password123# remain closely related. If a credential has been exposed, generate a genuinely different password rather than appending a predictable character.
- Rotating strong passwords on a rigid schedule. Unnecessary rotation can create password variants that people struggle to distinguish, increase reuse, and encourage weaker choices. Modern guidance generally favors changing a password when there is evidence of exposure rather than on a calendar alone.
- Confusing a strength result with a uniqueness check. A local strength assessment cannot tell you whether the password already appears in a breach, has been reused on another service, or is known to an attacker.
- Choosing length that interferes with reliable entry. A highly random 60-character value can be difficult to type, especially on mobile devices, and may encourage users to fall back to an easier password. Select a length that fits the storage and entry method without making the account harder to access.
Limitations of this approach
- Length does not protect against every attack. A strong password cannot stop credential stuffing with already exposed username-and-password pairs, phishing, malware, session theft, or insecure recovery processes. Multi-factor authentication and secure account recovery remain separate controls.
- The browser tools have different boundaries. password-strength has a published limit of 12 characters, so it cannot assess the longer passwords most users should consider for important accounts. password-generator can select a character count, but its exact character set is not stated, so a specific entropy-per-character claim should not be assumed from the interface alone.
- Local processing reduces data transfer but does not create a complete security decision. Both tools operate locally and make no backend calls according to their tools. That supports direct handling of the input, but neither tool can check a live breach database, account-specific blocklist, or service-specific acceptance rules.
- A long passphrase can still be guessable. Words drawn from a small personal set, familiar song lyrics, names connected to the account holder, and common sentence fragments may be recognized even when they are long. Each word must add meaningful unpredictability.
- Length eventually meets human and service constraints. Password managers can handle long random values well, but typing them manually is harder. Some services impose their own maximum lengths or storage limits, and an excessively long value may be truncated if the destination system is poorly designed.
- These tools are not substitutes for account recovery design. Even an excellent password can become a liability if support staff can bypass controls, recovery questions contain guessable facts, or reset notifications reveal too much. Security depends on the wider account system, not only on character count.
Frequently asked questions
Is 15 characters always enough? No. Fifteen characters is the current NIST minimum for a single-factor password, but it is a baseline rather than a guarantee. A longer unique value provides more resistance to offline guessing, especially if some of its randomness comes from a predictable pattern.
Is an 8-character password acceptable? It can be acceptable in limited contexts, such as a password used as part of multi-factor authentication under applicable guidance, but it is a weak choice for an account protected only by a password. Eight characters leaves a much smaller search space than a longer random value.
Do uppercase letters, numbers, and symbols matter? They can increase the available character set, but modern guidance generally does not require a fixed combination of character types. Length and unpredictability are more useful than satisfying a formula that produces predictable substitutions.
Can I test my final password with password-strength? Only if it is within the tool’s published limit of 12 characters. A longer candidate can exceed what that page accepts, so the tool’s assessment should not be treated as a prerequisite for using a longer password.
Why is a long passphrase often easier to use than a random string? People generally remember meaningful units and word relationships more effectively than long strings of arbitrary characters. Four or five independently selected uncommon words can also provide substantial entropy, provided the phrase is not drawn from predictable personal information or a famous quotation.
Does adding one character make a weak password strong? Not necessarily. It helps when the character is independently random and the rest of the password is also unpredictable. Adding a predictable suffix to a breached password leaves the underlying guessable structure intact.
Should I change a strong password every few months? There is generally no reason to rotate a password on a fixed schedule when there is no evidence of compromise. Change it sooner if it is reused, exposed, associated with a security incident, or suspected to have become known to an attacker.
Is password-generator appropriate for a high-value account? It generates random passwords with a secure random source, supports choosing the length, and processes the operation locally. It does not by itself check whether a password has been breached, whether the destination service supports the chosen length, or whether multi-factor authentication is available.