Configure, test and design in one place - VIA is the last application you'll need for your keyboard.

VIA Try Now! What's New Supported Keyboards Docs Firmware. Discord GitHub. Specification. Appendix. Supported Keyboards; Firmware Downloads; VIA Version 3. Appendix. Supported Keyboards. Supported Keyboards. Compatible as of 3/28/2025 _33 Rev1 _33 Rev2 [1 x 4] + 1 Macropad0-Sixty by ven0mtr0n: 0xCB 1337: 0xCB Static: 10bleoledhub: 1up Slider8:

VIA Nº3. The VIA team is pleased to announce a new release of VIA. New UI 3D Mode Olivia, Binary Artisan and queen of rose gold, has refactored the entire UI engine to deliver keyboard configuration in glorious 3D. 2D Mode

Mar 28, 2025 · Precompiled QMK firmware for VIA-supported keyboards

In order for VIA to configure a keyboard, it requires a definition of the keyboard - the physical layout of keys, any layout options, and other configurable elements like rotary encoders (knobs), lighting, etc.

VIA Version 3 is a refactoring of how the UI works in VIA, to allow fully customized UI within VIA to control firmware parameters like lighting, but also any custom feature implemented in the firmware, either in QMK Core or at the keyboard level. It works by defining what UI elements VIA should show, and binding those UI elements to IDs, which ...

Custom UI is handled in firmware by handling three commands of the VIA protocol: id_custom_set_value; id_custom_get_value; id_custom_save; When enabling VIA and a feature (like lighting) in QMK Core, by default, the command handlers that match the built-in UI definitions will be compiled.

VIA works by communicating with the firmware that is running on the device and sending it commands across USB. Enabling the VIA feature in QMK enables both the ability to communicate with the VIA Configurator and the ability to store keymaps and other settings. Create a via keymap directory and files within that are separate from the default keymap

VIA Version 3. Specification. Custom UI. Built-in Menus. On this page. Built-in Menus. qmk_audio ...

VIA requires a definition of both the physical arrangement of keys and the mapping of those keys to the switch matrix. It optionally requires definition of layout options - alternative physical arrangements of keys, such as different bottom rows, split right shift, etc.