SecretNote.eu

Password Crack Time: How Long Each Length Takes to Brute-Force

Password crack time depends on two things: how many characters the password has and how many different characters each position can be. Here is how long each length holds up against a fast brute-force attack, and why every extra character matters more than any symbol.

Sophie ParkerPublished · Updated · 8 min read
Padlocks of growing size beside hourglasses, showing that longer passwords take far longer to brute-force
Key takeaways The short version, before the details.
  1. At one trillion guesses a second, a random 8-character password falls in under an hour, even with symbols.
  2. Each extra character multiplies the work. A random 16-character password would take longer than the universe has existed.
  3. The tables only hold for random passwords. Human-chosen ones fall to dictionary attacks far sooner.

Ask how long it takes to crack a password and you get answers from "seconds" to "forever". Both can be right. Password crack time is plain arithmetic once you fix three numbers: how long the password is, how many characters it could be drawn from, and how fast the attacker can guess.

This guide fixes those numbers, shows the results by length, and then explains where real life differs from the table.

Password crack time by length and character set

The table assumes a truly random password and an offline attacker making one trillion guesses per second. On average the attacker finds it halfway through all possible combinations. Times are rounded.

LengthLowercase only (26)Upper and lowercase (52)Letters and numbers (62)All keyboard characters (95)
8InstantlyAbout 27 secondsAbout 2 minutesAbout 55 minutes
10About 1 minuteAbout 20 hoursAbout 5 daysAbout 11 months
12About 13 hoursAbout 6 yearsAbout 51 yearsAbout 8,600 years
14About 1 yearAbout 17,000 yearsAbout 197,000 yearsAbout 77 million years
16About 690 yearsAbout 45 million yearsAbout 760 million yearsLonger than the universe has existed
20About 316 million yearsLonger than the universe has existedLonger than the universe has existedLonger than the universe has existed

Two patterns jump out. Going from 8 to 12 characters does more than adding every symbol on the keyboard. And at 16 random characters with a full mix, brute force stops being a realistic threat at all.

What these numbers assume

A trillion guesses a second is a fast offline attack: the attacker has stolen a database of password hashes and is guessing on their own hardware against a quick hash. Against a live login page, or a slow password hash, the same password lasts far longer.

How password crack time is calculated

A random password of length L drawn from N possible characters has N to the power of L combinations. On average an attacker finds it after trying half of them. Divide by the guessing speed and you have the time.

combinations = N ^ L
average guesses = combinations / 2
crack time (seconds) = average guesses / guesses per second

example: 12 characters, 95-character set, 10^12 guesses/s
95^12 = 5.4 x 10^23 combinations
2.7 x 10^23 / 10^12 = 2.7 x 10^11 s = about 8,600 years

Security people often say the same thing in bits of entropy: length times log2(N). Each character from a 95-character set adds about 6.6 bits, and every extra bit doubles the work. An 8-character lowercase password has about 38 bits. A 16-character password from the full set has about 105.

Password length time to crack: what one character adds

Length is an exponent, so it compounds. With a full keyboard set, each extra character makes the attack about 95 times longer. Ten characters take about 95 times longer than nine. Eleven take about 9,000 times longer than nine.

Widening the character set only changes the base. Going from lowercase to all 95 characters multiplies the work by about 3.7 per character. That helps, but it is a small step next to adding two or three characters.

8 characters

Minutes to hours

Even with symbols, a random 8-character password falls in under an hour at a trillion guesses a second.

12 characters

Years to millennia

Random and fully mixed, it holds for thousands of years. With letters only, it can still fall within a human lifetime.

16 characters

Out of reach

With a full mix, it would take longer than the universe has existed. Brute force is no longer the threat.

Why real passwords crack faster than the table

