Multiply by 300. KPH = WPM × 300, because a typing test defines one "word" as 5 characters and there are 60 minutes in an hour, so 5 × 60 = 300. A 40 WPM typist produces 12,000 keystrokes per hour; a 60 WPM typist produces 18,000. Going the other way, WPM = KPH ÷ 300, so a posting asking for 10,000 KPH is asking for roughly 33 WPM. The arithmetic is exact and takes one line. The interesting question is whether the resulting number actually describes you, and that depends entirely on whether the keying you'll be doing looks like sentences or looks like a numeric keypad.

Skip the arithmetic and measure it directly: the free KPH typing test reports keystrokes per hour and WPM from the same five minute run.

What is KPH in typing?

KPH stands for keystrokes per hour: the number of individual key presses a typist makes in sixty minutes. Every key counts, letters, digits, spaces and punctuation alike, and on some tests Tab and Enter too. It's the unit data entry employers use because their work is measured in records and fields rather than sentences, and a keystroke is the smallest unit of that work. For the bars those employers actually set, see what is a good KPH.

WPM, words per minute, measures the same activity in a different unit. The only reason the two look unrelated is scale: a respectable typing speed is a two-digit number in WPM and a five-digit number in KPH. They are joined by one fixed conversion factor, which the next section derives.

How do you convert WPM to KPH?

The conversion runs through one intermediate unit, keystrokes per minute:

KPM = WPM × 5 (five characters per nominal word, spaces included)
KPH = KPM × 60 (sixty minutes in an hour)
Collapse the two steps: KPH = WPM × 300

Worked through with a real number. You finish a test at 52 WPM:

52 × 5 = 260 KPM
260 × 60 = 15,600 KPH

And in reverse, when a job posting hands you a KPH figure and you want to know what it means in the unit you're used to:

WPM = KPH ÷ 300
9,000 ÷ 300 = 30 WPM
12,000 ÷ 300 = 40 WPM

That is the whole formula. There's no rounding trick, no industry adjustment factor, and no separate table you need to look up. Every KPH figure in the table below is produced by that single multiplication, so you can check any row of it in your head.

The full conversion table

WPM	KPM (WPM × 5)	KPH (WPM × 300)	Where this lands against published requirements
20	100	6,000	Short of every published data entry bar cited on this page
25	125	7,500	Clears the 7,000 KPH floor in a State of Hawaii data entry recruitment, short of the 8,000 KPH county entry bar
30	150	9,000	Clears the 8,000 KPH entry bar in the San Luis Obispo County data entry series, short of its 10,000 KPH journey bar
35	175	10,500	Clears both that 10,000 KPH journey bar and the 7,000 KPH floor in a State of Hawaii data entry recruitment
40	200	12,000	Matches the senior 12,000 KPH bar in that same county series, and matches CalHR's 40 WPM certification minimum
45	225	13,500	Above every clerical bar cited on this page
50	250	15,000	Above every clerical bar cited on this page
55	275	16,500	Above every clerical bar cited on this page
60	300	18,000	Comfortably above clerical bars; the binding constraint at this level is accuracy, not speed
65	325	19,500	Comfortably above clerical bars
70	350	21,000	Comfortably above clerical bars
75	375	22,500	Comfortably above clerical bars
80	400	24,000	Comfortably above clerical bars
90	450	27,000	Comfortably above clerical bars
100	500	30,000	Comfortably above clerical bars

Any WPM that isn't in the table converts the same way. 32 WPM is 32 × 300 = 9,600 KPH. 47 WPM is 14,100 KPH. 72 WPM is 21,600 KPH. There is no rounding in any of it.

Two things to hold onto while reading it. First, the KPH column is arithmetic, not measurement: it says what your prose rate would come to if expressed hourly, not what a keying test would actually record. Second, the right-hand column compares against real published figures (sourced further down), and those figures are numeric production rates. A prose WPM that converts past a numeric bar has not cleared that bar. It has only shown you're in the neighbourhood.

KPH to WPM chart

Job postings usually hand you the KPH figure, so this is the direction most people actually need. Divide by 300, and round to one decimal place.

KPH requirement	KPM (KPH ÷ 60)	WPM equivalent (KPH ÷ 300)
6,000	100	20
7,000	117	23.3
8,000	133	26.7
9,000	150	30
10,000	167	33.3
11,000	183	36.7
12,000	200	40
13,000	217	43.3
14,000	233	46.7
15,000	250	50
16,000	267	53.3
18,000	300	60
20,000	333	66.7

The pattern worth noticing: every common clerical KPH bar lands between about 23 and 47 WPM. Those are modest prose speeds. That is exactly why the numeric keypad caveat below matters so much, because the bar is low in prose terms and much harder in keypad terms.

