What Is a Programmable Macro Keyboard?

When you see "programmable" on the box, it usually means one of two approaches, and plenty of boards combine them.

The first one adds extra keys. There's a column or a row of blank keys sitting beside the normal layout, usually down the left edge, and they do nothing until you assign them. The rest of the keyboard stays fixed: Q is still Q, Caps Lock is still Caps Lock. Gaming keyboards have been built this way for years, and you use the maker's software to tell each extra key what to do.

The second one lets you change any key you like. Caps Lock can become Control. That key next to the space bar you never touch can open your email. Any key can carry a macro. Keyboards built on open-source firmware work this way, and a few mainstream makers now offer a web-based configurator that does the same.

Both of them get called programmable. If you just want a few shortcut buttons next to a layout you already like, the first approach will do it. If you want to fix a layout you've always hated, only the second one will.

A remap is one key sending one different key. If you swap Caps Lock and Escape, that's a remap. Nothing clever is happening; the keyboard is just reporting a different key than the one printed on the cap.

A macro is one key sending a whole sequence. Your email address, typed out for you. "Select all, copy, switch window, paste." On some makers' assignment menus these show up as separate choices: a single keystroke, a block of text, or a recorded series of keys with the timing in between.

A layer is a second map of the whole keyboard that's only active while you hold a key down, or until you toggle it off. If you've ever used a laptop, you already use one: hold Fn and the F-keys turn into brightness and volume. Compact keyboards lean on layers heavily. A board with no arrow keys puts the arrows on a layer under the keys you'd expect to find them near, and tucks that layer behind a key your right thumb can reach. Open-source firmware will let you have dozens of layers. There's more on what compact layouts give up in our guide on keyboard sizes, which is linked at the end.

It lives in one of two places, and this is the question to ask before anything else.

The first place is inside the keyboard. The firmware, or a block of memory on the board, holds your layout and your macros. Plug the keyboard into another computer and everything just works, with nothing installed. Open-source firmware keeps the keymap on the keyboard by design, and a web configurator that talks to that firmware writes your changes to the board as you make them. The gaming brands call their version onboard memory or onboard profiles. Logitech, for one, describes it the same way: store the settings on the device itself and carry them to another computer without installing its software.

The second place is on your computer. The keyboard sends ordinary key presses and a program on your computer catches them and does the clever part. That's how the macro keys on many gaming keyboards work out of the box. You get more this way: profiles that switch on their own when a game launches, and macros that can open a file or a web page instead of only typing keys. The catch is that it only works where that program is installed and running.

If you only ever use one machine, you'll barely notice the difference. If you move between a work laptop you can't install software on and a desktop at home, it's the whole decision.

Not always, and that's the thing to know before you buy.

Two makers say as much on their own support pages. Razer's page on onboard memory says that "the ability to save macros on-board depends on your device model" and that "some Razer devices require Razer Synapse to be running for macros to function." Logitech's support page on its onboard memory mode lists macro types that simply don't work in that mode, including text-and-emoji macros and anything set to repeat while the key is held. Razer's page also says lighting effects can't be saved to the device at all; the software has to be running for those.

So a keyboard can honestly say onboard memory on the box, honestly store your key remaps, and still need its app open for the one macro you actually bought it for.

There's a second trap too. Some keyboards let you record a macro on the fly, with no software at all: press a record key, type the sequence, press stop. On open-source firmware, that kind of recording sits in working memory and is "lost when the keyboard is unplugged or otherwise rebooted", with a limit of around 128 keypresses across the slots. Whether a maker's on-the-fly recording survives a power cycle depends on the model. Assume it doesn't until the manual tells you otherwise.

What to look for: the number of onboard profiles on the spec sheet (by Razer's description, a device with one profile only stores the last one used), and the maker's support pages on macros in onboard mode, which tend to say more than the product page does.

It can. At least one major competitive shooter spells it out: Ubisoft's core rules for Rainbow Six Siege, dated July 2026, list "using adapters or devices to run macros, rapid-fire scripts, or automation" under cheating. Other publishers write their rules differently and enforce them differently, and the shorthand you'll hear from players, one key press for one action, is a rule of thumb rather than anything a publisher has written down. Read the rules of the game you play before you bind anything that fires more than once.

Two things follow from that. A macro stored in the keyboard's firmware sends the same key presses as one driven by software, so a rulebook that bans macros doesn't care where yours lives. Whether a game's anti-cheat can tell the two apart is a separate question, and not one to bet an account on. And a plain remap, one key sending one other key, isn't a macro at all. The board that lets you move Escape onto Caps Lock isn't what a rulebook like Ubisoft's is describing; the key that fires four actions is.

A macro pad is the extra-keys design sold on its own: a small block of programmable keys that sits next to whatever keyboard you already own. You keep the keyboard you like and add the shortcuts beside it, at the cost of a bit of desk space and one more cable or dongle. Everything above about where the programming lives applies here too.

Stream-deck-style controllers look similar, but they aren't the same thing. Each key is a little screen that shows you what it does, and the device is driven by its app on the computer. A macro pad sends keystrokes; a screen-key controller sends instructions to its software. If you're controlling apps while you stream, the screens earn their keep. If you've already memorised your shortcuts, a macro pad does the job with less to go wrong.

Your password. Or anything else you'd mind a stranger reading.

The QMK project, an open-source keyboard firmware, puts it bluntly: sending passwords or card numbers from a macro is "a supremely bad idea", because anyone who gets hold of the keyboard can read them back by opening a text editor and pressing the key. The same goes for a macro saved in a maker's app.

Five things, in the order they'll matter to you.

1. Which keys are programmable: every key, or a few extra ones beside the layout.

2. Where the programming lives: in the keyboard, or in an app. And if it's an app, whether it runs on your operating system.

3. Whether macros, and not just remaps, are stored on the keyboard, and how many profiles it holds.

4. Whether the configurator needs a cable. Some web configurators only see the keyboard over USB and only in certain browsers, so a wireless board may need plugging in to change anything.

5. If you play ranked games, what the game's own rules say about macros.

The keyboard guide linked below covers layouts and sizes, which is where layers come from in the first place, and the mouse guide covers the same onboard-profile question for the other hand.