简体中文
EnglishWhat Is QMK Firmware?
Updated
QMK Firmware is an open-source keyboard firmware for Atmel AVR and Arm USB families. It exists so that a keyboard's behavior — which key does what, how layers switch, what macros fire — is defined in software you control, not fixed by the manufacturer. If you want to remap, layer, or automate a compatible keyboard, QMK is the layer that makes that possible.
What problem it solves
Most keyboards ship with behavior burned in at the factory. You get the layout the vendor chose, and any customization stops at whatever their configuration tool exposes. QMK moves that logic into firmware you compile and flash yourself, so the keyboard's behavior becomes a file you edit rather than a setting you're allowed to change.
The project describes itself as "feature packed," "extensive compatibility," and backed by an "engaged community" — three claims that map onto the practical reasons people use it:
- Feature packed — a completely customizable, powerful firmware experience, per the project's own description.
- Extensive compatibility — it targets Atmel AVR and Arm USB microcontroller families, which is the hardware inside many custom and enthusiast keyboards.
- Engaged community — behavior, fixes, and keyboard definitions come from contributors rather than a single vendor.
What you can actually change
QMK's core value is that key behavior is programmable. In practice that covers:
| Area | What it means |
|---|---|
| Key mapping | Assign any keycode to any physical switch position |
| Layers | Multiple keymap layers you switch between, so one board can act like several |
| Macros | Sequences triggered from a single keypress |
| Per-key logic | Behavior that depends on modifiers, timing, or state |
The exact feature set depends on your keyboard's microcontroller and how its definition is written, so treat the list above as the category of things QMK enables rather than a guarantee for every board.
Who it's for
QMK fits you if you are building or modifying a keyboard whose controller is in the supported AVR or Arm USB families, and you want behavior that a stock configuration tool won't give you. It is a firmware project, so expect to work with source files and a build-and-flash workflow rather than a purely graphical app.
It is a poor fit if your keyboard's controller isn't supported, or if you only need a few remaps that the vendor's own software already handles.
How to get oriented
- Check compatibility first. Confirm your keyboard or controller falls under the Atmel AVR or Arm USB families QMK supports. This is the gate — nothing else matters if the hardware isn't covered.
- Find your keyboard's definition. QMK organizes support per keyboard, so locate the entry for your board before editing anything.
- Edit the keymap, not the core. Your changes belong in the keymap layer; the rest of the firmware is shared infrastructure.
- Build and flash. Compile the firmware and write it to the controller, then test the result on the board.
The expected result at each step is a working build you can flash; if a step fails, the usual cause is a mismatch between your keyboard's definition and the controller you actually have.
The takeaway
QMK Firmware is the open-source layer that turns a compatible keyboard's behavior into something you define in code. Its scope is Atmel AVR and Arm USB hardware, its purpose is full customization of keys, layers, and macros, and its practical limit is compatibility — check that before you invest time in a keymap.