QMK or VIA in 2026: Which Firmware Path to Pick

Spending two hours remapping Caps Lock to Escape and binding jump-to-definition to a finger shortcut is the most underrated benefit of a mechanical keyboard. But in 2026 that workflow hits a wall: VIA's official site, via.app, is no longer a configurator. It is a domain for-sale page listed at $39,000. I visited the domain directly and got Spaceship.com's sales page.

That does not mean VIA stopped working tomorrow. Most keyboards ship with VIA firmware already flashed, and the remapping capability lives in the chip. What it means is something else: the "download VIA, import the JSON, drag keys" flow that most tutorials still teach now points at a URL that no longer works. Search for a VIA tutorial today and you will be sent to a page that will not load.

This article splits into three routes based on how deep you want to go, and for each one I spell out what the tool can actually do and where you are inevitably pushed back to source code. The four ASINs at the end were each confirmed by loading the amazon.com product page and parsing its product title — none were guessed from a model number. Prices use the manufacturer's own site, because marketplace price fields on these listings pick up prices from same-category carousels and cannot be trusted. Stock status and ratings move over time.

⚠️ Affiliate disclosure: the product links below are Amazon affiliate links (tag=techpassive-20). If you buy through them I may earn a commission. That does not change a single limitation listed below.

TL;DR: Route one (remap a few keys) → buy a QMK/VIA board and use the vendor's own launcher. Route two (home-row mods, tap dance, more than four layers) → go straight to Vial, which closes VIA's main gaps. Route three (real wireless plus long battery) → recognise that ZMK is a different stack and do not apply QMK tutorials to it. Costs and hard limits for each route are in sections three through five.

Five firmwares, and who is actually related to whom

These five names get conflated constantly, but they sit in three distinct layers.

QMK is the engine. Its official site, qmk.fm, describes it as open source, targeting Atmel AVR and Arm USB families, currently supporting over 3,000 keyboards. It runs on the keyboard's microcontroller, with keymap, layers and macros stored in the chip's flash — nothing on your computer needs to be running. The cost is that changing a keymap means editing keymap.c source, recompiling, and reflashing.

VIA is a graphical shell on top of QMK. Keebio's official documentation is precise about this: VIA is essentially QMK with VIA_ENABLE turned on, plus a configurator that lets you drag keys in a browser instead of reflashing. Most keyboards do not ship with that feature enabled, which is exactly why the same keyboard is reported as remappable by one person and not by another.

VIA's hard limits come from that same documentation and are easily glossed over in tutorials: 4 layers by default, and increasing that requires going back to a QMK build environment. Advanced features such as tap dance are not exposed in the VIA configurator and need the build environment too. You also have to manually import a JSON definition file before the configurator recognises the board.

Vial is a different QMK fork that fills VIA's gaps. Pascal Getreuer's guide is the most widely cited document in this space, and his claim is blunt: VIA remains partially closed-source and appears to have had no updates since 2020, while Vial is fully open source and actively maintained. Functionally Vial natively adds Auto Shift, Caps Word, Combos, Key Lock, Key Overrides, Layer Lock, Repeat Key, tap dance, and dynamic editing of tap-hold configurations (permissive hold, quick tap, chordal hold, tap flow).

Vial is not complete either. The same document states that as of April 2026 it still lacks per-key tap-hold settings, autocorrect, key lock, leader key, OS detection, swap hands and unicode input. The document does give you a fix: customise your own Vial build to enable what is missing.

One design difference is worth noting: VIA requires you to manually load a JSON definition file, whereas Vial stores that metadata on the keyboard itself and is recognised automatically. That difference only becomes valuable once you are managing five keyboards.

ZMK solves a different problem. Its official site lists three things: powered by Zephyr, wide architecture support, MIT licensed, and wireless-first. The first two are technical descriptions. The third is the point — developer documentation explains why ZMK exists at all: QMK's GPL licence is incompatible with commercial Bluetooth stack implementations.

Vendor launchers are a fifth thing, and they are neither QMK nor VIA. Keychron now pushes its own Keychron Launcher across the line, and the company's product pages sell it as updating and customising your keyboard online with QMK and Keychron Launcher. VIA has been demoted to a secondary role here: on the Q6 Max and C2 Pro product pages I read on Keychron's Canadian site, the main flow is "Program with QMK & Launcher" and the VIA entry is collapsed into a single separate link. A third-party community project is blunter about the same thing — Keychron's firmware locks you into VIA and their web launcher, and getting real Vial onto such a board needs a community fork.

Route one: remap a few keys, use the vendor launcher

This route fits someone who wants Caps Lock to become Escape, wants one macro bound, or needs to fix a mislabelled key. No terminal, nothing to compile.

