C Typing Test
Type short, real C snippets and see how fast and accurately you handle * & { } ( ) ; # and < >. The test runs on your first keystroke and scores the run the moment you finish.
Before you start
Test setup
- 16 original C snippets
- Symbols: * & { } ( ) ; # and < >
- Joined onto one line, spaces kept
- WPM plus accuracy
How to take it
- Click the test area and type the code exactly, symbols included.
- Line breaks and indentation are turned into single spaces, so focus on characters, not layout.
- Fix mistakes with Backspace; corrected errors still count in accuracy.
- Take two or three runs: snippets change each time.
How scoring works
WPM uses the standard five-character word, so symbol-heavy code scores lower than prose for the same effort. Compare code results with other code results, not with your word-test WPM.
About the c test
The C test uses 16 short snippets written for TypePlay, covering hello world, summing an array, string length and swapping values with pointers. Each is 1 to 10 lines of everyday code, the kind you type many times a day.
What makes C different to type
C adds pointer symbols (* and &), preprocessor lines starting with # and plenty of semicolons, all of which need Shift or awkward reaches.
Where C typing matters
C is the language of operating systems, embedded devices and many first computer-science courses. It is compact but symbol-dense: a single line can hold an asterisk, an ampersand, brackets and a semicolon, so precise symbol typing is part of reading and writing C fluently.
Common C typing slips
Common slips are typing & where * was meant (or the reverse) in pointer code, forgetting the # at the start of an include line, and dropping the semicolon after a statement. The < and > around header names also catch typists who rarely use Shift with the comma and period keys.
Tip for a cleaner run
The asterisk and ampersand are on the number row with Shift. Practise *p and &x as small units rather than separate keys.
A two-minute C drill
Practise the pointer pairs *p, &x and **pp as single units, then #include <stdio.h> five times until it flows. A short daily round of these, followed by one C run, targets the exact keys that slow C typing down.
C typing test: common questions
What is a good WPM for C code?
Code scores lower than prose because of symbols and Shift reaches. Around 30 to 40 WPM on code is solid, and 50 or more is fast. Accuracy matters most: one wrong bracket breaks a program.
Are the snippets real code?
Yes. They are short, working C examples written for TypePlay, such as hello world. They are original and free of licensing restrictions.
Does the test keep indentation and line breaks?
No. The engine joins each snippet onto one line with single spaces, so the test measures characters and symbols rather than how your editor indents.