Skip to content
Calcipedia
Sophie Chen

Sophie Chen

Tech Writer & Software Engineer

19 March 2026 · Updated 31 March 2026

How to Create Strong Passwords You Can Actually Remember

Learn how to make strong passwords, when to use passphrases, why password managers and passkeys help, and which accounts to lock down first after a breach.

Somewhere right now, someone is creating an account with the password “Summer2026!” and feeling genuinely proud of themselves. Capital letter, number, special character — that hits all the requirements, right? It does. It’s also the digital equivalent of locking your front door and leaving the key under the mat. With a neon sign pointing at the mat.

Password security is one of those things everyone knows matters and almost nobody does well. It’s like flossing, or reading the terms of service, or backing up your hard drive. We understand the theory. We just keep hoping that “qwerty” with an exclamation mark will somehow be fine.

It won’t. Let’s talk about why, and what to do instead.

Why are weak passwords still so common?

The fundamental problem with human-created passwords is that humans are predictable. We pick dictionary words. We substitute letters with obvious numbers — “a” becomes “4”, “e” becomes “3”, “o” becomes “0”. We append the current year. We capitalise the first letter because the form told us to. Every single one of these patterns is the first thing an automated cracking tool tries.

Modern password-cracking rigs can test billions of combinations per second. A six-character password made of lowercase letters falls in under a second. Eight characters with mixed case and numbers? A few hours. That twelve-character password you thought was clever because it contains your cat’s name and your birth year? If it follows a recognisable pattern, it’s not buying you nearly as much time as you think.

The maths is unforgiving. Password strength is fundamentally about entropy — the number of possible combinations an attacker has to try. A truly random 16-character password drawn from uppercase, lowercase, digits, and symbols has roughly 105 bits of entropy. Your pet’s name with some number-swaps has maybe 30. That’s not a small difference. That’s the difference between a padlock and a bank vault.

The other problem is reuse. Attackers do not need to crack every password from scratch if a leaked login from one site happens to work on five others. That is why a password breach at an old shopping site can suddenly become a problem for your email, cloud storage, or payroll account. Security people call this credential stuffing. Normal people call it a very bad Tuesday.

How do you create a strong password you can still use?

Three things matter, in order of importance:

Length. This is the single biggest factor. Every additional character multiplies the number of possible combinations exponentially. A random 20-character password is orders of magnitude stronger than a random 12-character one, even if both use the same character set. If you remember nothing else from this article, remember: longer is better.

Randomness. The characters need to be genuinely unpredictable. Not “unpredictable to your friends” — unpredictable to a computer running statistical analysis on billions of leaked passwords. Humans are terrible at generating randomness. We think we’re being clever, but we’re drawing from the same mental well as everyone else. Let a machine do it.

Character variety. Using uppercase, lowercase, digits, and symbols expands the pool of possible characters at each position. This matters less than length and randomness, but it still helps. Think of it as seasoning — it’s not the main ingredient, but it improves the dish.

The Password Generator below handles all three of these for you. Set your desired length, pick your character types, and let it produce something that no human brain would ever come up with. That’s the point.

Generate passwords locally with browser cryptography Choose a random password for a password manager or a longer passphrase for manual typing. The output is generated in your browser; Calcipedia does not receive or store it.

Quick presets

24 random characters with symbols for accounts you will store, not memorize.

18 characters without symbols for stricter sign-up forms.

A longer passphrase for passwords you may need to type manually.

Shorter mixed password for old systems with tight length limits.

Password type

Character types

Generated password

.0y+.+Eq89dA:guynTOJFiV-

Strength estimate Strong

~155 bits of entropy · 24 characters · source size 88

Excellent for password-manager storage and high-value accounts.

Generate a unique password for every account and store it in a password manager.

Batch output

  • #1 .0y+.+Eq89dA:guynTOJFiV-
  • #2 @GHl?_-ve-L4osUxI|=Y7[UY
  • #3 cnI,+u-oz[!1h;t-@WApxD%9
  • #4 0ZEnM(=f>j^L4aPQvm@ZLF34
  • #5 Ecx0o)9@r%_0bs!s2*?J2iAy

If you are deciding what length to use, here is the practical version. For high-value accounts such as email, banking, cloud storage, and your password manager, I would start at 20 characters and only go shorter if the site behaves like it was last redesigned during the ringtone era. For ordinary logins, 16 random characters is still far better than the vast majority of passwords people create for themselves. The important part is not chasing a magical number. It is using a unique, machine-generated password every single time.

