Keystrokes per hour test

What keystrokes per hour actually measures

KPH counts keystrokes, not words. Every character you type is one keystroke, and so is every backspace, delete and tab you press to fix something. It is a measure of how much work your hands do at a keyboard, which is why data-entry and clerical roles ask for it instead of words per minute: their work is account numbers, addresses, part codes and dollar amounts, where “words” is not a meaningful unit at all.

Nobody is measured for an hour. A KPH figure is always a short sample extrapolated: type for a minute, multiply by sixty. That is what the test on this page does, and it is what the test at a staffing agency does. It also means the number is sensitive to how the sample went — one fumbled record inside sixty seconds moves it more than it should, so run the test two or three times and quote the middle result rather than your best one.

KPH to WPM: the conversion, and the arithmetic behind it

The conventional divisor is five characters per word. It comes from typewriter-era testing, where a “word” was standardised at five keystrokes including the space, and it is still the basis of every typing test that reports WPM. That gives two formulas:

• WPM = KPH ÷ 300 — five characters per word, sixty minutes per hour.
• KPH = WPM × 300 — the same relationship in the other direction.

So 8,000 KPH is about 27 WPM, 10,000 KPH is about 33 WPM, and a 40 WPM typist is a 12,000 KPH typist on paper. The converter above does this in both directions without needing you to run the test — which is the right tool if you already know your typing speed and an application has just asked for a KPH figure.

One honest caveat about that conversion. Prose and data are not equally hard. A 40 WPM typist measured on ordinary English will usually not sustain the equivalent 12,000 KPH on records full of digits, capitals and punctuation, because those need the number row, the shift key and constant precision. If a job specifies KPH, measure with data, not with paragraphs. That is why the corpus in this test is names, street addresses, invoice numbers, dates and amounts rather than a passage of writing.

What KPH employers ask for

The ranges in the table above are the figures that appear in job postings — what employers ask for, not measured statistics about how fast people actually type, and not a benchmark we are asserting. They are worth knowing because they tell you what number makes an application competitive rather than what number makes you average.

A few patterns hold across listings. General office and clerical roles tend to ask for the least, and often state the requirement in WPM instead. Dedicated data-entry roles state KPH and usually pair it with an accuracy threshold. High-volume production entry — claims processing, medical billing, logistics — asks for the highest alphanumeric figures. And 10-key numeric entry is quoted separately: a numeric-keypad KPH figure and an alphanumeric KPH figure are different measurements, and a listing that wants both will say so. If a posting gives a single number with no context, it almost always means alphanumeric.

Accuracy is usually the real gate. Many listings that ask for 8,000 KPH also ask for 98% accuracy, and in that pairing the accuracy is the harder requirement. A fast operator who introduces errors into a billing system costs more than a slow one, which is why the test above reports an accuracy-adjusted figure alongside the raw one. That adjusted number is the one worth quoting to yourself; quote the raw one only if the employer defines KPH as raw.

How this test counts

No test is meaningful unless you know its rules, so here are all of them:

• The clock starts on your first keystroke and runs for 60 seconds. There is no countdown to sit through and no penalty for reading the first record before you start.
• Every keystroke counts, corrections included. Printable characters, backspace, delete and the Enter that submits a record. Correcting a typo genuinely costs you three keystrokes in real data entry, so it counts as three here.
• Modifier combinations do not count. Ctrl, Cmd and Alt shortcuts are not keying, so they are ignored. Shift is not counted separately either — a capital letter is one keystroke, matching the convention every KPH test uses.
• Pasting is disabled. A pasted record is not a keystroke measurement.
• Accuracy is per character against the source record. A record you submitted is scored over the longer of what you typed and what was there, so skipping half of one costs you. The record you were mid-way through when the clock stopped is scored only over what you had typed — the rest was not an error, time simply ran out.
• Runs under five seconds are not scored. Extrapolating a two-second burst to an hour produces a number in the hundreds of thousands, which is arithmetic rather than a measurement.
• Nothing leaves your browser. No account, no upload, no result stored anywhere. Reload the page and it is gone.

