✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.
⭐ Key Takeaways
Quick answer: Our top pick is Logitech G600 MMO Gaming Mouse, with Logitech G502 HERO as a strong alternative.

Most Linux remapping advice stops at the gamepad. Steam Input rewrites a controller inside Steam, AntiMicroX turns pad buttons into keystrokes, and vendor suites such as Logitech Options or Razer Synapse do not exist for Linux, leaving extra buttons on mice, keypads and keyboards stuck with their firmware defaults. Input Remapper attacks the problem one level lower: it sits at the kernel input layer and rewrites events from keyboards, mice, gamepads and wheels before any application sees them.

That position gives it an unusual reach: a mapping applies in Steam and outside it, in a native port and in a Windows game running through Proton, because the game reads a virtual device the tool created. This article explains how it works, where its documented limits sit, how it compares with AntiMicroX, and which hardware gives it the most to work with.

As an Amazon Associate, we earn from qualifying purchases.

Quick answer

Input Remapper is a free Linux tool that rewrites what your keyboard, mouse and gamepad buttons do, system-wide. It reads devices at the kernel input level and injects remapped keys, combinations and macros through virtual devices, so it works on Wayland and X11 alike. Mappings live in per-device presets that can load automatically when hardware connects.

What Input Remapper actually does

The mechanism is deliberately low-level. A background service reads the real device’s events from the kernel input subsystem; when a mapping matches, the event is replaced and injected through a virtual keyboard or mouse the tool creates. The graphical interface is only the editor: the documentation notes that the daemon maps independently of the GUI, so a preset keeps working after the window closes.

The mapping vocabulary is broad. A key or button can become another key, a chained combination written in the form Control_L + a, a mouse button or movement, or a macro firing a timed sequence of events. Inputs can be combinations too: record several keys or an axis movement together and the mapping fires only when all are active, with adjustable analog thresholds. A mapping can also point at the word disable, which swallows the input entirely. Analog axes map to analog outputs with sensitivity, deadzone and non-linearity controls, so a gamepad stick can drive the mouse pointer, and both ordinary and high-resolution wheel events can be mapped, though the two wheel types may need separate handling.

Installation follows the usual distro routes: a package for Debian and Ubuntu, the Fedora and Arch repositories, and a system service to enable. Reading raw device events needs elevated permissions, and the service holds them, not your desktop session.

Input Remapper or AntiMicroX: which layer do you need?

AntiMicroX and Input Remapper overlap, but they aim at different centres of gravity. AntiMicroX is gamepad-first: it takes a controller and produces keyboard and mouse output, so games with no controller support can still be played on a pad. Its profiles, sets and turbo-style features are all organised around that one job.

Input Remapper is device-agnostic. The same preset system covers a keyboard, an MMO mouse with a thumb grid, a one-handed keypad and a gamepad, and because it injects at the input layer rather than translating for one game, a mapping follows the device everywhere. If your problem is a controller a game ignores, AntiMicroX is the more focused tool. If your problem is buttons on your desk doing nothing useful on Linux because the vendor software is Windows-only, Input Remapper is the one built for it.

Why it works on Wayland and X11 alike

Tools that inject input through the display server hit a wall on Wayland, because compositors deliberately restrict that. Input Remapper never talks to the display server at all: it reads the physical device below the compositor and injects keycodes through a virtual device. The README states support for X11 and Wayland outright, and the usage documentation explains the trade: the virtual device behaves like a USB keyboard, compatible with all display servers, but the environment’s layout ultimately decides which character a keycode produces.

That trade is the tool’s most important documented limitation. Input Remapper works in symbol names, and it can only inject what your fingers could type on the configured layout. A character that needs a combination cannot be injected directly; the documented workaround is to map the combination itself, such as Shift_L + 1. Layout-independent key constants exist, but the documentation warns they can surprise on non-US layouts.

Presets, autoload and the injection workflow

Day-to-day use follows a simple loop: pick a device, create a preset, record an input by pressing the button you want to change, type the output, and press Apply to start the injection. Changes save automatically. To edit an input later you stop the injection first: while the daemon runs, the original event never reaches the interface to record again.

Presets are per device, and autoload makes them practical: the configuration file names a preset for each device, and when it connects, the service loads the preset without opening the GUI. Two documented recovery notes belong in any honest summary: if a macro leaves a key hanging, unplugging and reconnecting resets it, and if an autoloaded preset leaves a device unusable, unplugging and plugging in twice stops the injection. Presets are plain configuration files, easily backed up or copied between machines.

What the tool does not do natively is switch presets per application: autoload reacts to devices connecting, not to windows gaining focus. The documentation lists a community add-on that watches the focused application and swaps presets, which tells you the demand exists but is not core behaviour. Game-specific layouts mean keeping several presets and switching manually, or leaving per-game work to Steam Input.

Five devices that give Input Remapper plenty to work with

The tool is free, so the buying question is which hardware benefits most: extra inputs whose vendor software does not run on Linux, such as thumb grids, keypads and back buttons. All five devices below report through the kernel input layer Input Remapper reads.

Logitech G600 MMO Gaming Mouse

Logitech G600 MMO Gaming Mouse

Logitech G600 MMO Gaming Mouse

Check price on Amazon

The G600 is the classic case: a twelve-button thumb grid plus a G-Shift button that doubles it, and configuration software with no Linux version. A preset can turn that grid into numpad keys, shortcuts or macros for an MMO hotbar.

