How to Create a Strong Password: Length Beats Complexity

TL;DR: A strong password is long before it is complicated. Aim for at least 16 characters, generated randomly rather than invented from personal details. Length is what multiplies the guessing effort; symbols and capital letters add far less than most advice suggests. Use a unique password for every account and let a manager remember them.

Length beats complexity, by a lot

This is the point that has changed most in the last decade of security advice, and it is the one most people have not updated.

Every extra character multiplies the number of combinations an attacker must try. Going from 8 characters to 16 does not double the difficulty; it raises it by roughly the same factor raised to the eighth power. Complexity rules, meanwhile, add a small multiplier and push people toward predictable patterns like Password1! and Summer2025! that attackers test first.

The practical conclusion is simple: a long random password is stronger than a short complicated one, and it is also easier to type.

What the numbers look like

Rough guidance, assuming random generation rather than human-chosen strings:

  • 8 characters – cracked quickly by modern hardware if the hash is weak
  • 12 characters – acceptable minimum for low-value accounts
  • 16 characters – a sensible default for anything that matters
  • 20+ characters – appropriate for email, banking, and password manager access

These are guidelines, not guarantees. The real variable is how the service stores passwords. A well-designed service uses a slow hashing algorithm, which makes guessing dramatically harder; a badly designed one may store them in a form that falls fast.

You cannot control the server side, so the practical answer is to make the password long enough that it does not matter.

Passphrases are easier to live with

For the few passwords you actually have to remember, a passphrase beats a scramble. Four or five unrelated words, such as a random combination of nouns, gives you high length with something your memory can hold.

The trap is that people invent phrases from song lyrics, quotes, or family names, which makes them guessable. The value comes from random selection, not from meaningful sentences. If you build a phrase yourself, it will probably be less random than you think.

For everything else, generate and store. There is no benefit to memorising a password you could look up.

The rules that actually matter

Most password guidance is noise. These are the ones with real impact:

Never reuse. One leaked password should not open your email and your bank. Reuse is how a small breach becomes a total one.

Prioritise email. Your email account can reset almost every other account. It deserves the longest password and two-factor authentication before anything else.

Turn on two-factor authentication. A long password protects against guessing; two-factor protects against a breach where the password is already known. They solve different problems.

Change passwords after a breach, not on a schedule. Routine forced rotation encourages weak, incremental changes like Password1 to Password2. Change when there is a reason.

Never send credentials over chat or email. That includes “just this once” for a family member.

Patterns that look strong and are not

Attackers use dictionaries built from real leaked passwords, and those dictionaries are extremely good at the things humans invent.

Substituting characters is the classic failure: P@ssw0rd is in every cracking list. Appending a year or exclamation mark is the second: Company2024! takes almost no extra effort to crack. Keyboard walks like qwerty and 1qaz2wsx are covered. Names, pet names, sports teams, and birthdays are all in the dictionaries.

If a password has a structure you can describe to another person, it probably has a structure an attacker can describe too.

The practical workflow

Generate, store, and stop thinking about it. That is the whole method.

When you create an account, let the generator produce 16 to 20 random characters, save it, and move on. When a site offers a passphrase mode, use it. When you must type a password on a device that is not yours, use a temporary one and change it afterwards.

If you want a quick sanity check on a specific password, a password strength tester will show how quickly it would fall to an offline attack. The result is usually more convincing than any explanation.

What about biometrics?

Fingerprint and face unlock are convenient and genuinely secure against a stranger guessing a password. They are not a replacement for a strong password, for one structural reason: a biometric cannot be changed.

If a password leaks, you change it. If a fingerprint template leaks, you cannot issue yourself a new finger. That is why biometrics work best as a local convenience layer, unlocking a device or a vault, rather than as the secret that authenticates you to a remote service.

Most phones handle this correctly by using biometrics to unlock a hardware-backed key, which then authenticates to the password manager. The fingerprint never leaves the device. That design is fine. Sending a fingerprint hash to a website is not.

The practical rule: use biometrics to unlock things you control, and use a long random password plus two-factor authentication to prove identity to services you do not.

What to do this week

Change your email password to something long and unique, enable two-factor authentication on it, and install a manager for the rest. That sequence fixes the highest-risk account first and makes everything after it easier.

Then work through banking and any account with a saved payment method. Everything else can migrate gradually as you log in.

The goal is not a perfect setup on day one. It is reaching the point where no single leak can hand an attacker your whole digital life.