Here is the part of InputMapper’s story that rarely gets told: it was never only a PlayStation tool. Read the official input list and you will find the Xbox 360 Controller and the Xbox One Controller listed as supported input devices, right alongside the DualShock 4 and DualShock 4 V2. In other words, InputMapper can take your Xbox pad as the thing you hold, and then decide what your PC pretends you are holding instead.
That raises an obvious question. Xbox controllers already speak XInput, and XInput is what most PC games expect — so why route one through InputMapper at all? For plain gaming in a modern title, you usually should not, and this page will say so plainly. But there are four real jobs InputMapper does for an Xbox pad that Windows alone does not: keyboard and mouse output, macros, per-game profiles, and testing. If any of those is your problem, the under-told Xbox side of InputMapper is exactly the tool you have been missing.
New to the software? Grab it from the download page and skim how to use InputMapper first — everything below assumes a working install with ViGEmBus in place.
How Xbox Pads Fit Into InputMapper
InputMapper separates the idea of an input from the idea of an output. Inputs are the physical devices you hold. Outputs are what the software presents to Windows and your games: a virtual Xbox 360 controller (via ViGEmBus), a virtual DS4 (via ViGEmBus), or keyboard and mouse emulation. The official list puts the Xbox 360 Controller and Xbox One Controller on the input side of that equation, and nothing stops an input from being re-expressed as a different output.
So an Xbox pad in InputMapper is not a hack or a side effect of generic device handling — though Generic XInput Devices are also on the official list, which covers many third-party pads in the same family. Your Xbox controller is a named, supported input, and once it appears in InputMapper you can build profiles for it just as you would for a DualShock 4, following the same workflow described in our InputMapper profiles guide.
Reason One: Keyboard and Mouse Output
The most useful reason to map an Xbox pad is to reach software that has no controller support at all. Point-and-click games, older titles, emulators with awkward input pages, media and productivity apps — plenty of PC software only listens to the keyboard and mouse. InputMapper can translate your pad into those signals: face buttons become keys, a stick can drive the mouse pointer, triggers can become clicks. Suddenly the Xbox controller on your desk is a couch-friendly remote for software that was never designed for one.
This works in the other direction for accessibility too. If a game’s native pad support exists but cannot be rebound, mapping the pad to the keys the game does accept can restore control over your own layout. It is not glamorous, but for the person who needs it, it is the difference between playing and not playing.
Reason Two: Macros and Reason Three: Per-Game Profiles
Windows treats your Xbox pad as a fixed device: a button is a button. InputMapper treats it as a starting point. A profile can move actions to where your thumbs prefer them, combine inputs, or bind a sequence to a single press through a macro — handy for repetitive menus, training-mode drills, or turning a multi-key command in a strategy game into one pad press.
Profiles make this sustainable. Instead of one global compromise, you keep a profile per game: one layout for the racing title, another for the keyboard-heavy simulator, another for desktop mouse control. InputMapper’s whole design — the same design DualShock owners use, compared in our InputMapper vs DS4Windows breakdown — is built around switching those mappings as the context changes. Xbox owners simply get to use that machinery too, and most never knew it was there for them.
Reason Four: Testing and the Virtual DS4 Output
Here is the trick developers, streamers, and curious players appreciate most: because InputMapper can output a virtual DS4 (via ViGEmBus), an Xbox pad can be presented to a game as a DualShock 4. Why would you? To test how a game behaves with PlayStation prompts without owning the hardware. To check whether a title’s DS4 support works before recommending it. To follow a guide written for PlayStation button labels while holding the pad you actually have.
The same flexibility helps when troubleshooting. If a game misbehaves with your physical pad, re-presenting it through a clean virtual device is a fast way to learn whether the fault lives in the game, the driver layer, or the hardware. And if the virtual device ever appears alongside the physical one and inputs double up, that is the classic problem covered by our double input fix — with HidHide v1.5.230 as the modern way to hide the physical pad, detailed in the HidHide guide.
The Honest Limits
Now the boundaries, because they matter. Mapping an Xbox pad through InputMapper does not add PlayStation features to it. There is no touchpad hiding in your Xbox controller waiting to be unlocked, and the virtual DS4 output cannot conjure hardware your pad does not have. What changes is the signal your PC sees, not the device in your hands.
Second, a native XInput game that already reads your Xbox controller perfectly gains nothing from the extra layer. Every translation step is a place where configuration can go wrong, and if your only goal is “press A, game receives A,” plug in and play. InputMapper earns its place when you need something Windows does not offer — a keyboard binding, a macro, a profile, a different virtual identity — not as a ritual to perform before every session.
Third, remember what InputMapper is: a finished tool whose final build, 1.7.7452.13622, dates to May 2020. It does its listed jobs well, but plan your setup around the official list rather than hoping for support that was never announced.
Pad Options if You Are Shopping
Any genuine Xbox 360 or Xbox One controller works as an official input. If you are buying a pad primarily for PC and like the Xbox layout, a wired third-party option such as a PowerA controller is a sensible desk pad — it lives in the same XInput world and pairs naturally with the profile workflows above.
Shop PowerA Controllers on Amazon
Affiliate link — see our Affiliate Disclosure.
Frequently Asked Questions
Is an Xbox controller really an official InputMapper input?
Yes. The Xbox 360 Controller and the Xbox One Controller both appear in InputMapper’s official input list, alongside the DualShock 4, DualShock 4 V2, and generic XInput devices.
Why map an Xbox pad if games already support it natively?
For keyboard and mouse output to software with no controller support, for macros, for per-game profiles with custom layouts, and for testing — including presenting the pad to a game as a virtual DS4 via ViGEmBus. For a native XInput game that already works, you do not need it.
Does InputMapper add PlayStation features to an Xbox controller?
No. It changes the signal your PC sees, including a virtual DS4 output, but it cannot add hardware features such as a touchpad to a controller that does not have them.
What should I do if inputs register twice?
That is the double input problem: the game sees both the physical pad and the virtual device. Hide the physical controller — HidHide v1.5.230 is the modern tool for this — and follow a dedicated double input fix.