How to learn touch typing

What touch typing actually is

Touch typing is not a speed. It is a change in how the key is found. A hunt-and-peck typist locates a key visually and then presses it, so every keystroke costs a search. A touch typist's finger already knows where to go, because each key is stored as a movement from a fixed starting position rather than as a picture of a keyboard.

That distinction explains the thing that frustrates most self-taught typists: practising more does not fix it. More repetition of a visual search makes you a faster searcher, and the ceiling on searching is somewhere around 60 words per minute. It is a genuinely different skill, which is why it takes a deliberate few weeks rather than gradually happening.

The payoff is not only speed. It is that typing stops consuming attention. When your fingers handle the keyboard, you can read from a document, a whiteboard or a second monitor while you type, and you can think about the sentence instead of the spelling of it.

Step 1 — home position

Rest your left index finger on F and your right index finger on J. Almost every keyboard made in the last forty years has a small raised bar or dot on those two keys, and it exists for exactly this reason: it lets you re-find home position by feel, with your eyes anywhere else. Let the remaining fingers fall naturally — left hand on A S D F, right hand on J K L ; — and rest both thumbs on the space bar.

Every key on the board is now defined as a reach: a finger leaves home, presses one key, and returns. The return is the part beginners skip, and it is what keeps the map accurate. If the hand drifts, every reach is measured from the wrong origin and the errors look random when they are not.

Posture matters less than the internet suggests, with two real exceptions. Keep your wrists floating rather than resting on the desk edge while you actually type, and keep your elbows at roughly a right angle so your fingers hang over the keys instead of stretching up to them. Everything else is comfort.

Step 2 — learn the keys in the right order

A typing curriculum is really a schedule for introducing keys, and there is a standard one. It comes from typing textbooks that predate computers, and it survives today in KTouch and GNU Typist. The rule is two keys at a time, paired across the hands, working outward from the strongest fingers to the weakest.

Notice what the order is not: it is not row by row. Learning the whole top row at once is a ten-key jump, and you cannot drill it, because nothing meaningful is spellable from ten unfamiliar letters. Instead the rows interleave. The next key is always the one your hand can nearly already reach — which is why e arrives early, being the most common letter in English, and why y and z are saved for last.

This is the ladder KeySlice uses, unchanged:

The first two or three steps have too few letters to spell any word at all, so they drill key patterns — jjf jfj ffj — exactly as the traditional courses do. Real words appear the moment the letters exist to make them, at C and A. Do not skip the pattern stage looking for something that feels more like typing; it is short, and it is where the reach itself is learned.

Step 3 — the four rules that decide the outcome

Never look down

This is the rule the whole method rests on. Every glance at the keyboard is a repetition of the skill you are trying to replace, and the effect is not small — it is the difference between learning and not learning. Willpower usually fails here in week one, so use a physical barrier: a tea towel over your hands, a shallow cardboard box, or a keyboard cover. Remove it once you stop reaching for it.

Accuracy before speed

Aim for about 95% accuracy. Below that, you are rehearsing the wrong movement often enough to learn it. Far above it, you are typing well inside your comfort zone and nothing is being stretched. And accuracy is faster even on its own terms: an error costs a backspace, a retype, and the half-second pause where you notice it, so a 92% run is usually slower in real time than a 98% run at the same nominal speed.

Short and daily

Fifteen minutes a day beats two hours once a week, because motor skills consolidate between sessions rather than during them. Sleep does a meaningful part of the work. The practical consequence is that missing days costs you more than short sessions do.

Stop when you get sloppy

When accuracy falls apart mid-session, the session is over. Practice past fatigue teaches the fatigued version of the movement. Ten good minutes are worth more than twenty-five that end badly.

Step 4 — a realistic four-week schedule

This is what fifteen minutes a day actually looks like. The numbers are typical rather than promised; people vary by a factor of two either way, and starting speed matters less than consistency.

Week 1 — the uncomfortable one

Home row and the first few pairs. Your speed will be somewhere between 5 and 15 WPM, which is dramatically slower than you can already type, and this is the week most people quit. Expect it, and judge the week on whether you kept your eyes up rather than on the number. By day five or six the home row starts arriving without thought.

Week 2 — the map fills in

Most of the alphabet, and real words instead of patterns. Speed climbs to roughly 15–25 WPM. Errors begin to cluster on specific keys rather than being spread evenly, which is the first point where drilling your weak keys specifically pays off more than general practice.

Week 3 — back to where you started

The full alphabet plus capitals and basic punctuation. Around 25–35 WPM, which for many people is roughly their old hunt-and-peck speed — reached now without looking, which means it will keep going up rather than plateauing. This is the week it starts feeling like typing.

Week 4 and after — it becomes invisible

Sentences, punctuation, and whatever you actually write. 35–45 WPM, and rising slowly from here on ordinary use alone. The formal practice can stop; what you keep is the habit of not looking. Getting from here to 70 WPM is mostly a matter of months of normal typing, plus occasional targeted drills on the keys that stayed slow.

Step 5 — find your weak keys and drill those

An overall WPM score hides where your time actually goes. Two people can both type 45 WPM while one of them loses everything on the bottom row and the other on the number row — and a generic drill helps neither, because most of its letters are ones they already own.

What you want to know per key is two numbers: how often you get it right, and how long you pause before it. The second one matters more than people expect. A key you always hit correctly but hesitate 400 milliseconds before is not learned; it is being worked out. Those keys are invisible to an accuracy score and they are usually where the next real gain is.

The keys that are slow are predictable in aggregate — the pinkies, the bottom row, and any reach that crosses the hand's natural line — but which ones are slow for you is not. This is the part KeySlice automates: every keystroke updates a per-key score, and the drills you get are weighted toward the keys you are currently worst at, while keys you have mastered stop consuming practice time.

Common mistakes

• Learning a whole row at once. Ten new keys cannot be drilled, because nothing is spellable. Two at a time is not slower; it is the only version that works.
• Chasing WPM in week one. The score is meaningless until the map exists, and chasing it is what makes people look down.
• Anchoring the wrists on the desk. It forces reaches to come from the fingers alone, which is where the ring and little fingers give up.
• Using the wrong finger "just for this key". Almost always B, Y, or the number row. The exception becomes the habit, and it caps the whole hand's speed later.
• Skipping capitals. Most self-taught typists shift with the same hand that types the letter. Learning the opposite-hand shift is one short lesson and it removes a stumble from every sentence you will ever write.
• Practising only prose when you write code. Ordinary text is almost entirely lower-case letters on the home and top rows. Code lives on brackets, semicolons, underscores and operators, reached with the weakest fingers.

If you type code

Programming is a different typing problem, and prose is a poor proxy for it. A developer who types 70 WPM on English can drop below 30 on a block of real source, because the symbol density is completely different and the symbols sit on exactly the keys most people never drilled: the brackets, the punctuation row, and the shifted top row.

The mix also differs sharply by language, which is why practising all three at once is worth less than practising the one you write. Python leans on colons, underscores and consistent indentation. C++ is dense with braces, semicolons, angle brackets and the scope operator. HTML is mostly angle brackets, quotes and slashes, typed in the particular rhythm that closing tags demand. Each has its own drill page, on the same trainer.

Do the alphabet first regardless. Symbol drills on top of an unreliable letter map just make both harder.

Frequently asked questions