Once you generate one, save it immediately in a password manager before you do anything else. Do not admire it, think you will remember it, and then close the tab like a tragic hero. You will not remember it. That is not a moral failing. It is just how brains work.

If a site forces absurd password rules, use the generator to fit the site rather than falling back to your old favourite. Plenty of websites still insist on one symbol, one number, one uppercase letter, and a haiku about your first pet. Fine. Let the generator satisfy the nonsense while you keep the password long and unique.

Are passphrases better than passwords?

If staring at “x7#Qm!9vLp2&kR” makes you want to go back to using your dog’s name, there’s a middle ground: passphrases. String together four or five random, unrelated words — “correct horse battery staple” is the famous example, though you shouldn’t use that exact one since it’s now in every cracking dictionary on the planet.

A four-word passphrase from a list of 7,776 words gives you about 51 bits of entropy. Bump it to six words and you’re at 77 bits. Not as strong as a fully random 20-character string, but dramatically stronger than anything you’d invent on your own, and actually possible to type without wanting to throw your keyboard out the window.

The trick is that the words must be randomly selected. “I love my cat” is not a passphrase. It’s a sentence. Attackers know about sentences.

This is where people often wander off course. Song lyrics, film quotes, family mottos, football chants, and “funny phrases only I would think of” feel personal, so they feel secure. They are not. They are still built from familiar language patterns. If you want a passphrase that holds up, use unrelated words, keep it long, and do not decorate it with the same predictable substitutions everyone else uses.

Passphrases are especially useful when you genuinely need to type something yourself: a master password, a device login, a streaming box, a console, or any situation where copying and pasting a 24-character random string feels like a prank. In those cases, a long, random passphrase is the grown-up compromise between security and sanity.

Should you use a password manager or a passkey?

Here’s the uncomfortable truth: you shouldn’t be memorising passwords at all. Not in 2026. A password manager generates unique, random credentials for every account, stores them encrypted behind a single master password (or biometric), and auto-fills them when you need them. You memorise one strong passphrase. The manager handles the other three hundred.

I used to work at a startup where the entire engineering team shared a single password for the production database. It was stored in a Slack channel called #passwords. The startup no longer exists, and while I can’t prove causation, I’m not ruling it out.

Use a password manager. Use unique passwords for every site. Enable two-factor authentication everywhere it’s offered. This is the baseline in 2026, not the advanced course. Current guidance from organisations such as NIST and CISA leans in this direction too: longer unique passwords, password managers, and stronger sign-in protections matter far more than clever little symbol swaps.

And now there is a newer option worth knowing about: passkeys. If a service offers a passkey, it is usually better than creating yet another password because passkeys are designed to resist phishing and do not rely on you inventing something memorable in the first place. In practice, that often means you sign in with your device PIN, fingerprint, or face unlock instead of typing a password at all.

The important distinction is that passkeys and password managers are not enemies. For most people, they work together. Use passkeys where supported. Use a password manager for the many sites that still need passwords. Keep MFA turned on for important accounts, especially email, banking, and anything that can reset other logins. If your email account is weak, everything downstream is weak too.

If you are cleaning up an old mess of reused passwords, start with the accounts that can unlock the rest of your digital life:

  1. Email
  2. Banking and payment services
  3. Apple, Google, or Microsoft account
  4. Password manager
  5. Work logins and cloud storage

Change those first, turn on MFA, and then work through the less critical accounts afterwards. That one-hour triage session will do more for your account security than reading ten breathless headlines about hackers in balaclavas.

What should you do after a password leak or breach?

If you find out one of your passwords has been exposed, do not just change that single account and declare victory. The more useful question is: where else did I reuse it, or anything close to it? A leaked password often travels with its friends. “Summer2026!”, “Summer2026!@”, and “Summer2026!Netflix” are not different passwords in any meaningful defensive sense.

Work methodically. Search your password manager for reused or similar entries. Update the password on the breached site, then change every other account that used the same or a closely related version. Log out of old sessions if the service offers that option. Review recovery email addresses, backup codes, and trusted devices. If the account holds payment details or private data, check recent activity instead of assuming nothing happened.

You also do not need to turn this into a monthly password-rotation ritual for every account you own. Change passwords when they are weak, reused, exposed, or no longer under your control. Changing a strong unique password every few weeks just creates more opportunities to invent something worse.