How do you calculate keystrokes per hour from a test?

If you have a result in hand rather than a requirement, pick the route that matches what your test reports:

Your test reports WPM: multiply by 300. 45 WPM becomes 13,500 KPH.
Your test reports CPM (characters per minute): multiply by 60. 240 CPM becomes 14,400 KPH. This is the more honest route, because it uses characters you actually typed rather than the nominal five-character word.
You timed yourself on a batch of records: count every keystroke in the batch, divide by the minutes it took, and multiply by 60. 1,200 keystrokes in 6 minutes is 200 per minute, or 12,000 KPH.

The third route is the closest to how an employer scores a production test, and it's the only one that captures the reading and field-to-field movement real keying involves.

Where does the ×300 rule come from?

The 300 is built entirely out of the 5-character word, so it's worth knowing that convention isn't a shortcut typing sites invented. WPM never counted actual words. If it did, a passage full of "a", "to", and "it" would score triple a passage full of "keyboard" and "understand", and no two test results would ever be comparable. So the typewriter era standardized the word away and replaced it with a fixed unit: five characters, spaces included. Type 300 characters in a minute, of any kind, and you typed 60 "words".

That convention is what makes the two units convertible at all. KPH counts raw keys. WPM counts keys divided by five. Multiply the divided number back up by five and you're in keystrokes per minute; multiply by sixty and you're in keystrokes per hour. Nothing else happens in the formula. We covered the gross and net variants of the underlying maths in how WPM is calculated, and the same five-character definition is doing the work there too.

It's also worth being honest about what that convention smooths over. Typing is not a uniform activity across people. The largest published study of typing behaviour, Observations on Typing from 136 Million Keystrokes (Aalto University and University of Cambridge, CHI 2018), collected data from 168,000 volunteers and found that typists sort into eight distinguishable style categories, with overlapping keypresses far more common than expected. A single multiplier flattens all of that into one number. That's fine for orientation. It's not a measurement.

When does the conversion mislead you?

Four situations, and the first one accounts for most of the confusion people run into.

Numeric keying is a different exercise. Data entry roles that quote KPH usually mean numeric work: invoices, claims, account codes, batches of figures entered on a ten-key pad. That's one hand on a small cluster of keys rather than ten fingers across a full board, and there are no spaces padding the keystroke count the way prose has. Your sentence-typing speed says very little about it. Converting 60 WPM into 18,000 KPH and putting that on an application for a keypad role is claiming something the number doesn't support. Ten-key testing and its own benchmarks are a separate skill with a separate ceiling. Mechanical and membrane keyboards change the feel of that work far less than people hope, a point we checked against the research in mechanical vs membrane keyboards.

Gross and net get compared by accident. KPH is very often reported gross, with an error rate stated separately alongside it ("8,000 KPH at 99% accuracy"). WPM benchmarks are usually net, with uncorrected mistakes already subtracted. Convert a net WPM up to KPH and compare it against a gross KPH requirement and you've quietly compared two different quantities, in the direction that flatters you. The general version of this problem is why your WPM differs on every typing test.

Navigation keys may or may not count. Real keying means Tab or Enter between fields, sometimes on every record. Some scoring engines count those presses, some don't. On short numeric records that difference moves a score by a noticeable margin, which is one reason the same person gets two different KPH figures from two different tools.

KPH names an hour it never measured. A one-minute test extrapolated by ×300 assumes you'd hold that exact pace for sixty consecutive minutes. Nobody does. Production keying includes reading source documents, resolving ambiguous handwriting, and correcting rejected batches, so the hourly rate an employer has in mind is a sustained shift average rather than a burst. A longer test gets you closer to an honest figure, which is the whole argument in 1 minute vs 5 minute typing tests.

What KPH do data entry postings ask for?

Published class specifications are far more informative than general internet advice here, because they show the bar as a ladder rather than a single number. San Luis Obispo County's Data Entry Operator class specification sets three:

Data Entry Operator I: 8,000 keystrokes per hour in production mode, error factor not to exceed 1%
Data Entry Operator II: 10,000 keystrokes per hour, error factor not to exceed 0.7%
Data Entry Operator III: 12,000 keystrokes per hour, error factor not to exceed 0.35%

Notice what happens across that span. Speed rises by half, and the permitted error factor tightens to roughly a third of what it was. Speed alone doesn't move you up the ladder.