How it goes:plug in the cable (for most models this is a hard requirement — the specific limit shows up in the next section), open the vendor launcher in a browser, drag and save.

The ceiling on this route is four layers. Hit a fifth and you have two choices: live with four, or move to route two. Settle this before you buy, not after.

Route two: home-row mods and tap dance, go straight to Vial

This route fits someone already on a 60% or 65% layout who wants home-row mods (so the pinkies stop carrying Ctrl and Shift), or tap dance to make one key behave three ways.

Two terms that get conflated deserve separating here. Home-row mods is a layout technique — assigning modifier behaviour to home-row letter keys — not a firmware feature. The firmware feature that actually enables it is tap-hold / mod-tap, which QMK's documentation describes as one key doing three jobs: tap for a letter, hold for a modifier, tap-then-tap for a third behaviour.

QMK's tap dance documentation gives concrete numbers that are useful when copying a setup:

• Tap dance is off by default and needs TAP_DANCE_ENABLE = yes in rules.mk, costing less than 1KB of firmware size
• TAPPING_TERM defaults to 200 milliseconds — you must complete repeated taps inside that window or they register as separate presses
• The docs spell out the failure mode exactly: with a 175ms threshold and a double-tap bound to Enter, tap once, wait more than 175ms, then tap again, and you get SPC SPC instead of ENT
• If you want tap-dance keys to be more forgiving than normal keys, get_tapping_term() lets you widen them. The documentation's example widens them to 275 milliseconds, and the stated reason is blunt: the author wants a short term (~175ms) for ordinary keys but finds that too fast to reliably complete a tap dance

The ceiling on this route:Vial still lacks autocorrect, leader key, OS detection and a batch of other features, which means custom builds.

Route three: real wireless plus long battery, and ZMK is a separate stack

This route fits split-keyboard users, and anyone who will not accept a wireless board that drops frames.

The cost is learning a different system. ZMK is designed for battery life and wireless maturity, built on Zephyr rather than QMK, with a different configuration path. One point in that third-party developer guide deserves quoting directly: the headline on the Q Ultra line is 660 hours of battery, but if the vendor's ZMK fork ships a configurator that makes you hand-write a devicetree file to remap a key, that line loses half its audience — and flattening the customisation curve with VIA was the whole appeal of the Q series. Confirm the configurator is graphical before buying.

Four live listings: official specs and real limitations

Everything below comes from vendor spec sheets and the product pages I fetched. I am not writing about "feel" or "value for money", because neither can be traced to a source.

Keychron K5 Max (B0DCNR5VJY) official specs: 108-key 100% full-height layout, Gateron low-profile switches, 2000mAh battery, 1000Hz on 2.4GHz and wired versus 90Hz on Bluetooth, STM32F402 MCU with 256KB flash, macOS/Windows/Linux. Three real limitations: the 100% full-height layout is not split, so it does nothing for anyone with wrist pressure problems; the 2000mAh battery is the smallest in this group, so do not expect endurance; and low-profile switches have short travel, meaning remapping cannot fix the feel of the switch itself.

👉 View Keychron K5 Max on Amazon

Keychron K2 Pro (B0C65JKDHF) official specs: 75% layout with 84 keys, Broadcom Bluetooth 5.1 for up to three devices, 1000Hz wired versus 90Hz wireless, 4000mAh battery, NKRO on both wired and wireless. This limitation belongs in the article because the product page states it: Keychron's own listing notes that the user can remap a key on wired mode only, and once done the keymap works on both wireless and wired. Remapping is wired-only. For anyone who wants to remap on the go, that is a hard limit. Its STM32L432 MCU carries 128KB flash — the smallest here — which starts to matter when you stack layers and macros over time.

👉 View Keychron K2 Pro on Amazon

Keychron Q11 (B0C9Q7S8CB) official specs: 75% split layout with 91 keys, full aluminium frame, works as a normal keyboard with a bridge cable, wired USB-C. The limitation that needs the most attention: it is a wired board with no wireless, which puts it outside route three entirely. The split design also adds learning cost for beginners, since each hand needs separate adaptation. And the product page I fetched showed it out of stock in some regions, so check availability before ordering. The genuine advantage: a bridge cable lets you use it as a conventional keyboard, which lowers the entry barrier to splitting.

👉 View Keychron Q11 on Amazon

Keychron Q1 Max (B0CR1JHZ6R) official specs: 75% layout, full-metal 6063 aluminium, CNC machined, ARM Cortex-M4 STM32F402 with 256KB flash, 1000Hz on 2.4GHz and wired versus 90Hz on Bluetooth, 4000mAh battery, south-facing RGB, double gasket mount, screw-in PCB stabilisers. Limitations: at from $189.99 it is the most expensive here; the official weight of 1724g makes it a desk-bound board rather than a portable one; and knob remapping depends on configurator support — third-party documentation notes that not all keyboards have added rotary encoder keycode support yet, so treat it as firmware-version dependent. It has the largest flash of the four and the most solid build, which makes it the one with the most headroom if you plan to stack layers and macros in QMK.