This is also where your email account matters so much. A surprising number of breaches become dangerous not because the first account was valuable, but because it let an attacker request password resets elsewhere. If your email password is old, reused, or memorable in the wrong way, fix that before you fix anything else.

When does your network setup matter for account security?

Password security doesn’t exist in a vacuum. The network you’re connected to matters too. If you’re logging into your bank on an unsecured public Wi-Fi network, your strong password is doing less heavy lifting than you’d hope. Understanding basic network architecture — how devices are addressed, how subnets partition traffic, how your home network is structured — gives you a more complete picture of where your data actually travels.

Subnetting, for instance, is how networks are divided into smaller segments. Your home router creates a subnet that separates your devices from the wider internet. Corporate networks use subnets to isolate departments, limit broadcast traffic, and enforce access policies. It’s plumbing, essentially — not glamorous, but the kind of thing you notice immediately when it breaks.

If you’re curious about how IP addressing and subnetting work, or you need to calculate network ranges for a home lab or small office setup, the IP Subnet Calculator below breaks it down.

IP subnet calculator Calculate an IPv4 subnet from a CIDR prefix or dotted subnet mask, then compare the network address, broadcast address, first and last usable host, wildcard mask, host count, and binary breakdown.

Common subnet presets

Current subnet: 192.168.1.0/24 uses 24 network bits and 8 host bits.

Planning notes

Cloud VPCs can reserve provider-specific addresses inside each subnet, so the raw IPv4 usable host count may be higher than the number a cloud platform lets you attach to instances.

Wildcard masks are the inverse of subnet masks and are commonly used in ACLs, firewall rules, and routing policy syntax.

Result

192.168.1.0/24

This private subnet is a common LAN or VLAN size. Check the usable host count against DHCP pools, gateways, printers, servers, and growth room.

254

Usable hosts

256

Total addresses

/24

CIDR prefix

255.255.255.0

Subnet mask

IP Address192.168.1.100
Network Address192.168.1.0
Broadcast Address192.168.1.255
First Usable IP192.168.1.1
Last Usable IP192.168.1.254
Usable Host Range192.168.1.1 – 192.168.1.254
Subnet Mask255.255.255.0
Wildcard Mask0.0.0.255
CIDR Prefix/24
Network / Host Bits24 / 8
IP ClassC
IP TypePrivate
Binary IP11000000.10101000.00000001.01100100
Binary Mask11111111.11111111.11111111.00000000
Binary Network11000000.10101000.00000001.00000000

Subnet cheat sheet

CIDRMaskAddressesUsableTypical use
/16255.255.0.065,53665,534Large private block or route summary
/22255.255.252.01,0241,022Small business or cloud tier
/24255.255.255.0256254Common LAN or VLAN
/27255.255.255.2243230Small department subnet
/30255.255.255.25242Router-to-router link
/31255.255.255.25422RFC 3021 point-to-point link
/32255.255.255.25511Single host route

For most readers, the useful takeaway is not “become a network engineer by Thursday”. It is simpler than that. Know which devices are on your network. Put guests and smart-home gadgets on a guest network if your router supports it. Do not leave the default router password in place. Keep router firmware updated. And if you run a home lab, a small office, or anything with multiple device groups, understanding subnet boundaries helps you avoid turning one compromised device into everyone else’s problem.

If the calculator gives you a network address, broadcast address, and host range and you are wondering what to do with that information, here is the plain-English version: it tells you which addresses belong to the same local segment and how many devices can live there. That matters when you are separating work devices from personal ones, isolating test kit, or checking whether a router configuration is broader than you intended. It is less about creating a “strong password network” and more about reducing the blast radius if one login or device goes bad.

A practical 30-minute password cleanup plan

If you want the short version, here it is:

  1. Put your email account behind a long unique password and MFA first.
  2. Use the Password Generator to replace reused passwords with random ones.
  3. Use a long random passphrase only where you truly need something memorable to type.
  4. Turn on passkeys where they are offered and make sure your password manager is protected with MFA too.
  5. If you manage a more complex home or office setup, use the IP Subnet Calculator to sanity-check how your network is segmented.

Your accounts are only as strong as their weakest credential. Make sure that credential was not chosen by a tired human at 11:47 p.m. who thought “Dragon2026!” was a stroke of genius. I say that with love, and with painful memories of startup login habits that should never see daylight again.

Calculators used in this article