VIA or VIAL: A No-Guessing Setup Guide for a Programmable Macro Pad

Customer and forum signal

Customer feedback praises the metal construction, knobs, screen, and stored keymaps, but repeatedly reports uncertainty about VIA versus VIAL, whether a JSON file is required, and why local software differs from the browser configurator.

Recommended opening

A programmable macro pad is only useful after the correct configurator recognizes it. The reliable starting point is not “try every VIA download.” It is to identify the exact model, follow the firmware path specified for that model, use a supported browser, and verify that the finished keymap survives a reconnect.

Content structure

1. Start With the Exact Model, Not the Product Family Name

2. VIA and VIAL Are Related, but They Are Not Interchangeable Instructions

3. When a JSON File Is Needed — and When It Is Not

4. Connect, Authorize, Map, Save, and Reconnect

5. How to Test a Knob, Layer Key, and Onboard Memory

6. A SKU-Specific Setup Matrix to Add Before Publication

Q&A

Q: Does every QMK macro pad use the same configurator?

A: No. QMK describes the firmware ecosystem; the user-facing configurator and connection flow still depend on the device firmware and model.

Q: When is a JSON file required?

A: A JSON definition may be required when the configurator does not already know the device layout. Use only the file supplied for the exact model and firmware revision.

Q: Does onboard memory mean the software is never needed?

A: The software is still needed to create or change the mapping. Onboard memory means the saved mapping can remain available after the device is moved to another supported computer.

Q: Why do customer reviews disagree about VIA and VIAL?

A: Different variants, firmware revisions, browser versions, and outdated instructions can produce different results. A model-by-model support table is more reliable than one universal claim.