Keychron Not Discoverable: How to Actually Enter Pairing Mode on Every Model
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Keyboard TesterYour Keychron is not discoverable because you have not completed the full pairing sequence for your specific model, or the physical Bluetooth/cable switch is in the wrong position. Keychron uses at least three distinct pairing mechanisms across its product line, and the steps are not interchangeable. The keyboard's onboard BT module, typically a Nordic nRF52840 on newer models or a TLSR8208 on older Q and C series boards, will not broadcast if the mode switch is set to wired, if a previously paired profile is blocking the slot, or if the firmware is in a locked state after a botched update.
Physical Switch Check Before Anything Else
Every Keychron with Bluetooth has a physical mode switch on the left side of the board. It has three positions: Off, Cable (USB), and Bluetooth. If that switch is sitting on Cable, the BT radio is completely powered down in hardware. No amount of key combinations will make it discoverable. Slide it to Bluetooth first. Then confirm your host device has Bluetooth enabled and is not currently connected to a different Keychron profile occupying the same slot.
On the K-series slim boards (K1, K2, K3, K7, K8), the switch is a physical rocker on the left spine. On the Q-series and V-series (Q1, Q2, Q3, V1, V2, etc.), the same three-position slider is present but recessed slightly. On the B-series (B1 Pro, B6 Pro), the switch is identical in function but the board defaults to USB HID mode on first power-on even with the switch in the BT position, so you must still run the pairing sequence manually.
Pairing Mode Sequences by Model Family
Use the table below to find your exact sequence. "Fn" refers to the dedicated Fn key on full and TKL layouts, or the rightmost modifier key on compact layouts where Fn is embedded.
| Model Family | Pairing Key Combo | Indicator | Timeout |
|---|---|---|---|
| K1, K2 (v1/v2), K3, K4, K6, K7, K8 | Fn + 1, 2, or 3 held 3 seconds | Blue LED flashes rapidly on selected slot key | 3 minutes |
| K10, K10 Pro, K11, K12, K14 | Fn + 1, 2, or 3 held 3 seconds | Blue LED on number key, rapid blink | 3 minutes |
| Q1 Pro, Q2 Pro, Q3 Pro, Q5 Pro | Fn + 1, 2, or 3 held 4 seconds | Blue LED rapid blink; no blink means switch is on Cable | 5 minutes |
| B1 Pro, B6 Pro | Fn + 1, 2, or 3 held 3 seconds after switching to BT mode | Blue LED blinks 3 times then rapid blink | 3 minutes |
| K3 Pro, K7 Pro, K9 Pro | Fn + 1, 2, or 3 held 3 seconds | Blue LED rapid blink on slot key | 3 minutes |
| V1, V2, V3, V6 | Fn + 1, 2, or 3 held 3 seconds | Blue LED rapid blink; RGB boards show blue pulse on all keys | 3 minutes |
Hold the combination for the full duration. Tapping it briefly toggles to an already-paired profile, it does not open a new pairing advertisement. If the LED does not blink rapidly after 4 seconds, the switch is not in the BT position or the battery is critically low.
Why the Keyboard Still Does Not Show Up After the Correct Sequence
If you ran the right combo and the LED is blinking but the host still does not see the keyboard, work through these in order:
- Slot already paired to another device. Keychron stores one device per slot (1, 2, 3). If slot 1 is paired to your phone and that phone is powered on nearby, the keyboard will auto-reconnect to the phone instead of advertising as new. Power off the previously paired device or use a different slot number.
- Battery below 10%. The nRF52840 BT radio draws enough current during advertising that a depleted cell causes the keyboard to drop out of pairing mode within seconds. Plug in via USB-C and charge for 20 minutes before retrying. The battery is a 3.7V lithium cell rated between 1500mAh (K3) and 4000mAh (K10) depending on model.
- Host Bluetooth stack cached a broken pairing. On Windows 11: Settings > Bluetooth and devices > find the Keychron entry > Remove device. On macOS 13 and later: System Settings > Bluetooth > hover the device > click the X > Remove. On iOS 16+: Settings > Bluetooth > tap the i icon > Forget This Device. After removing, run the pairing sequence again on a fresh slot.
- Firmware lock after incomplete QMK flash. Q-series and V-series boards running QMK can enter a state where the BT subsystem is unresponsive after a partial flash. Connect via USB, open QMK Toolbox 0.3.2 or later, confirm the board enumerates as a HID device, and re-flash the factory firmware from Keychron's firmware page for your exact model revision before attempting BT again.
- 2.4GHz RF congestion. In dense Wi-Fi environments, channel overlap between 802.11b/g/n on channels 1, 6, 11 and Bluetooth's frequency-hopping spectrum causes dropped advertisement packets. Move the keyboard within 1 meter of the host for initial pairing.
After you confirm pairing works, you can verify all keys register correctly using the Keyboard Test tool directly in your browser without installing any software.
Comparing Bluetooth Performance Across Keychron Generations
Not all Keychron Bluetooth implementations are equal. The older TLSR8208-based boards (K1 original, K2 v1, K8 original) have a shorter effective pairing range and slower reconnect time than the nRF52840 boards introduced around 2021.
| BT Chip | Models | BT Version | Typical Reconnect | Max Reliable Range |
|---|---|---|---|---|
| TLSR8208 | K1 (original), K2 v1, K8 original | Bluetooth 3.0 | 4-8 seconds | 5 meters |
| nRF52840 | K2 v2, K3, K3 Pro, K7, Q-Pro series, V-series | Bluetooth 5.1 | 1-3 seconds | 10 meters |
If you own a TLSR8208 board and it stops being discoverable entirely, the chip's firmware is stored in internal SPI flash and cannot be updated by the end user. At that point the BT module is effectively end-of-life and wired use is the only reliable option.
If you suspect intermittent key dropout rather than a pure pairing problem, run the Keyboard Test over a wired connection first to isolate whether the issue is in the switch matrix or in the wireless layer. You can also use the Mac Keyboard Test if you are on macOS and want a layout-specific check.
Frequently Asked Questions
Why does my Keychron show up in the Bluetooth list but fail to connect?
The keyboard is advertising on a slot that already has a stored pairing key for a different host. Your new device can see the advertisement but cannot complete the handshake because the keyboard's stored link key does not match. Run Fn + the slot number for 4 seconds to clear and re-advertise that slot as unpaired, then connect from the new host.
Does the Keychron K2 v1 support Bluetooth 5?
No. The K2 version 1 uses the TLSR8208 chip, which is Bluetooth 3.0. Only K2 version 2 and later models moved to the nRF52840 with Bluetooth 5.1. Check the sticker on the bottom of the board: it will say V1 or V2 explicitly.
My Keychron was working yesterday and is not discoverable today. What changed?
The most common overnight cause is a previously paired device, such as a phone or tablet, powering on and auto-claiming the slot before you sit down at your computer. The keyboard reconnects to the first device that responds and stops advertising. Power off the other device, or switch to an unused slot with Fn + a different number and pair fresh.
Can I use Keychron's Bluetooth and USB simultaneously?
No. The physical three-position switch is a hardware selector, not a software toggle. When the switch is in the Cable position, the BT radio receives no power. There is no mode that runs both simultaneously on any current Keychron model.
How do I know if my Keychron's battery is too low to pair?
On RGB models, the battery indicator is Fn + B. A red light means below 15%. On non-RGB models, the only indicator is the BT LED dropping out of rapid-blink mode within 5 seconds of starting the pairing sequence. Plug in via USB-C and charge until the charging LED turns off or turns solid before retrying.
Will resetting the keyboard to factory defaults fix a persistent Bluetooth issue?
On Q-series and V-series boards running QMK, you can reset by holding Escape while plugging in USB, which puts the board in bootloader mode and clears the EEPROM on the next firmware flash. On K-series and B-series boards, there is no user-accessible factory reset. Clearing all three pairing slots by holding Fn + 1, Fn + 2, and Fn + 3 each for 4 seconds on a fresh charge is the closest equivalent and resolves the majority of persistent pairing failures.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Keyboard Tester