60% vs 65% vs 75% Keyboard: Which Size Should You Get?

What You Lose Going from 75% to 65%

The only thing a 65% removes compared to a 75% is the physical F-row. F1-F12 are still accessible on a 65% keyboard - but only via the Fn key combination (Fn + 1 = F1, Fn + 2 = F2, etc.). The keyboard is 1.1 inches narrower as a result.

If you use F-keys frequently, that two-key combo interrupts your workflow. If you rarely use F-keys, you lose 1.1 inches of width for essentially no penalty.

What You Lose Going from 65% to 60%

Going from 65% to 60% removes the dedicated arrow keys and the small navigation cluster (Delete, Home, End, Page Up, Page Down). These are still reachable on a 60% via Fn layers, but navigating text - selecting, jumping between words, scrolling - becomes measurably slower without muscle memory.

The 60% is only 0.5 inches narrower than the 65%. That is a very small physical gain for the functional loss of dedicated arrow keys.

What Stays the Same Across All Three

• Key pitch (spacing between keys): identical - 19mm center-to-center
• Key height and feel: determined by switch and keycap profile, not layout
• Typing depth: identical (~10.4cm / 4.1")
• Hot-swap, wireless, and build quality options: available across all three layouts

FPS and Competitive Gaming (CS2, Valorant, Apex Legends)

65% wins for most FPS players.

The argument for compact keyboards in FPS gaming is mouse space. On a standard right-handed setup, a narrower keyboard shifts the mouse zone further right and allows lower-elbow, arm-sweep aiming - a real advantage at low DPI (400-800 DPI with high sensitivity multipliers in-game).

The 65% captures most of that mouse space advantage over TKL while keeping dedicated arrow keys - useful for in-game navigation and menu access.

The 60% is 0.5 inches narrower than the 65% - that half-inch rarely matters. But a 60% without dedicated arrows means binding arrow keys via Fn layer is not viable during gameplay. This makes the 65% the better choice over 60% for gaming.

Keyboard	Mouse space gained vs TKL	Arrow keys	F-key binds
60%	~3.5" more	Fn layer only	Fn layer only
65%	~2.5" more	Dedicated	Fn layer only
75%	~1.4" more	Dedicated	Dedicated

Verdict for gaming:

• Pure FPS with no F-key binds: 65%
• FPS + some F-key binds (map key, weapon switch): 75%
• MMO / RPG with heavy F-key macros: 75% or TKL

75% wins for work, clearly.

Work involves typing in documents (arrows needed constantly), navigating spreadsheets (Home/End/PgUp/PgDn), using browser shortcuts (F5 for refresh, F12 for dev tools), and Zoom shortcuts (F-key mute binds on many setups).

A 60% or 65% keyboard handles none of these natively. Every F-key or navigation key requires an Fn combination - slowing down routine work tasks.

For Programming

IDE workflows rely heavily on F-keys: F2 (rename symbol), F5/F10/F11 (debugger controls), F8 (next error), F12 (go to definition). On a 65%, every one of these requires an Fn combination. In a debugger session where you repeatedly press F10 and F11, Fn combos break muscle memory and slow the process.

Exception: Vim/Neovim users who avoid F-keys entirely can use 65% without friction. If your workflow has already remapped F-keys away, the 65% is fine.

Programming workflow	Recommended
VS Code with default shortcuts	75%
JetBrains IDEs (IntelliJ, PyCharm, WebStorm)	75%
Vim / Neovim	65% or 75%
VS Code with fully custom keybindings	65%

Factor	65%	75%
Width	11.5" / 29cm	12.6" / 32cm
F-row	Fn layer	Dedicated physical keys
Arrow keys	Dedicated	Dedicated
Nav keys (Home/End/PgUp/PgDn)	2-4 dedicated	4-6 dedicated (compressed)
Mouse space vs TKL	2.5" more	1.4" more
Width difference between them	-	1.1" / 2.8cm wider
Best use case	FPS gaming, minimal desk, no F-key workflows	Work, programming, hybrid use

Choose 65% over 75% when: You game primarily and rarely open an IDE, spreadsheet, or use browser dev tools. You value every centimeter of mouse room.

Choose 75% over 65% when: You split time between work and gaming, you use any IDE with default shortcuts, or you want a keyboard that handles every use case without compromise.

Factor	60%	65%
Width	11.0" / 28cm	11.5" / 29cm
Dedicated arrow keys	No	Yes
Small nav cluster	No	Partial
Width difference	-	0.5" / 1.3cm wider
F-row	Fn layer	Fn layer
Best use case	Minimalist, travel, Vim users	Gaming, compact setups

The 60% vs 65% decision almost always comes down to one question: do you use arrow keys?

If yes: 65%. The 0.5-inch width difference is negligible - you gain dedicated arrow keys for half an inch of extra keyboard width.

If no - meaning you navigate text exclusively with Vim keybindings, mouse, or custom remaps - the 60% is a clean choice with slightly less desk presence.

For nearly everyone, the 65% is the better buy over the 60%. The functional difference far outweighs the 0.5-inch width savings.