Is 60 WPM good?

60 words per minute is a good typing speed. It sits around 50% above the commonly cited adult average of roughly 40 WPM, and it clears the requirement of essentially every job that states one. It is not a fast speed in competitive terms — that conversation starts north of 100 — but it is the speed at which typing stops being something you have to think about.

Is 60 WPM fast, or just fine?

Both, depending on the room. Among the general population 60 is quick enough to be noticed: you will be visibly faster than most colleagues, and nobody will ever wait on your typing in a meeting. Among people who type competitively it is entry level, because that group self-selects for speed and starts around 100.

The reason the question feels ambiguous is that both answers get quoted without their context. A 60 that came from a common-word test is a different 60 from one measured on real prose with punctuation, and a competitive typist quoting "only 60" is measuring against a very unusual peer group.

What changes at 60

This is where the tax disappears. Below about 50 WPM there is a persistent gap between finishing a thought and finishing the sentence that carries it, and that gap quietly shapes how you write — people who type slowly write shorter emails, skip the second draft, and avoid long-form replies without ever deciding to.

At 60 that mostly closes. The bottleneck moves from your hands to your head, which is where it should be. Getting faster still helps, but from here it stops changing what you are willing to write.

Where 60 WPM stands

• Roughly 50% above the ~40 WPM adult average.
• Above the 35–45 WPM most administrative job listings ask for.
• Below the 80–100 band where typing speed starts being someone's hobby rather than a side effect.
• Comfortably proficient. Not competitive, and there is no shame in that — most people never measure at all.

Is 60 WPM bad for a programmer?

No, and the premise is worth pushing back on. Writing code is not a sustained typing exercise: it is bursts of typing separated by thinking, navigating and reading, and the constraint is almost never characters per minute. Plenty of extremely good engineers type around 60.

Where speed does show up is in the surrounding work — messages, documentation, review comments, incident notes — which is most of the writing a working day actually contains.

Can you win a typing race at 60 WPM?

Yes, against other 60 WPM typists, which is who you would be racing. TypeBag's paid tiers use per-tier Glicko-2 ratings plus a global MMR, so matchmaking brackets you with players at your own speed rather than against the top of the ladder. You need to beat people who type like you, not the record holder.

Inside a bracket, accuracy decides more races than speed does. A mistyped character has to be corrected before the passage continues, so a clean 60 regularly beats a scrappy 68. That is the single most useful thing to know at this level, and it is why slowing down slightly often wins more.

Getting from 60 to 80

This is the most improvable stretch on the whole ladder, and it usually comes down to three things:

• Looking down. Even occasional glances cost more than people expect, because each one costs re-finding your place as well as the glance itself.
• Punctuation and capitals. Most self-taught typists never learned proper shift and symbol fingerings, so the rate collapses on real prose while staying fine on plain words.
• Correcting mid-word. Hammering backspace on reflex costs more time than the original error. Fixing errors deliberately is faster than fixing them fast.

All three are drillable, which is why 60 to 80 responds better to practice than any later jump. Past 100 the gains come from rhythm and error prevention and get considerably harder to find.

The honest test of a 60 is a race against another person on text you have never seen, which is harder than any solo test and tells you more. A free TypeBag duel takes under a minute, is unrated, and needs no account; try one.