Hand and finger load
- Synchronized data appears here after analysis.
Analysis shows the load assigned to both hands and all eight fingers.
Enter Latin text or recorded key sequences to compare QWERTY, Dvorak, and Colemak by key frequency, finger load, and adjacent-key patterns.
Input and analysis settings
Up to 20,000 characters. Chinese characters do not reveal the actual input-method key sequence; use pinyin, Latin text, or recorded keys.
Results use fixed 30-key layouts and standard fingering models for comparison only.
Analysis shows the load assigned to both hands and all eight fingers.
Analysis shows key frequency in the selected 30-key letter area.
| Layout | Valid keys | Same-finger pairs | Hand switches | Average movement | Left / right hand |
|---|---|---|---|---|---|
| Synchronized data appears here after analysis. | |||||
The table compares like-for-like measures; it does not rank a single best layout. Learning cost, personal fingering, and real speed are outside this model.
Characters are normalized with NFKC, lowercased, and mapped to the selected layout's fixed 30-key letter area. Same-finger rate = consecutive pairs assigned to one finger ÷ all consecutive valid pairs; hand alternation uses the same denominator. Finger load = that finger's keys ÷ valid keys. Movement is an estimated Euclidean distance between key centers in model units.
Spaces, line breaks, and unsupported characters break adjacent pairs, so the ends of separate words or unknown segments are not connected.
Counts and distances remain unrounded internally. Percentages show one decimal place and average movement shows two; comparisons use the original values.
Only fixed QWERTY, Dvorak, and Colemak 30-key letter areas and standard fingering are modeled. Chinese characters may come from different input methods and cannot reveal a unique key sequence. Shift layers, shortcuts, spaces, Enter, and custom fingering are outside the model.
It is the share of adjacent valid key pairs assigned to the same finger. A higher value only describes this fixed model; it is not a direct speed or comfort result.
Metrics can conflict, and language, fingering, shortcuts, and learning cost differ. The page reports separate measures instead of inventing an absolute ranking.
They are excluded from the 30-key counts and break adjacent pairs, so characters on opposite sides are not treated as consecutive keys.
Text and analysis results stay in this browser. Nothing is uploaded, no remote API is called, the URL is not written, and local storage is not used.
The tool uses no third-party runtime code or assets; the layout maps, algorithm, and interface are independently implemented.