How to Remap a Split Keyboard with Vial

One of the quickest ways to make a split keyboard harder to use is to remap everything on day one. A better approach is simpler: keep the familiar parts familiar, then change only the keys that interrupt normal work.

Elytra is a useful case study because its 63-key row-staggered QWERTY layout remains recognizable while the two halves can be positioned independently. The current ElimKeys Elytra product page lists USB-C and Bluetooth connectivity, hot-swappable low-profile switches, and Vial support for full key remapping, macros, and combos. Vial’s official documentation also covers layered keymaps. The familiar letter layout provides a stable starting point; Vial handles the functions that do not fit comfortably on the default layout.

ElimKeys Elytra split keyboard shown as an introduction to Vial key remapping — Keep the base layer familiar, then remap only where regular work reveals friction.

Quick take

What to remap first	Why it matters on a split keyboard	Beginner-friendly example
One layer key	A compact split board has fewer visible keys, so one reliable function layer matters more than many clever shortcuts.	Hold Fn for Home, End, Page Up, Page Down, media controls, app shortcuts, or an optional numpad layer.
High-friction reach keys	Split spacing changes your hand position; some old reaches may now feel less natural.	Move Backspace, Delete, or a language/input key closer to the resting position.
An optional macro	A macro is worthwhile only when it removes a repeated sequence.	A meeting-note template or email sign-off used several times a day.
An optional combo or navigation layer	Add one only when it reduces a repeated reach or interruption.	A two-key Delete combo or a small navigation layer.

1. Start with the default layout and make one useful change

The default layout gives you a baseline. Keep the letter area and most modifiers unchanged until ordinary typing reveals a repeated interruption. In this guide, base layer means Layer 0, while keymap refers to the complete configuration across all layers.

Type normally for a while. Open a document, answer a few messages, use familiar shortcuts, and note where the hands hesitate. The first useful remap is usually ordinary: Backspace, Delete, a right-side modifier, media control, language switching, or another key used throughout the day.

ElimKeys Elytra split keyboard with a clear and familiar base-layer layout — A readable base layer makes the keyboard easier to trust while the rest of the keymap evolves.

2. Connect Elytra, unlock Vial Web, and make a basic remap

Power on both halves and, following the official Elytra user manual, connect the left (Central) half to a trusted computer with USB-C. The official Vial first-time-use guide explains the basic remapping workflow and how ordinary key assignments are written to the keyboard.
Open Vial desktop or Vial Web. For Vial Web, use a recent Chrome, Chromium, or Edge browser. When the site asks you to unlock or authorize the keyboard, follow the on-screen procedure only on a computer you trust. When configuration is finished, select Security > Lock or reconnect the keyboard to leave unlocked mode.
Confirm that Vial has detected Elytra and that the on-screen keyboard matches the physical board. Check the active layer before editing; Layer 0 is the base layer.
Record the original layout before changing it. Take screenshots of the base layer and any layers you plan to edit, or export a configuration file if the Vial version you are using offers that option.
In Vial, select the on-screen key you want to change, choose the new keycode, and confirm that the label on the Vial layout updates as expected.
Test the ordinary remap in a plain text editor. Standard key assignments are written to the keyboard as soon as the new keycode is selected, so there is no separate Save button for a basic remap.
Macros use a different workflow. Open the Macro editor, create or edit the sequence, click Save, then assign that macro to a key and test it. A macro that has not been saved in the editor may not be available as expected.
If a change is wrong, use the screenshots or exported configuration to restore the affected key. If Vial no longer detects the board, reconnect the left half, reopen Vial or Vial Web, repeat the unlock step, and confirm the active layer before editing again.

Bilibili hands-on: opening, connection, layout screen, and firmware workflow

The walkthrough shows Elytra being connected, recognized in the configuration interface, and taken through layout and firmware-related screens.

3. Decide what to change next

The Reddit beta tester review of Elytra gives a practical example: the reviewer kept the dedicated arrow cluster and remapped controls for switching tracks and adjusting volume. The point is not to copy that choice; it is to tie every change to a recurring interruption.

Before changing another key, name the problem in one sentence: Backspace is too far away. Cmd is awkward on macOS. The input-language key is buried. Screenshots interrupt the workflow. A specific problem makes the result easier to judge.

4. Build one useful layer

The Vial layers manual describes layers as stacked keyboard functions that can be switched when needed, much like a laptop function layer. On a compact split keyboard, one thumb or corner key can provide access to functions that do not fit on the base layer.

A sensible first layer for Elytra might place Home, End, Page Up, and Page Down around the dedicated arrow cluster, add media controls and app shortcuts in easy-to-remember positions, or provide an optional numpad layer. Keep the first layer simple enough to recall without looking it up.

Daihuku Keyboard: Vial layers and everyday typing workflow

Daihuku demonstrates Vial layers, Bluetooth switching, and everyday typing on Elytra. The footage shows how extra functions can be added without making the familiar base layer difficult to read.

5. Add macros, combos, or advanced keycodes carefully

The Vial macros manual defines macros as stored action sequences, while the Vial combos manual explains how a chosen group of keys can trigger another action. Both are optional and should be added only when a repeated task or awkward reach justifies the extra complexity.

When a repeated task justifies a macro, create or edit it in the Macro editor and click Save before assigning it to a key. Combos should be equally selective: define a small key combination only when it replaces a repeated interruption. Screenshots, a meeting-note template, an email sign-off, or a difficult Delete reach are reasonable examples; adding features simply because Vial offers them is not.

Whatever is added, test the keymap with the spacing, angle, mouse, and palm support used during normal work. A shortcut that feels easy when the halves are close together may become awkward after they are separated.

ElimKeys Elytra split keyboard positioned for testing remapped keys — Test remapped keys with the same spacing, angle, and palm support used during normal work.

If the relevant keycodes are available in the Elytra firmware detected by Vial, an optional navigation or mouse layer can reduce hand movement. Mouse Keys, Mod-Tap, and similar advanced functions should not be assumed to exist in every Elytra firmware build; use them only when they appear in the available keycode options. For design, CAD, spreadsheets, games, or other pointer-heavy work, a dedicated mouse or trackpad may still be the better tool.

JSyntax: Vial setup, layers, mouse layer, and travel-focused workflow

JSyntax shows Vial setup, layers, a mouse-layer workflow, and travel use. Treat the advanced functions as examples to explore only when the corresponding keycodes are available in the Elytra firmware shown by Vial.

6. Test and simplify over the first week

A first-week plan should follow real typing problems rather than assign a new Vial feature to every day:

Days 1-2: Keep the base layer familiar and record repeated interruptions. Day 3: Fix one or two high-friction keys and build one simple layer. Days 4-7: Add a macro or combo only when a repeated task clearly justifies it. At the end of the week, remove anything you did not use.

Good remapping is often subtractive. A feature that sounds clever but is forgotten during real work is clutter. The goal is not to fill every available slot; it is to keep the keymap easy to understand.

ElimKeys Elytra split keyboard with wooden palm rests for everyday keymap testing — The same keymap can feel different as spacing, angle, and palm support change, so evaluate it in the setup used every day.

Final take

Start with the key that interrupts typing most often, then follow the full workflow: record the original layout, confirm the active layer, make one basic remap, and test it before moving on. On Elytra, the first change may be Backspace, Delete, a right-side modifier, a media control, a language key, or the key used to access a layer.

Standard key assignments are written to the keyboard immediately, while edits made inside the Macro editor require the Save button. Keep screenshots or an exported configuration so changes can be reversed. The best keymap is not the most complicated one; it is the one that remains understandable during normal work.