Average Typing Speed by Context
“Good” typing speed depends entirely on what you're comparing it to.
“What's a good WPM?” doesn't have one honest answer — it depends entirely on who you're comparing yourself to. A number that's impressive for casual typing is unremarkable for a professional transcriptionist, and competitive typists operate in a range that would be a career-defining skill anywhere else. The ranges below are the commonly cited bands for each context; treat them as orientation, not a certificate.
By context
| Context | Typical range (WPM) |
|---|---|
| General population, casual typing | 30–45 |
| Average office / knowledge worker | 40–65 |
| Professional typist / data entry | 60–80 |
| Programmer (sustained, real code) | 40–70 |
| Transcriptionist / court reporter | 75–100+ |
| Competitive typist (top percentile) | 120–150+ |
These are broad, widely-cited bands rather than results from a single controlled study — typing-speed research uses inconsistent test lengths, text difficulty, and error penalties, so exact figures vary by source. Use them as a rough compass, not a leaderboard.
Why programmers often type “slower” than expected
Programmer WPM looks low next to office-worker WPM, and that's not a skill gap — it's a different task. Code isn't prose: it's dense with punctuation, symbols, and pauses to think about what to write next, all of which a raw-prose WPM test doesn't measure. A programmer who tests at 55 WPM on plain text may still type code faster, in practical terms, than someone who tests higher but hesitates constantly over unfamiliar symbols and indentation.
Why these numbers vary so much between sources
- Test length. Short bursts (15–30s) tend to read higher than sustained multi-minute tests, since fatigue and error-correction haven't caught up yet.
- Text difficulty. Common English words are faster to type than random text, numbers, or unfamiliar punctuation — comparing scores from different text sources isn't really comparing the same thing.
- Net vs. raw WPM. Raw WPM ignores mistakes; net WPM (the number that actually matters) subtracts them. A score reported without saying which one it is can't be compared fairly to another score — HeroTyping always shows both, separately, on the results screen.
What actually matters more than the number
A single WPM score is a snapshot, not a skill level — it swings with the text, your focus, and even the time of day. Consistency (how even your pace is across an entire test, not just your peak burst) and accuracy are better long-term signals of real ability than any one result. HeroTyping tracks both alongside WPM on every results screen for exactly this reason: chasing a single peak number tends to encourage exactly the rushed, error-prone typing that slows you down in practice. If you want to actually move your baseline rather than just your best run, start with how to improve your typing speed — accuracy first, speed follows.
Test yourself
Numbers on a page are easy to skim past. Take a typing test under the same conditions a few times (same duration, similar text type) before comparing your result to any of the ranges above — a single test tells you less than a short streak of them.