The tables assume every character is random. People's passwords are not. Attackers know this, so they rarely start with pure brute force. They try the likely passwords first.

  • Dictionary and leak lists. Billions of real passwords from past breaches are freely available. If yours is on one, its crack time is close to zero, however long it is. You can check a password against known leaks with Have I Been Pwned's Pwned Passwords.
  • Patterns. A capital first letter, a word, a year and an exclamation mark at the end is a pattern that cracking rules try early. "Summer2025!" looks like 11 mixed characters but behaves like a short word list.
  • Reuse. A password cracked on one site gets tried everywhere else, which is the idea behind credential stuffing as opposed to brute force. Length cannot protect a password that has already leaked. See why password reuse is so dangerous.

Crack time estimates are a best case. Any calculator that counts characters treats "Password123!" like a random 12-character string. Real attackers would guess it in seconds. Trust the numbers only for passwords a generator made.

What slows a brute-force attack down?

How fast an attacker can guess depends on where they are guessing and how the password was stored.

  • Online attacks are slow. Against a live login page, the attacker is limited by network speed, rate limits, lockouts and bot checks. Thousands of guesses an hour is a lot there, so even modest passwords survive pure brute force online.
  • Fast hashes are the danger zone. General-purpose hashes like MD5 or SHA-256 are built to be quick, which helps attackers who have stolen a database. That is why SHA-256 is fine for checksums but too fast for storing passwords.
  • Slow password hashes cut the rate dramatically. Algorithms such as Argon2id, scrypt and bcrypt are deliberately expensive, so each guess costs real time and memory. The OWASP Password Storage Cheat Sheet recommends them for exactly this reason.

You cannot pick how a website stores your password. So plan for the worst case, a fast offline attack, and choose a length that survives it.

What password length survives an offline attack?

For accounts you care about, use at least 16 random characters with a mix of character types. That puts brute force out of reach even in the fast offline case. Then make sure the password is never reused and never chosen by hand.

Standards bodies agree that length matters most. NIST SP 800-63B asks services to accept long passwords and check new ones against known breached passwords, rather than forcing complexity rules.

Make a password that survives brute forceRandom, 8 to 64 characters, generated in your browserOpen tool

A password manager makes this painless: you only remember one strong master password, and every account gets its own long random one.

How to check your own password crack time

The SecretNote password generator uses the same model as the tables above: a trillion guesses a second, half the possible combinations on average.

  • For new passwords: set a minimum and maximum length between 8 and 64, choose lowercase, uppercase, numbers and symbols, and generate. It uses your browser's secure random number generator and shows the password's bits of entropy, an estimated brute-force time, and a rating from Weak to Excellent.
  • For an existing password: the "Test a password" box on the same page estimates how long the password you type would take to guess. It works out the character set from the types of character you used. It runs entirely in your browser, and what you type is never sent or saved.

Keep the limits in mind: the tester counts characters, not meaning. A dictionary word with a number added will score far better there than it deserves. For a password you will actually rely on, let the generator make it.

Long random password with a strength meter at full, next to a stopwatch
Password Generator

Get a password no brute-force attack can finish

Generate a random password up to 64 characters and see its entropy and estimated crack time right away.

Generate a passwordRuns in your browser

Frequently asked questions

At one trillion guesses a second, a random 8-character password using all 95 keyboard characters falls in about 55 minutes on average. With lowercase letters only, it falls in under a second. If the password is a word or a known leak, it goes even faster, because attackers try those first.

A random 12-character password with letters, numbers and symbols would take about 8,600 years at a trillion guesses a second. That is solid for most accounts. A 12-character password you made up, built from words and dates, can fall much faster. For important accounts, 16 random characters is the safer target.

Length. Each extra character multiplies the work by the size of the character set, about 95 times for a full keyboard mix. Moving from lowercase to all 95 characters multiplies it by only about 3.7 per character. A few extra characters beat adding symbols, though using both is best.

Only for random passwords. Most calculators count length and character types and assume every character was picked at random. Real attackers start with leaked passwords, dictionary words and common patterns, so a human-chosen password usually falls much sooner than its estimate. Treat the result as a best case, not a guarantee.

Yes, if the words are chosen at random. With the 7,776-word EFF diceware list, each word adds about 12.9 bits. Six random words give about 77 bits, roughly 3,500 years at a trillion guesses a second. Words you pick yourself, like a song lyric, are far weaker.