Floors are often lower than people expect. A State of Hawaii Data Entry Operator I recruitment for Oahu asked candidates to self-certify the ability to key at a minimum of 25 records or 7,000 keystrokes per hour with an error rate of no more than 10%, a bar that converts to around 23 WPM. And plenty of employers don't name a number at all: Colorado's state Data Entry class description simply notes that some positions in the series may be expected to maintain a specified number of keystrokes per hour, with an intern level that exists specifically for people who haven't hit the agency's keystroke standard yet.

One important limit, stated plainly. Some employers don't accept a converted figure or a self-administered result of any kind. California's typing certification requirements call for a minimum of 40 net WPM from a five-minute test that was proctored either virtually or in person, and CalHR will not accept certifications from tests that weren't proctored or ran shorter than five minutes. No online certificate satisfies that, ours included, and we walked through exactly how California's process works in how to get a California typing certificate. What satisfies it is an actual proctored sitting, arranged through the hiring agency or another state department. Where a posting says proctored, take the proctored test. Everything on this page is for the much more common case where an employer wants a credible starting figure and will run their own assessment later. Typing speed requirements for jobs covers which roles fall into which camp.

How do you measure KPH directly instead?

If you want a keystroke figure that came from your hands rather than from a multiplication, measure characters and scale those.

Take a test, then read the CPM figure on the results screen. CPM is characters per minute, and multiplying it by 60 gives you keystrokes per hour derived from what you actually typed, rather than from a nominal five-character word. On TypeTimer, CPM counts correct characters, so the resulting hourly figure is already a net one. That's the conservative direction to be wrong in, and it's the figure you can defend if someone asks how you got it.

To make the sample resemble the work, turn on the numbers toggle in the test options before you start. That mixes digits into the text instead of running pure prose, which pulls the result closer to what mixed alphanumeric keying feels like. It still isn't a numeric keypad test, and you should say so if you quote the number.

Then report it precisely. "14,400 KPH derived from 240 CPM over a 5 minute mixed alphanumeric test, 98% accuracy" is a sentence a hiring manager can evaluate. "Fast typist" is not. And if the posting asked for KPH while you only have WPM, convert it, label it as a conversion, and be ready to sit their test.

Run a WPM test with numbers switched on, note the CPM on your result card, and multiply by 60. That's your keystrokes per hour, measured rather than inferred, in about the time it takes to read this paragraph.

Frequently asked questions

What is 60 WPM in keystrokes per hour?

18,000 KPH. The working: 60 × 5 = 300 keystrokes per minute, and 300 × 60 = 18,000 keystrokes per hour. That figure sits well above the clerical requirements quoted above, though it describes prose output rather than numeric keypad output.

What is 40 WPM in keystrokes per hour?

12,000 KPH. 40 × 5 = 200 keystrokes per minute, and 200 × 60 = 12,000. That matches the top rung of the San Luis Obispo County data entry ladder, though that bar is set for production keying with a tight error ceiling.

What is 8,000 KPH in WPM?

About 26.7 WPM. 8,000 ÷ 300 = 26.67. It's a common entry-level data entry requirement, and in prose terms it is a modest speed. The difficulty sits in hitting it on numeric records with the error rate the posting attaches.

How do you calculate keystrokes per hour?

Multiply WPM by 300, or multiply CPM by 60. If you're timing yourself on real records, count total keystrokes, divide by minutes taken and multiply by 60. The CPM route is the more accurate of the first two because it uses characters you actually typed.

Is 10,000 KPH good?

It's a solid mid-range clerical figure and it clears most published entry bars. It converts to roughly 33 WPM. In the San Luis Obispo County ladder it corresponds to the journey-level Data Entry Operator II standard, one step above entry. Whether it's good for a particular posting depends on the accuracy requirement attached to it, because that's where those specifications tighten hardest as the levels rise.

Why is my 10-key KPH lower than my converted WPM?

Because they're measuring different things. Prose typing spreads work across ten fingers and gets a free keystroke from every space, which is a significant share of the total in ordinary text. Numeric keypad entry uses one hand on a small key cluster, has no spaces to pad the count, and often includes Tab or Enter presses between fields that some scoring engines don't credit. The gap isn't an error in your typing or in the formula. It's the formula being applied outside the conditions it describes.

Do employers use KPH or WPM?

Both, split roughly by job family. Clerical, administrative, and general office roles almost always state WPM. Dedicated data entry, claims processing, medical billing, and accounts payable roles state KPH, usually paired with a maximum error rate. When a posting names one unit, answer in that unit and note which test produced the number. Converting silently and presenting the result as measured is the one thing worth avoiding. Legal and medical support roles are a good example of postings that name WPM but test for accuracy just as hard, which we covered in legal secretary typing speed.

WPM to KPH and KPH to WPM: Data Entry Conversion Chart