A test at an employer may differ in the details — some count only correct keystrokes, some use a longer sample, some use their own software with a numeric keypad. Take your result here as a good estimate, not as a certificate.

How to get faster at data entry specifically

• Learn the number row without looking, then learn the keypad. The single biggest difference between a 6,000 KPH operator and a 12,000 KPH one is usually the digits. If your work is mostly numeric, the 10-key pad with the right hand anchored on 4-5-6 beats the number row substantially.
• Practise the punctuation you actually key. Slashes in dates, hyphens in account numbers, dollar signs, decimal points, commas in thousands. These are the keys people are slowest on and they appear constantly in real records.
• Chase accuracy first, speed second. Every correction costs three or four keystrokes and breaks your rhythm. Operators who slow down by five per cent and stop backspacing usually end up with a higher net figure.
• Stop looking between the source and the screen. Reading the source once, keying the whole record, then verifying is faster than glancing back and forth mid-field.
• Fix your posture and your keyboard. Sustaining a rate for an hour is a different problem from hitting it for a minute, and it is mostly ergonomics.

Where dictation does and does not help

Honestly: dictation will not help you key an account number. Structured fields — codes, amounts, dates, IDs — are faster and safer typed, and no speech engine should be anywhere near them.

Where it does help is the other half of most clerical jobs: the notes field, the case summary, the email explaining why the invoice was short-paid, the handover message at the end of a shift. That is prose, and prose is the thing people speak far faster than they type. Most people type somewhere between 40 and 80 words a minute and speak comfortably above that without trying — you can measure both for yourself on the voice typing test.

VoiceSnap Pro is a dictation app for macOS and Windows built for that use. Hold one keyboard shortcut, speak, and clean punctuated text appears in whichever field your cursor is already in — the CRM note, the ticket, the email — with filler words removed and punctuation added. Every dictation is also saved to a searchable library, which is useful when you need to find what you wrote about an account three weeks ago. It is a one-time $39 purchase rather than a subscription, and nothing you dictate is used to train AI models.

It has not shipped yet. Join the waitlist for one email on release day, or try the browser speech-to-text tool first to see what dictation feels like.

Questions people ask

Is 8,000 KPH good?

It clears the requirement in a lot of general data-entry listings, and it is roughly 27 WPM. Whether it is good depends entirely on the role you are applying for: for high-volume production entry it is on the low side, for general office work it is comfortable. Pair it with your accuracy figure — 8,000 KPH at 99% is a stronger claim than 10,000 KPH at 93%.

How do I convert 10,000 KPH to WPM?

Divide by 300. Ten thousand keystrokes per hour is about 33 words per minute. The converter above will do it for any number, in either direction, without running the test.

Does this count backspaces?

Yes. Raw KPH counts every keystroke including corrections, which is the standard definition and the one most employers use. The accuracy-adjusted figure reported alongside it is the number that reflects usable output.

Why is my KPH lower here than on other typing tests?

Because this test uses data, not prose. Records full of digits, capitals and punctuation are genuinely slower to key than sentences, and a test built on paragraphs will flatter you relative to the work a data-entry job actually involves. If you want the prose number too, the WPM test measures that.

Can I use my result on a job application?

As your own estimate, yes — that is what people use these tests for. Be ready for the employer to re-test you on their own software, and quote a figure you can repeat rather than the best single run you managed.

Is this a 10-key test?

No. The corpus here is alphanumeric — names, addresses and mixed codes — which is the measurement most listings mean when they give a single KPH figure. A pure 10-key numeric test is a separate measurement, usually quoted separately in the same listing.

Is anything I type stored?

No. The test runs entirely in your browser, there is no account and no result is saved or transmitted. Reload the page and every trace of the run is gone.