"What is a good typing speed?" sounds like it should have one answer. It does not. A speed that feels excellent for casual email may be too slow for a timed data-entry screen, and a speed that looks impressive on a test is useless if accuracy collapses under pressure.
This guide explains how to think about "good" in practical terms: common WPM bands you will see in typing guides and job posts, why accuracy belongs in the same conversation, and how to pick a target that fits your work instead of chasing someone else's number.
There is no single official "good" WPM
No global authority publishes an official good typing speed for everyone. Schools, employers and online tests set their own bars. Typing websites often group scores into bands such as beginner, average, above average and fast so you can place yourself roughly on a map.
Treat those bands as rules of thumb, not measured statistics from a single large study. Different tests use different text difficulty, durations and error rules, so the same person can land in different bands depending on how they are measured. For a deeper look at why published "averages" disagree, see average typing speed.
The useful question is not "what is the good speed?" It is "what speed (and accuracy) do I need for the task in front of me?"
Practical WPM bands many guides use
The ranges below mirror the kind of labels you will see on WPM charts and practice sites. They are for orientation. Always confirm any figure a school or employer actually requires.
| Rough band | About this WPM | How people often use it |
|---|---|---|
| Beginner / slow | Under ~30 | Still learning the keyboard or hunting and pecking |
| Everyday / average | Mid-30s to mid-40s | Comfortable for email, notes and light computer work |
| Solid / above average | Roughly 50–60 | Comfortable for most office writing and many job screens |
| Fast | Roughly 70–80+ | Strong for heavy writing, coding notes or competitive practice |
| Very fast | 90+ | Rare for casual users; more common among dedicated typists |
If your own WPM chart page uses slightly different cutoffs, follow that chart when you compare scores from this site. Consistency of method matters more than matching every site's labels.
What employers and tests often look for
Job posts and screening tests usually care about a minimum, not a vague "good." Requirements vary by role and by country, but a few patterns show up often:
- General office or admin work. Many postings ask for a comfortable working speed plus high accuracy. Figures in the mid-40s to around 60 WPM appear frequently, but the posting is the only number that counts.
- Data entry and transcription-style roles. Speed targets are often higher, and error rules are stricter. Net WPM (speed after subtracting mistakes) matters more than a flashy gross score. Our guide to typing speed for data entry jobs covers how those tests usually work.
- School or certification screens. Follow the stated duration, text type and whether backspace is allowed. A "good" classroom score is whatever meets that rubric.
If a posting does not list a number, aim for a speed you can sustain for several minutes with accuracy that would not need heavy cleanup. Employers hire usable output, not a one-minute peak.
Test your typing speed free — 60 seconds to your WPM and accuracy.
Open the free typing speed test →Accuracy is part of "good"
A high WPM with low accuracy is not a good typing speed for real work. Every mistake costs time to find and fix, and on many formal tests wrong characters reduce your score.
A practical way to judge a run:
- Note WPM and accuracy together.
- Prefer a slightly lower WPM with high accuracy over a higher WPM full of fixes.
- When accuracy is solid (many people aim near the high 90s on practice tests), then push for more speed.
If you rush and accuracy drops, slow down until clean typing returns, then add speed again. That cycle beats forcing faster runs that teach bad habits.
How to decide what is good for you
Use this short checklist instead of a universal number:
- Name the use case. Emails? Essays under a clock? Customer chat? Job screening? Coding comments?
- Check for a required number. If a syllabus or job post states a target, that is your definition of good.
- Measure yourself the same way every time. Same keyboard, same difficulty mode, same test length. Warm up once, then take a few timed runs and average them.
- Set a near-term goal. Moving from the high 30s to the low 50s is often more useful than dreaming about 100 WPM overnight.
- Pair the goal with accuracy. For example: "55 WPM at 97% or better on a 60-second Medium test."
Worked example: setting a personal target
Suppose you take three 60-second Medium tests after a warm-up and score:
| Run | WPM | Accuracy |
|---|---|---|
| 1 | 44 | 96% |
| 2 | 47 | 98% |
| 3 | 45 | 97% |
Your mean speed is (44 + 47 + 45) ÷ 3 = 45.3 WPM, with accuracy already strong. A sensible next goal might be 50–55 WPM while keeping accuracy at or above 96%. That is "good" relative to where you are now, even if someone else is chasing 80 WPM.
If a job posting later asks for 60 WPM with high accuracy, raise the target to match that screen and practice under the same rules the employer will use.