Keychron Per-Key RGB Not Working: Fix VIA Lighting Layers and Firmware Fast

Published on 2026-11-08 ยท 7 min read ยท By MiniTestLab Engineering Team ยท Category: Keyboards

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester

Your Keychron per-key RGB is almost certainly sitting on a disabled or zeroed-out lighting layer in VIA, not a dead LED strip. Keychron boards running QMK store RGB state in EEPROM, and that stored state survives firmware flashes, so a bad layer value written during a VIA session or a partial flash can black out every LED while the controller itself is fully functional. Physical LED failure across an entire keyboard is statistically rare; what you are seeing is almost always a software or firmware state problem.

Confirm the Scope Before You Touch VIA

Before opening VIA, use the Keyboard Test to verify that the keyboard is registering keystrokes at all. If no keys register, you have a USB or firmware problem, not an RGB problem. If keys register normally but all LEDs are dark, you are in the right place.

Run through this quick scope check first:

Fix Lighting Layers Inside VIA

VIA 3.0 and later handles RGB through the Lighting tab, not through keycode assignments. Older VIA 2.x builds put lighting controls under a dedicated layer. The procedure differs slightly.

  1. Download VIA from usevia.app. Do not use a cached or offline copy older than six months; Keychron has pushed definition file changes that break older VIA builds.
  2. Connect the keyboard and confirm VIA detects it. If VIA shows "No devices found," your board needs its JSON definition loaded manually. Go to Settings, enable "Show Design tab," then load the correct JSON from Keychron's GitHub repository under qmk_firmware/keyboards/keychron.
  3. Click the Lighting tab. You will see two sliders: Brightness and Effect Speed, plus an Effect selector dropdown.
  4. Set Brightness to 255. If it was already at 255, drag it to 0, wait two seconds, then drag it back to 255. This forces a new EEPROM write.
  5. Set Effect to anything other than "None" or effect index 0. Effect index 0 is solid off on several Keychron firmware builds, which is confusing because it appears selected by default after a partial flash.
  6. For per-key color control specifically, select effect "Custom" or "Solid Color" and then use the Key Lighting section to paint individual keys. If the Custom option is missing, your firmware does not have RGB_MATRIX_CUSTOM_USER compiled in, which means you need a firmware update.

After making changes, disconnect and reconnect the USB cable. VIA writes to EEPROM asynchronously and a cold reconnect confirms the values actually persisted.

Firmware Version and QMK Flash Procedure

Keychron per-key RGB not working after a firmware update almost always means the new firmware binary has RGB_MATRIX_ENABLE = yes but the EEPROM from the previous version stored an incompatible lighting struct. QMK does not automatically wipe EEPROM on version mismatch unless the developer bumped EECONFIG_VERSION in config.h.

The fix is an EEPROM reset. Here is the exact process for QMK Toolbox:

  1. Open QMK Toolbox. Set MCU to STM32L432 for Q-series boards or ATmega32U4 for older K-series boards. Check your board's product page or the PCB silkscreen to confirm.
  2. Put the keyboard into bootloader mode. On most Keychron QMK boards: hold Escape while plugging in USB. On Q-series with the reset button on the PCB, press that button once with a straightened paperclip through the hole on the bottom case.
  3. In QMK Toolbox, click "Clear EEPROM" before flashing. QMK Toolbox will show "EEPROM cleared" in the log.
  4. Flash the latest firmware bin from Keychron's GitHub releases page. Confirm the filename contains your exact model number and layout (ANSI vs ISO, keyboard size).
  5. After flash completes, disconnect, wait 10 seconds, reconnect. Open VIA and set brightness and effect as described above.

If you are on a Mac and QMK Toolbox is not available, use the command line: qmk flash -kb keychron/q1/ansi_encoder -km via after putting the board in bootloader mode. Replace the keyboard path with your actual model path from the QMK firmware tree.

Per-Key RGB vs Zone RGB: What Your Board Actually Supports

Not every Keychron keyboard supports true per-key RGB even if it has RGB lighting. This table covers the main current lines:

