QMK vs VIA vs Proprietary Keyboard Software: What You Can Remap
Two keyboards may both say “programmable,” yet one stores custom layers directly in firmware while the other depends on a Windows utility running in the background. For users who switch computers or operating systems, that difference matters more than RGB presets.
QMK is firmware, not a desktop skin
QMK is an open-source keyboard firmware project supporting extensive keymaps, layers, tap behaviors and other features on compatible boards. Its exact feature availability depends on each board’s build, MCU and configuration. Traditional QMK workflows can involve compiling and flashing a keymap, which is more technical than dragging key icons in a browser. The advantage is control: a compatible board may run a carefully built layout without host-side software. QMK support should be checked by exact model and revision, not assumed from brand identity.
VIA is a configuration interface
VIA provides a friendlier way to edit supported dynamic keymaps on compatible firmware. It is not interchangeable with QMK: a QMK board is not automatically VIA-enabled, and a keyboard advertised as “VIA compatible” still may need the correct definition or firmware. Ask which layers, macros and special keys work on that exact revision. For office use, the ability to remap Home, End or media keys quickly can be more valuable than an elaborate custom compiled keymap. An interface screenshot is not evidence that a random model supports every advertised feature.
Proprietary software can be fine, with caveats
A vendor utility may make per-app profiles and lighting easier, yet tie advanced settings to a particular OS or internet login. Check whether settings stay in onboard memory, whether macros work when the app is closed, and whether the software still receives security updates. Do not install firmware packages or configuration executables from unknown file hosts just to save a used keyboard. The vendor’s support page is the proper place to retrieve software and firmware. For a shared workplace computer where installations are prohibited, onboard remapping and independent operation should rank high.
Three questions to ask the seller
Does the exact model appear in official QMK support or the manufacturer’s documented ecosystem? Can you remap the relevant keys on your own operating system? Are settings stored on the device? Ask for a video showing an actual layer change and a reboot, not a marketing brochure with “QMK/VIA” stamped on it. Also ask whether the board has a recovery or bootloader procedure in case firmware flashing fails. Programmability is valuable only when its support story survives ordinary ownership.
Before you buy: four things to verify
- Verify the exact keyboard revision in official support documents.
- Check onboard profiles and host OS support.
- Confirm needed layers/macros exist in that build.
- Avoid unknown firmware downloads and undocumented flashing.
Source and further reading
For the underlying hardware, layout or buyer-protection details, start with Official QMK keymap documentation. Always verify individual model specifications with the maker before purchase.
Frequently Asked Questions
No. VIA needs compatible dynamic keymap support and often a definition for the board.
Often when stored in device firmware, but behavior and profiles are specific to the board and implementation.