AntiMicroX is a free, open-source program for Linux and Windows that maps gamepad buttons and axes to keyboard keys, mouse movement and clicks, scripts and macros. Version 3.6.1, released in May 2026 under the GPL-3.0-or-later licence, is a small maintenance release, and it works the same way whether you are setting it up for a desktop game with no controller support or for controlling an ordinary application from the sofa. This guide walks through the whole first session in order: install the program, connect a controller, create a profile, assign your first keys, test the result in a real game and save everything so you never have to repeat the setup. If you only want the files, start on the AntiMicroX download page; if you want to understand profiles first, read the guide to AntiMicroX profiles alongside this tutorial.
What AntiMicroX does — and what it does not do
AntiMicroX sits between your controller and your other software. When you press a button, the program sends the keyboard key, mouse action, script or macro you assigned to that button, and the game or application simply sees that input. That is why it is useful for older games, emulators, media players and desktop tools that were never designed for a gamepad. It can also generate an SDL2 game-controller configuration, which helps an unusual gamepad behave like a generic Xbox 360-style layout in SDL2-based software. Detection itself is handled through SDL2, so the practical rule is simple: if SDL2 recognises your controller, AntiMicroX can usually work with it. There is no official by-name compatibility list from the project, and no controller should be described as officially guaranteed. AntiMicroX runs on Linux and Windows only. There is no official macOS version and no official Android or iOS app, so any download claiming otherwise is not from this project.
Step 1: Install AntiMicroX
Download version 3.6.1 only from the official GitHub Releases channel, either directly or through the links on our download page. On Windows you have two choices: the AMD64 installer or the portable zip that runs without installation. Both Windows builds are 64-bit only, and both are unsigned, so Windows may show an unknown-publisher or SmartScreen prompt. That is expected for this project; it is not, on its own, proof that a file is harmful, and it is also not a guarantee that a file is safe. The sensible check is the SHA-256 hash published with the GitHub release, which our download page reproduces. On Linux you can use the .deb packages, the AppImage, the Flatpak or a distribution package. Our separate AntiMicroX on Linux guide explains those routes in more detail. Once installed, launch the program before you open any game, so the profile is already active when the game starts.
Step 2: Connect your controller
Connect the controller the way you normally use it, wired or wireless, and then look at the main AntiMicroX window. A recognised controller appears as a device you can select and configure. Press a few buttons and move each stick: the matching control in the window should react, which confirms the program is receiving input before you assign anything. If nothing reacts, close other software that might be claiming the device, reconnect the controller and restart AntiMicroX. On Linux, the project documentation points users to tools such as sdl2-jstest and evtest when they need to check whether the system and SDL2 see the device at all. Get a clean, visible response in the AntiMicroX window first, because every later step depends on that one fact: the program can see the controller and identify each control correctly.
Step 3: Create your first profile
A profile is the file that stores every assignment for one controller layout. AntiMicroX profiles use the .amgp format, and one profile can hold far more than a single set of button mappings, as later sections explain. For your first profile, keep the goal narrow: pick one game or application, list the five or six keyboard keys it uses most, and map only those. Start from the controller view, select a button, and open its assignment. The interface separates ordinary assignments from advanced slots, and for a first session you should ignore the advanced options completely. Choose a key, confirm it, and move to the next button. A small, finished profile you understand is worth much more than a large profile copied from someone else that you cannot debug. When the basics work, use our profile creation guide to learn how saving, loading and organising .amgp files works, including how to reuse one good layout as the starting point for the next game instead of rebuilding from zero each time.
Step 4: Assign keys, mouse actions and more
Each button, trigger, stick direction or D-pad direction can send a keyboard key, a mouse button, mouse movement, a script or executable, or a macro built from several actions. Begin with keyboard keys, because they are the easiest to test. A practical order is to map movement and confirmation actions first, then menu and cancel actions, and only then anything optional. Write down what you assigned as you go; after twenty assignments, nobody remembers them all reliably. For sticks, pay attention to deadzones. A deadzone is the small area around the centre where input is ignored, which prevents drift. Project guidance notes that 8000 is the typical XInput profile value, while a value around 2000 was suggested from the author’s own experience with a Logitech F310, so treat those numbers as starting points to adjust, not rules.
- Map movement and confirm actions first, so the layout is usable early.
- Test every assignment immediately after making it.
- Adjust one deadzone or sensitivity value at a time.
- Save the profile before you experiment with advanced slots.
Step 5: Test the layout outside and inside a game
Test in two stages. First, with AntiMicroX focused and then with a simple text field or desktop application focused, press each mapped button and confirm the expected key arrives. This catches swapped buttons, missing assignments and keys that only work when a particular window has focus. Second, start the game with AntiMicroX already running, and check the same actions in a safe place such as a menu, a training area or an early save you can reload. If the game also supports controllers natively, disable or unbind the game’s own mapping for the actions AntiMicroX is sending, otherwise one press can trigger two different inputs at once. That double-input problem is the most common beginner confusion, and it is a configuration clash, not a fault in either program.
Step 6: Save, reload and build good habits
Save the profile with a name that says which game and controller it belongs to, and keep the .amgp file somewhere you back up, such as a documents folder you sync. Loading a saved profile later takes seconds, and a named collection of profiles is the real long-term value of the program: each game gets the layout you tuned for it. From here, three features are worth learning in order. Sets let one profile hold eight different layouts and switch between them. Auto Profiles can load the right profile automatically when a particular application becomes active, although Auto Profiles do not work on Wayland. Advanced slots add pauses, holds, cycles and timing controls for more complex behaviour. For the safety questions new users usually ask next, including what the unsigned Windows build means in practice, read is AntiMicroX safe? before you go looking for profiles or builds on random sites.