Specs

  • Buttons: 20 programmable, including a 12-button thumb panel
  • Sensor: laser, 200 to 8,200 DPI
  • Connection: wired USB
  • Model: 910-002864

Logitech G502 HERO

Logitech G502 HERO

Logitech G502 HERO

Check price on Amazon

The G502 HERO spreads fewer extra buttons well: side buttons, a DPI shift button and clickable wheel directions give Input Remapper half a dozen inputs most Linux players leave at defaults. It is the pick for a shooter mouse that still carries remappable extras.

Specs

  • Sensor: HERO 25K optical, 100 to 25,600 DPI
  • Buttons: 11 programmable
  • Connection: wired USB
  • Extras: five adjustable 3.6 g weights
  • Model: 910-005469

Razer Tartarus V2 Gaming Keypad

Razer Tartarus V2 Gaming Keypad

Razer Tartarus V2 Gaming Keypad

Check price on Amazon

The Tartarus V2 is a one-handed keypad with 32 programmable keys, an eight-way thumb pad and a scroll wheel. On Linux, OpenRazer covers its lighting, and the OpenRazer project itself notes that key rebinding on its keypads is a job for a third-party tool such as Input Remapper. Every key is an ordinary key event waiting for a preset.

Specs

  • Keys: 32 programmable, mecha-membrane switches
  • Thumb controls: 8-way directional pad, 3-way scroll wheel
  • Connection: wired USB-A
  • Model: RZ07-02270100-R3U1

8BitDo Pro 2 Bluetooth Controller

The Pro 2 adds two back buttons many games never see: map them to keys the game does understand and they work in any title. Its maker’s configuration app covers other platforms, so on Linux it is a standard Bluetooth or wired controller, and system-level remapping is how the extras get used.

Specs

  • Connection: Bluetooth, USB-C wired
  • Back buttons: 2; rumble and 6-axis motion in Switch mode
  • Modes: Switch, X-input, D-input and macOS modes
  • Battery: 1,000 mAh, maker-rated up to 20 hours

Keychron V3 Mechanical Keyboard

Keychron V3 Mechanical Keyboard

Keychron V3 Mechanical Keyboard

Check price on Amazon

The V3 is the counterpoint: a keyboard whose QMK firmware already remaps keys and stores them on the board, travelling between machines with no software at all. It marks the boundary of what Input Remapper is for — the tool exists for the mice, keypads and pads that cannot do this trick.

Specs

  • Layout: 87-key tenkeyless, knob version
  • Firmware: QMK and VIA support, hot-swappable switches
  • Switches: Keychron K Pro Brown
  • Connection: wired USB-C

How to choose

Start from the device, not the tool. List the desk inputs that currently do nothing useful on Linux. If they belong to one gamepad and one unsupported game, AntiMicroX or Steam Input is the shorter path. If they span a mouse, a keypad and a keyboard, or you need the same mapping inside and outside Steam, per-device presets are the right shape.

Check the layout question next. If your planned mappings are ordinary keys, shortcuts and macros, the symbol limitation will not bite. If you hoped to put characters from another layout on spare buttons, plan around combinations instead.

Finally, think about how you play. Players who live inside Steam often need Input Remapper only for the mouse and keypad, Steam Input covering the controller. Players spread across launchers and Proton titles benefit most from mappings that live below all of that. Where a device offers firmware-level remapping, as the Keychron does, prefer the firmware and save this tool for hardware that has none.

Who should skip this

Skip Input Remapper if all your gaming happens inside Steam and your only device is a mainstream controller: Steam Input already does per-game layouts with a friendlier interface, and a second remapping layer invites confusion about which one produced an input. Skip it if you are uncomfortable enabling a system service with access to your input devices, because that access is the entire mechanism.

Also skip it if you need per-application switching as a core feature, since autoload is per device and per-window behaviour lives in a community add-on. And if your devices already store QMK, VIA or onboard profiles you are happy with, it adds a moving part without adding capability.

FAQ

Does Input Remapper work on Wayland?

Yes. The project states support for X11 and Wayland, and the reason is architectural: it reads the physical device and injects through a virtual keyboard at the kernel input level, below the compositor, so display-server restrictions do not apply. The caveat is that your keyboard layout decides which characters the injected keycodes produce.

Can Input Remapper remap a gamepad as well as mice and keyboards?

Yes. The project lists gamepads, joysticks, wheels and triggers among its input types, and analog axes can map to other axes, to mouse movement or, past a threshold, to keys and macros. For a pad whose game has no controller support, AntiMicroX is the more specialised option, but Input Remapper covers pads within a whole-desk setup.

Is Input Remapper a replacement for my mouse or keyboard software?

Partly. It replaces the remapping function of vendor suites that do not exist on Linux, the function most players miss. It does not replace firmware settings such as DPI stages, polling rate or lighting stored on the device; those belong to tools like Piper and Solaar, or the maker’s software on another operating system.

Final verdict

Input Remapper fills a specific and common hole in a Linux gaming setup: the buttons that vendor software forgot. Its design is sound, documented honestly, and robust across the Wayland transition precisely because it never depended on the display server. The limitations are real but well-signposted: it injects what your layout can type, it switches presets per device rather than per game, and it asks for a system service with input access in exchange for its reach. For a desk built around an MMO mouse, a keypad or a pad with back buttons, it is the missing layer.

Explore Our Guides & Free Tools