Series Per-Key RGB RGB Matrix Driver VIA Support
Q-series (Q1, Q2, Q3, Q5, Q6) Yes ISSI IS31FL3741 or IS31FL3733 Yes, JSON required
V-series (V1, V2, V3) Yes ISSI IS31FL3733 Yes, JSON required
K-series (K2, K6, K8) older revisions No, side RGB only WS2812 strip Limited
K-series newer revisions (K2 Pro, K6 Pro) Yes ISSI IS31FL3733 Yes
C-series No WS2812 underglow only No

If your board is a K2 revision A or B, the LEDs under each key are single-color white. You cannot get per-key color from those boards regardless of VIA settings. Revision C and later switched to RGB SMD LEDs. Check the sticker on the bottom of the case for the revision letter.

If your keychron backlight not working issue is isolated to a single key rather than the whole board, that is a dead SMD LED, which requires soldering. The LED footprint on Q-series boards is SK6812MINI-E. Replacements are available from LED suppliers for under $5 per strip of ten. You will need to remove the switch above the dead LED, desolder the LED pads, and reflow a new unit. Check the LED orientation mark on the PCB silkscreen before soldering.

While you have the board open for any repair, verify the ribbon cable connecting the PCB to the daughter board (present on some Q-series layouts) is fully seated. A partially lifted ZIF connector on that ribbon will kill RGB on one half of the board while leaving the other half functional.

After any hardware or firmware change, run the Keyboard Test again to confirm full key registration alongside the restored RGB. If you suspect a polling or connectivity issue introduced during the repair, the Mac Keyboard Test is useful for Apple silicon machines where USB-C adapters sometimes throttle HID polling.

Frequently Asked Questions

Why does my Keychron RGB turn off after every reboot?

EEPROM is not persisting your VIA lighting settings. This happens when the EEPROM address space for RGB_MATRIX conflicts with another QMK feature using the same memory offset, which is a firmware bug. Flash the latest firmware, clear EEPROM in QMK Toolbox, and set your lighting values fresh. If it still resets, check whether your firmware was compiled with NKRO_ENABLE = yes alongside RGB_MATRIX_ENABLE = yes; on ATmega32U4 boards that combination can overflow EEPROM allocation.

VIA does not show a Lighting tab on my Keychron. Where is it?

Your board's JSON definition file does not include the lighting menu entries, or you are using a VIA version older than 2.6. Load the latest JSON from Keychron's official GitHub under /qmk_firmware/keyboards/keychron/your_model, then reload VIA. The Lighting tab appears automatically once VIA reads a definition that declares rgb_matrix support.

My Keychron RGB works in Windows but not in macOS. What is different?

Nothing in the keyboard firmware changes between operating systems; RGB state lives in EEPROM. What changes is USB power delivery. macOS aggressively suspends USB devices. Go to System Settings, Battery, Options and disable "Enable Power Nap" and "Wake for network access." Also check that the USB port is not set to low-power mode via a third-party app like Endurance or coconutBattery's port limiter.

Can I use Keychron's Launcher app instead of VIA for RGB control?

Keychron Launcher is available for Q Pro and K Pro series boards that use Bluetooth and have the Keychron-specific firmware variant. It does not work with standard QMK firmware. If you flashed a community QMK build, Launcher will not detect the board. Stick to VIA for any board running QMK.

One row of LEDs is out but the rest work fine. Is this a firmware issue?

No. A full row going dark while others work points to a failed LED driver channel on the ISSI IS31FL3733 or IS31FL3741 IC, or a broken trace feeding that row. Firmware and VIA cannot fix a hardware driver failure. Check the IC under magnification for lifted pads or flux bridges. If the IC is damaged, replacement requires hot air rework and is not a beginner repair.

Does clearing EEPROM delete my VIA keymaps?

Yes. EEPROM clear wipes all stored layers, macros, and lighting settings. Export your keymap JSON from VIA before you clear EEPROM. In VIA, go to File, Export Keymap, and save the JSON file. After reflashing and clearing, import it back through File, Import Keymap.

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Keyboard Tester