👉 View Keychron Q1 Max on Amazon

Troubleshooting: four things that genuinely block people

Your remap did not stick after saving. First check whether you did it over wireless. The K2 Pro note above already says remapping is wired-only. Connect by cable once, remap, then unplug.

The configurator does not see the keyboard at all. This is usually not a broken board. VIA needs a JSON definition imported manually while Vial relies on metadata stored on the keyboard, so the same symptom has a completely different cause in each tool. Vendor launchers also only recognise their own models, so a third-party board will never pair with one.

You cannot find the VIA download page. Not your problem. via.app is a domain for-sale page. If you need the VIA configurator, go through your keyboard vendor's official support page, or evaluate route two instead.

qmk doctor or the compile step errors out. The documented prerequisite is installing QMK's MSYS shell environment and then running qmk doctor. That first setup step is more painful than it sounds, and it is the real extra cost of route two over route one.

What I did not verify

Stating the boundaries, as this site always does:

• I have not physically used these four keyboards. Every spec comes from vendor spec sheets and product pages I fetched, not from measured feel.
• I have not compiled or flashed any QMK firmware. The tap-hold and tap-dance behaviours and defaults quoted above come from QMK's official documentation. I did not reproduce them locally. The SPC SPC example is the documentation's own failure example.
• "Over 3,000 keyboards" is qmk.fm's own claim. I did not audit the repository count.
• The Vial feature-gap list reflects April 2026 (Getreuer's wording). Vial is actively maintained, so gaps may have closed.
• Prices are from keychron.com. Marketplace price fields on the listings picked up same-category carousel prices during fetching and cannot be relied on. For the K2 Pro and Q11 I found no unified official site price and left those cells blank rather than guessing.
• Stock changes. The Q11 showed unavailable in some regions when I fetched it. Confirm before ordering.

FAQ

Is it still worth buying a keyboard labelled QMK/VIA just to remap keys?

Yes, but read the label for what it actually promises. QMK/VIA means the chip supports it; how far you can actually go depends on two things: whether the board shipped with VIA enabled, and whether the feature you want is exposed in the configurator. If your goal exceeds four layers or needs tap dance, plan for route two rather than hoping the VIA interface will stretch.

Can I install Vial on my Keychron?

It depends on the model. A third-party community project states that stock firmware locks you into the vendor launcher and upstream Vial will not install; the exception is wired-only models, which can run upstream vial-qmk as-is, while everything else — wireless models, or anyone needing RGB, Hall effect tuning or the wireless bridge — needs a community fork. That is a community project, not vendor support, and reflashing carries risk: interrupting a flash mid-write is the main way to cause real trouble. For a wireless board, staying on the vendor launcher is the safer call.

Are home-row mods actually worth learning?

One third-party developer guide calls them the biggest keyboard movement of 2025–2026, on the grounds that they redistribute the Ctrl/Shift load from the bottom-left corner across all fingers, and that the pinkies are a primary source of repetitive strain injuries. The cost is equally concrete: the first one to two weeks bring noticeably more typos, with fast typing especially prone to accidental modifier triggers. The documented mitigation is tuning the tap-hold timing, starting at 170–200ms and shortening it to match your typing speed, plus permissive hold. The same guide notes they work best on split, column-staggered boards and feel somewhat awkward on row-staggered 60/65% layouts.

Why is VIA capped at four layers, and can I change that?

You can, but it changes what the tool costs. Four layers is the VIA configurator's default ceiling, and exceeding it requires a QMK build environment and a reflash — and the moment you do that, you have already needed route two. So the correct use of that number is to make the requirement decision before buying, not to struggle with it afterwards.

Which of these boards should I pick?

If you are only remapping a few keys, the K5 Max has the lowest official price (from $71.24) and is sufficient. If you want wireless plus multi-device switching, the K2 Pro's 4000mAh and three-device Bluetooth are roomier than the K5 Max's 2000mAh, at the cost of accepting wired-only remapping. If flash headroom and metal construction matter most, the Q1 Max's 256KB flash is the largest of the four, at the highest price. And if what you actually want is a wireless split, none of these four delivers it — the Q11 is a split but wired-only.

👉 Join Xiaomi MiMo Platform: Leading AI model platform with cost-effective inference

👉 Join Aliyun AI: Top AI products with exclusive coupons for business innovation

📌 This article was AI-assisted generated and human-reviewed | TechPassive — An AI-driven content testing site focused on real tool reviews