KeebForge
Guides Layout & size
Decision 01 of 13

Layout & size

The footprint, and which keys make the cut.

Keyboard "size" is described as a percentage of a full-size board. Shrinking the board removes blocks of keys — first the numpad, then the function row, then navigation and arrow clusters — and relocates them to layers you reach with a modifier key. A smaller footprint means less reaching for the mouse and a more ergonomic shoulder angle, at the cost of muscle memory for the layers.

Why people go smaller

A 65% keeps arrows and a handful of nav keys while ditching the numpad and function row, landing in the sweet spot for most programmers: compact, but nothing essential is more than a layer away. 60% and 40% boards lean fully into layers for a minimalist, ultra-portable setup.

When to stay big

Heavy spreadsheet or data-entry work benefits from a real numpad (full-size or a separate macropad). If they hit F-keys constantly in an IDE or DAW, a TKL or 75% keeps the function row physical.

Key count is a consequence

You do not really pick a key count directly — it falls out of the layout you choose. The counts below are typical; exact numbers vary a little by kit.

The options, compared

Every choice you'll see for this decision in the builder.

Full-size (100%)
~104 keys

The traditional office layout. Nothing is hidden behind a layer, which is great for accountants and number crunchers, but it pushes the mouse far to the right.

Pros
  • Dedicated numpad
  • Zero learning curve
  • All keys always visible
Trade-offs
  • Largest footprint
  • Mouse sits far from home row
Tenkeyless (TKL / 80%)
~87 keys

Drops the numpad but keeps the function row, arrows and nav cluster intact. A hugely popular "no compromises except the numpad" choice.

Pros
  • Keeps F-row, arrows, nav
  • Mouse moves noticeably closer
  • Familiar typing experience
Trade-offs
  • No numpad
  • Still fairly wide
75%
~84 keys

Packs the function row, arrows and a column of nav keys into a tight, almost-square footprint. The favourite of many developers who still want F-keys.

Pros
  • Function row + arrows in a small board
  • Efficient use of space
  • Lots of modern kits to choose from
Trade-offs
  • Keys are tightly packed
  • Right-hand keys can be cramped
65%
~68 keys

Removes the function row but keeps dedicated arrow keys and a few nav buttons. Widely considered the best balance of small footprint and everyday usability.

Pros
  • Dedicated arrow keys
  • Small footprint, mouse stays close
  • Great all-rounder
Trade-offs
  • Function row lives on a layer
  • Limited nav keys
60%
~61 keys

No arrows, no function row, no nav cluster — everything beyond the core is on layers. Clean, tiny, and a favourite of enthusiasts who have internalised their layer map.

Pros
  • Very compact and portable
  • Huge case & keycap selection
  • Keeps hands centred
Trade-offs
  • Arrows and F-row on layers
  • Real learning curve
40%
~45 keys

The minimalist extreme. Even the number row is gone. Deeply efficient once mastered, but a real commitment to layer-based typing.

Pros
  • Tiny and ultra-portable
  • Everything within one row of home
  • A genuinely fun challenge
Trade-offs
  • Steep learning curve
  • Numbers/symbols all on layers
Further reading
Next
Key arrangement
Start designing your keyboard