Keystrokes Per Minute: How KPM Relates to WPM and KPH
By Mark Fulton · · Last verified

Keystrokes per minute (KPM) is the number of keys you press in sixty seconds, and it converts to words per minute with one rule: KPM = WPM × 5, because a typing test counts one "word" as five keystrokes, spaces included. So 60 WPM is 300 KPM, 40 WPM is 200 KPM, and 100 WPM is 500 KPM. To go from KPM to keystrokes per hour (KPH), multiply by 60. The conversion is exact. What varies from site to site is what each one counts as a keystroke, and that is why two tools can show you two different KPM figures for the same minute of typing.
Run a one-minute test and read your CPM on the result screen, free, no signup. It shows WPM, CPM and KPH side by side so you can check every number in this guide against your own run.
What are keystrokes per minute?
KPM counts every key press that produces output over a one-minute window. Letters, digits, punctuation and the space bar all count. A typist who produces 250 characters of text in a minute has typed 250 keystrokes per minute, which is 50 WPM on the standard definition.
The reason the conversion is a clean multiplication is that WPM is not really a count of words. Real words vary in length ("a" versus "extraordinary"), so typing tests agree to treat a word as five characters. The Wikipedia entry on words per minute states the convention directly: the word is standardized to five characters or keystrokes in English, including spaces and punctuation. That one agreement is what ties WPM, KPM, CPM and KPH into a single family of units.
Think of it as the same speed written at four different resolutions:
- WPM is the coarse one, a two-digit number for most people.
- KPM and CPM are five times finer, a three-digit number.
- KPH is the same thing stretched across an hour, a five-digit number.
Nothing about your hands changes between them. If you want the full walk through of how the word-based figure is built and where gross and net come apart, how WPM is calculated covers it step by step.
Do spaces and backspaces count as keystrokes?
Spaces count. Backspaces are where sites disagree, and it is the main reason one tool's KPM does not match another's.
There are three common ways a typing tool can count:
- Every physical key press. Letters, spaces, Backspace, Shift, everything. This is the truest meaning of "keystroke" and the one that inflates the number for a typist who corrects a lot, since each correction costs two presses (the wrong key and the Backspace) before the right one.
- Characters that end up in the text. Corrected mistakes disappear, so the count reflects the output rather than the effort.
- Only correct characters. Anything wrong is excluded entirely.
None of these is wrong. They answer different questions. The first measures finger activity, the second measures output, the third measures clean output. When someone says their KPM is "300" and a friend's tool says "270" for the same minute, the gap is usually a counting rule, not a difference in typing.
Shift and other modifier keys are a smaller wrinkle. A capital letter takes two physical presses but produces one character, so tools built on the physical count and tools built on the character count drift apart on text with a lot of capitals, symbols and code.
The practical takeaway is to compare numbers only when they come from the same counting rule. If you track your own progress, stay on one tool and one unit. If an employer quotes a number, ask or check which basis it uses before you compare it to your own.
What does TypeTimer's result screen actually count?
TypeTimer's result screen shows several figures that are easy to mix up, so here is exactly what each one is, taken from how the app computes them:
- Gross WPM takes every character in the text you typed, spaces included, divides by 5, and scales to a minute.
- KPH is that same character count scaled to an hour. It sits on the gross basis, which means it is gross WPM times 300, and a posting that quotes KPH usually means this raw basis too.
- CPM is different: it is the number of correct characters per minute. The app adds up the characters you typed correctly, plus the spaces that ended a correctly typed word, and scales that to a minute.
- Net WPM, the headline figure, starts from gross WPM and subtracts one word per minute for each uncorrected error still on screen when the test ends.
So on TypeTimer, CPM and KPM are close relatives but not identical. KPM by the plain definition counts everything you typed. CPM counts only what you typed right. On a clean run with no mistakes, the two land on the same number. On a messy run, CPM comes in lower, and the gap tells you how much of your speed was wasted on errors.
A quick example. Say you type 300 characters in a minute and 12 of them are wrong. Your gross figure is 300 characters per minute, which is 60 gross WPM. Your CPM is 288, because only the correct characters count. The 12 uncorrected errors then pull net WPM down from 60 to 48. Same minute of typing, three different numbers, each one honest about a different thing.
Because the corrected mistakes are removed from the text as you fix them, a corrected typo does not drag CPM or net WPM down the way a mistake you leave in does. That is deliberate: it rewards fixing errors, which is what a data entry job wants.
How do KPM, CPM, WPM and KPH convert?
Everything runs through the same factor of five, and then a factor of sixty for the hour. This table uses the gross, characters-in-the-text basis, so KPM and CPM are equal at 100% accuracy:
| WPM | KPM (WPM × 5) | KPH (KPM × 60) | Where you usually see this unit |
|---|---|---|---|
| 20 | 100 | 6,000 | Beginner touch typing practice |
| 27 | 133 | 8,000 | Lower end of common data entry bars |
| 33 | 167 | 10,000 | A common data entry posting figure |
| 40 | 200 | 12,000 | Clerical and administrative screens |
| 50 | 250 | 15,000 | Office work, customer support chat |
| 60 | 300 | 18,000 | Strong general typing speed |
| 70 | 350 | 21,000 | Transcription and heavy writing roles |
| 80 | 400 | 24,000 | Fast typists |
| 100 | 500 | 30,000 | Elite speed, competitive typing |
Rows at 27 and 33 WPM are rounded; 8,000 KPH is exactly 26.7 WPM and 10,000 KPH is exactly 33.3 WPM. The reverse direction is just as short. Divide KPM by 5 to get WPM, and divide KPH by 300.
Which unit shows up depends on the kind of work:
- Prose and office jobs quote WPM. The text is sentences, so a word-based unit fits.
- Data entry and numeric keypad jobs quote KPH. The work is fields and numbers, and a keystroke is the smallest unit of it. The Wikipedia entry above notes that numeric entry is measured in keystrokes per hour, and that many jobs require a certain figure, often 8,000 or 10,000.
- KPM and CPM turn up mostly inside tools, glossary pages and non-English tests. Character counts translate across languages better than "words" do, which is why some tests report characters per minute.
If you need the hour-based conversion in more depth, with the full table both directions, see WPM to KPH. For the benchmark side of the hourly unit, what is a good KPH lays out the bars employers actually set.
What is a good KPM?
Since KPM is WPM times five, a good KPM is whatever a good WPM is, with the digits rescaled. The ranges below follow the same bands used across this site:
- Under 150 KPM (under 30 WPM): a learning speed. Fine for starting out, below most job bars.
- 150 to 200 KPM (30 to 40 WPM): functional. This meets the entry bar on many data entry and clerical postings.
- 200 to 300 KPM (40 to 60 WPM): solid for office work and the range most working adults sit in.
- 300 to 400 KPM (60 to 80 WPM): fast, comfortable for heavy writing and transcription work.
- Above 400 KPM (80+ WPM): very fast. Useful, but past this point accuracy usually matters more than extra speed.
Two honest caveats apply to any KPM figure. The first is the counting basis from earlier: a KPM that counts Backspace and Shift is not the same as one that counts output only. The second is test length. Speed measured over one minute is nearly always higher than speed held for five, because a sprint hides fatigue. If the number is going to be used for something that matters, test it over a longer window as well. The comparison of short and long runs is in 1-minute vs 5-minute typing tests.
The best evidence on how people actually type comes from large datasets rather than guesses. The Aalto University study Observations on Typing from 136 Million Keystrokes analyzes keystroke-by-keystroke data from a very large online typing test, and it is a good place to see how typing behavior varies from one person to the next. The useful lesson for anyone chasing a KPM target is that speed is a spread across a population, not a single bar to clear.
For work that is mostly numbers, the target changes shape. A keypad role cares about keystrokes per hour at a low error rate, not prose speed, and the practice approach differs too. The 10-key typing test guide covers that case, and there is a 10-key practice page to train on.
Which unit should you report to an employer?
Report the unit the employer used, on the basis they used, and add accuracy.
- If the posting says WPM, give net WPM and your accuracy percentage. Net is the safer number to quote because it already accounts for errors.
- If the posting says KPH, give KPH and say it came from a keystroke test. Do not convert a prose typing speed to KPH and present it as numeric entry speed. The two skills overlap but are not interchangeable, and a keypad test is the honest proof for a keypad job.
- If the posting says only "typing speed" or gives no unit, use WPM. It is the unit every recruiter reads without a second thought.
- If you only have KPM or CPM, convert it to WPM (divide by 5) and state the WPM, so nobody has to do the arithmetic.
Whichever you pick, the number is more convincing when someone else can check it. A self-reported figure is just a claim. TypeTimer's verified typing certificate gives a result a recruiter can confirm through a public lookup, rather than taking your word for it. One honest limit: an online certificate, ours included, is not a proctored test, so where a job requires an in-person or agency-administered exam, you will still sit that exam. For most private-sector screens, a checkable result beats a typed number on a resume.
Why do typing sites count keystrokes differently?
Because there is no single standard for what a keystroke is, only for what a word is. The five-characters-per-word convention is widely shared. How a tool treats Backspace, Shift, errors, auto-corrected words and non-printing keys is a design choice each site makes for itself. A tool built to measure finger activity counts raw presses. A tool built to rank competitors on clean output counts only correct characters. A tool built for data entry practice counts gross keystrokes so the figure matches what employers quote.
Add a couple of structural differences on top: the text itself (common words versus random characters or code), the test length, and whether the clock starts on the first key or on a countdown. Each one shifts the result by a few percent, and together they explain most of the gap between your scores on different sites. The long version of that story is in why your WPM differs on every typing test.
None of this makes any one tool wrong. It means the useful habit is to pick a basis, stick to it, and compare like with like.
Check your own numbers
The fastest way to make this concrete is to run one test and do the arithmetic yourself. Take the WPM on your result screen, multiply by 5, and see whether it lands near your CPM. If CPM comes in lower, the difference is your uncorrected errors, and reducing those is usually the quickest route to a higher net score. Multiply WPM by 300 and you should land on your KPH.
FAQ
How many keystrokes per minute is 60 WPM?
60 WPM is 300 keystrokes per minute, because KPM = WPM × 5. Over an hour, that is 18,000 keystrokes.
Is KPM the same as CPM?
Close, but not identical. KPM counts keystrokes and CPM counts characters, and on a clean run with no errors they match. On TypeTimer, CPM specifically counts only correct characters (plus the spaces after correct words), so on a run with mistakes your CPM comes in below your gross keystroke total.
What is a good KPM for data entry?
Many data entry postings quote KPH rather than KPM, often 8,000 or 10,000 keystrokes per hour. Divide by 60 to get KPM: 8,000 KPH is about 133 KPM, and 10,000 KPH is about 167 KPM. Accuracy requirements usually matter as much as the speed.
Why do typing sites count keystrokes differently?
There is a shared convention for how many characters make a word, but not for how to treat Backspace, Shift, errors and corrections. Each site decides, so the same minute of typing can produce different KPM figures on different tools.
See your KPM, CPM and KPH on one screen
Take a one-minute test on the WPM test and read the CPM figure on your result screen, then check it against the conversion table above. When you want a number a recruiter can verify, add a verified certificate for $4.99.