Buying guide
Keyboard percentages are useful shorthand, but they do not answer the buying question on their own. This guide compares 40%, 60%, 65%, 75%, and full-size layouts so you can decide which functions deserve a physical key and which can live on a layer before buying a split keyboard.
Keyboard percentages sound precise, but they are market shorthand rather than a formal standard. RTINGS' keyboard-size guide describes common conventions, yet two boards sold as 65% can still use different navigation columns, modifier keys, thumb keys, or duplicate letters. Split keyboards blur those labels further because physical separation, thumb areas, and software layers may matter more than the raw key count.
The better question is not “Which percentage is best?” but “Which actions need to remain one keypress away in my actual workflow?” The answer depends on whether you write, program, enter numbers, edit media, play games, or move among several devices. Elytra is a useful case study because its 63-key layout sits between familiar compact conventions rather than matching one label exactly.
First, understand what the percentages usually remove
The percentage describes an approximate footprint and feature set relative to a traditional full-size board; it does not guarantee an exact number of keys. The table below summarizes common conventions, not a universal standard.
| Layout | Typical keys | Usually keeps | Usually moves or removes | Best fit | Layer load |
|---|---|---|---|---|---|
| 40% | About 40-50 | Letters, core modifiers, space or thumb keys | Number row, function row, arrows, navigation, numpad | Users who actively want to design and maintain a custom keymap | High |
| 60% | About 60-62 | Letters, number row, standard punctuation | Usually arrows, navigation cluster, function row, numpad | Everyday typing, gaming, travel, and users comfortable with a simple Fn layer | Moderate |
| 65% | About 66-68 | 60% core plus dedicated arrows and a small navigation column | Function row and numpad | Office work, writing, coding, and buyers new to compact layouts | Light to moderate |
| 75% | About 80-84 | Dedicated arrows, navigation keys, function row | Numpad | Shortcut-heavy work, editing, and users who want compactness without deep layers | Light |
| Full-size | About 104-105 | Function row, navigation cluster, numpad | Very little | Accounting, sustained data entry, legacy workflows, and the greatest direct key access | Low |
40%: minimal physical keys, heavy reliance on layers
A 40% split keyboard normally removes the physical number row, function row, navigation cluster, and often several punctuation or modifier positions. When the keymap is designed well, frequently used functions can remain close to the home row and thumb positions. The trade-off is that the board only becomes efficient after its layers make sense to the user.
This category suits users who already know which symbols, shortcuts, and navigation patterns they want. It can be a demanding first split keyboard for someone who still looks down for numbers, changes software frequently, shares the board, or does not want to maintain a custom keymap. A well-designed 40% layout can be fast; a copied keymap can feel like a memory test.
60%: familiar letters and numbers; navigation usually moves to a layer
A typical 60% layout preserves the alphanumeric block and number row. F1-F12 usually sit on Fn plus the number row, while arrows and navigation keys are commonly layered. The format saves substantial desk space without hiding everyday letters, numbers, and punctuation.
For gaming, general writing, and travel, a 60% layout may be enough. For spreadsheets, code review, document editing, or any workflow that repeatedly uses arrows, Home, End, Page Up, Page Down, and Delete, the exact layer matters more than the percentage. Those commands should form a coherent cluster rather than being scattered across unrelated positions.
65%: a familiar starting point for compact-keyboard buyers
A 65% layout is a common starting point because it usually restores dedicated arrow keys while keeping the overall width compact, often with a narrow navigation column. The function row and numpad remain absent, but routine office work typically requires less layer use than on a 60% board.
Ruka Mikoshiba's Japanese hands-on post described Elytra as feeling close to a familiar 65% experience. That is one user's first impression rather than evidence of a universal learning curve, but it illustrates why a compact split can feel approachable even when its exact key count does not match a conventional 65% template.
75%: compact width without giving up the function row
A 75% layout restores F1-F12 and usually keeps a fuller navigation cluster. It can suit IDE debugging, creative applications, browser shortcuts, media controls, and workflows built around function keys. The layout remains narrower than tenkeyless or full-size boards because the clusters are compressed rather than separated by wide gaps.
The trade-off is physical size. On a two-piece 75% split keyboard, each half becomes larger, and a travel case must protect more surface area. Buyers considering a wireless 75% split keyboard should check whether “split” means two independent modules or a single chassis with a divided, angled layout. They should also verify how the halves communicate and whether both sides can be positioned freely.
Full-size and split full-size: direct access wins, but the desk gets wider
A full-size keyboard provides the least ambiguity: a dedicated number pad, function row, arrows, and navigation block are always visible. It remains practical for users whose work is dominated by accounting, sustained numeric entry, legacy shortcuts, or software designed around a standard 104/105-key map.
The disadvantage is not only portability. A wide right-side number pad can push the mouse farther from the typing area. A full-size split board may improve hand spacing, but it does not automatically solve mouse reach. Users who need numbers only part of the day may be better served by a compact split keyboard plus a separate wired or wireless number pad that can sit on either side or be stored when not needed.
The keys that should drive the decision
Dedicated arrow keys
Arrows are easy to dismiss until they are used hundreds of times per day. Writers move through text, developers navigate suggestions and logs, spreadsheet users change cells, and gamers use menus or camera controls. A good arrow layer can be excellent, but users who switch applications constantly may prefer visible arrows so navigation never depends on remembering the active layer.
When a physical function row matters
Function keys matter unevenly. Many users rarely touch them, while developers, editors, CAD users, and enterprise-software users build entire routines around them. Fn plus the number row is often easier to learn than an unrelated layer because the spatial relationship remains obvious. A physical F-row is worth the extra size when the workflow requires frequent one-handed function-key presses or complex modifier chords.
Do you need a number pad?
A top number row works for occasional quantities, dates, shortcuts, and passwords. A numpad layer can work for short bursts when the user can keep the grid in memory. A separate wired or wireless number pad is more flexible for mixed work: wired models suit permanent desks, while wireless models are easier to reposition or carry. A built-in number pad makes the most sense when numeric entry is continuous enough that setup and repositioning would become a nuisance.
Judge the frequency and duration of numeric work rather than relying on a general preference for or against numpads. If the number pad is used for sustained blocks every day, keep a physical numpad available. If it appears only for occasional totals or spreadsheet formulas, a layer or separate pad can preserve mouse space for the rest of the day.
Why compact split keyboards rely on layers and remapping
A layer does not remove a function; it changes the path used to reach it. That can reduce finger travel when the map is consistent, or add friction when frequent commands are hidden behind awkward holds. Compact keyboards work best when the layer follows an obvious pattern: F-keys on the number row, navigation in a directional cluster, and workflow-specific shortcuts grouped by purpose.
The current ElimKeys product page and online manual document Vial remapping and multiple layers. Those are product capabilities rather than proof that every user will prefer the default map, and the exact assignments available still depend on the current firmware and Vial interface. The practical value is that real use can reveal which functions deserve better positions.
For a deeper explanation of physical key geometry, spacing, and software layers, see Split Keyboard Layouts Explained. Start conservatively: keep the base layer recognizable, then move only the functions that repeatedly interrupt normal work.
Watch bookchi's ElimKeys Elytra review on YouTube. This independent Korean review shows split positioning, the Vial configuration interface, and changes to the compact right side. It is useful context for the trade-off between key count and workflow; it covers an earlier review unit, so check the official product page for current specifications.
Where the 63-key Elytra fits
Elytra is a 63-key split keyboard that sits between common 60% and 65% conventions. It retains the number row and visible arrow keys, but omits a physical function row, numpad, and some conventional right-side positions. Its row-staggered QWERTY geometry remains familiar, although the compact right side does not reproduce every standard modifier position.
Karn Bulsuk's early Elytra overview highlighted the 63-key count, absent function row, and compact right side as the main layout questions. It also noted the value of fully wireless halves for independent positioning. Because that article covered a crowdfunding-stage unit, use the current official product page and manual for production specifications and the latest keymap.
The latest official keymap and Vial guidance should be checked before purchase. Elytra does not provide a conventional standalone right Shift position. If the required assignment is available in the current firmware and Vial interface, remapping can address a few personal mismatches; it should not be used to rationalize a layout that fundamentally conflicts with the workflow.
Elytra is likely a good fit when...
- You want a first split keyboard without relearning a column-staggered or ortholinear letter layout.
- You use the number row and arrows regularly but can place F-keys and secondary navigation on layers.
- You value mouse space, portability, and independent positioning more than maximum direct key access.
- You are comfortable checking the current Vial options and making a few deliberate remaps after testing the default layout.
- You work across several devices and want a compact board that can move between desks.
Elytra is a weaker fit when...
- Your work depends on continuous numpad entry or a physical function row.
- You require every conventional right-side modifier in its standard location and do not want to remap.
- You want an extreme 40% layout with deep thumb layers and minimal finger movement.
- You want a larger 75% or full-size split with more dedicated navigation and shortcut keys.
- You prefer a one-piece keyboard with fixed geometry and minimal setup or repositioning.
Watch Ushaslime's ElimKeys Elytra review on YouTube. This independent Japanese review shows spacing and angles between the halves, low-profile switches, real typing, and Vial remapping in a daily desk setup.
A quick decision method before buying
Open the software you use most and note every non-letter key pressed during a representative hour. Do not count a shortcut because it sounds important; count it because it actually appears. Then sort the keys into three groups: must be dedicated, acceptable on a simple layer, and rarely needed.
| Question | When the answer is yes | When the answer is no |
|---|---|---|
| Do you use a number pad for sustained daily entry? | Consider full-size or a separate physical numpad. | A top row or numpad layer may be enough. |
| Do you use F-keys frequently or in complex modifier shortcuts? | Consider 75% or larger. | An Fn layer on a 60% or 65% layout may be sufficient. |
| Do you navigate with arrows throughout the day? | Favor visible arrows. | A coherent navigation layer may be better. |
| Will you customize the keymap? | Compact boards become more flexible. | Choose the layout closest to current habits. |
| Will the keyboard travel? | Compare compact formats, case size, cables, modules, and total weight. | A larger layout may be worth the extra direct access. |
Final take: choose the smallest layout that keeps your workflow predictable
A 40% split is not automatically more efficient, and a full-size board is not automatically more practical. The right key count is the smallest one that preserves predictable access to the commands used most often. Everything else can move to a layer, separate accessory, or less prominent position, provided the new path remains easy to remember.
For many buyers, 65% is a common compact starting point, while 75% may suit shortcut-heavy work that benefits from a physical F-row. A 60% suits users who accept layered navigation, while 40% rewards people who actively want to design a keymap. Full-size remains practical when sustained numeric entry and the greatest amount of direct key access matter more than desk width.
Elytra's 63-key design occupies a middle ground: familiar letters and numbers, visible arrows, no physical F-row or numpad, and some room for personal adjustment. If the required assignments are available in the current firmware and Vial interface, remapping can address a few individual mismatches. The layout is best suited to users who want a compact, portable split without turning the keyboard into a full-time keymap project.
Share:
How to Choose an Ergonomic Split Mechanical Keyboard for Small Hands
How to Choose a Quiet Split Keyboard for Office Work