Here is a question more PC players should ask before installing anything: do you even need a separate controller mapper? If almost everything you play lives in your Steam library, Valve has already built one into the Steam client, for free. Steam Input is a capable mapper in its own right. InputMapper, by contrast, is a standalone, system-level tool from 2020 that works everywhere, including all the places Steam does not reach. This comparison is about drawing that boundary honestly, because choosing wrong in either direction wastes your time: installing legacy software you never needed, or fighting Steam’s limits in games it was never meant to cover.
Two Different Kinds of Mapper
Steam Input is part of the Steam client. You configure your controller per game, inside Steam, and those settings apply when that game is launched through Steam. It works with most controllers, including the DualShock 4 and the DualSense, and because it ships with a client most PC gamers already have installed, the setup cost is often zero. For many games, Steam handles a PlayStation controller with no extra software at all.
InputMapper is the opposite shape. It is a standalone application from DSDCS, closed-source freeware, whose final build 1.7.7452.13622 dates to May 2020. Once running, it presents your controller to the whole of Windows as a virtual Xbox 360 controller or virtual DS4, through the ViGEmBus driver, or as keyboard and mouse input. It does not care how a game was launched, which store sold it, or whether Steam is even installed. Its official inputs are the DS4 and DS4 V2, Xbox 360 and Xbox One controllers, the DualShock 3 and PS Move Navigation controller via a Magic-NS dongle, and generic DirectInput and XInput devices, but not the DualSense or the Switch Pro Controller, which its final build predates.
That architectural difference, per-game inside one client versus global at driver level, explains every practical difference that follows. See how to use InputMapper for the standalone setup and for the wider landscape.
At a Glance
| Feature | InputMapper | Steam Input |
|---|---|---|
| Price | Free, closed-source freeware, donations accepted, no paid edition | Free, built into the Steam client |
| Where it works | System-wide, for any game or application, however it was launched | Games launched through Steam, plus non-Steam shortcuts added to Steam, with caveats |
| Configuration style | Standalone profiles and macros that apply globally or per profile | Per-game configuration inside Steam |
| DualShock 4 | Yes, including DS4 V2 | Yes |
| DualSense | No, final build predates it | Yes |
| Virtual output | Virtual Xbox 360 and virtual DS4 via ViGEmBus, plus keyboard and mouse | Remapping inside Steam; no standalone global driver-level mapping outside Steam |
| Extras | Touchpad as mouse, lightbar and rumble controls, macros | Per-game layouts managed through Steam |
| Status | Unmaintained since May 2020 | Part of the actively maintained Steam client |
When Steam Input Alone Is Enough
Steam Input is enough, genuinely, not as a consolation prize, for a large share of players. If your games are bought on Steam and launched from Steam, if you mainly want a PlayStation controller to behave sensibly in those games, and if per-game layouts appeal to you more than a global profile system, you may never need InputMapper or anything like it.
The DualSense makes the case even stronger. Steam Input supports it; InputMapper does not and cannot, because its development ended before the controller existed. A DualSense owner whose library is on Steam should start and probably finish with Steam Input. Our DualSense on PC guide walks through that route. The same logic applies to anyone who dislikes installing drivers: Steam Input asks for nothing beyond the client you already run, whereas InputMapper needs ViGEmBus and, to avoid double input, the HidHide hiding tool, a stack that works well but is undeniably more moving parts.
There is also a maintenance argument. Steam is updated constantly by Valve. InputMapper has not been updated since 2020. For games inside Steam’s world, choosing the maintained, built-in option is simply the lower-risk default, and we recommend it as the first thing to try.
When InputMapper Wins
InputMapper’s territory begins where Steam’s ends. The moment a game is launched outside Steam, from another store, a standalone installer, or an emulator, Steam Input is not there, unless you add that program to Steam as a non-Steam shortcut, which works for many titles but comes with caveats: overlays, launch quirks, and per-game inconsistency. Emulator users feel this most. Emulators are classic non-Steam software, often launched directly, configured once, and expected to see a standard XInput controller every time. A global, driver-level virtual Xbox 360 controller from InputMapper fits that expectation exactly, with the same profiles and macros available on the desktop and in every application, not just inside one client’s library.
InputMapper also wins when you want one consistent mapping everywhere: the same profile behaviour in a launcher, a store client, an emulator front-end, and a game. Its profiles, macros, touchpad-as-mouse, and lightbar and rumble controls apply at the Windows level. Steam Input’s per-game model is a strength inside Steam and a limitation outside it, because there is no standalone global driver-level mapping from Steam Input for the rest of your PC.
You can get InputMapper from our download page, with its final, unmaintained status stated up front, because for this use case, archived but global can still beat current but confined.
The Conflict Between Them
The trouble starts when both tools try to map the same controller at the same time. If Steam Input is remapping your DualShock 4 while InputMapper is also presenting it as a virtual Xbox controller, a game can receive input from two paths at once, the classic double-input problem, or follow the wrong device entirely. Menus scroll twice, buttons act doubled, and camera control becomes a mess.
This is a known, fixable clash rather than a reason to abandon either tool. Our troubleshooting section covers the InputMapper and Steam Input conflict in detail, including the dedicated guide at inputmapper-steam-input-conflict, and the general fix in our double input fix. The principle is simple: for any given game, exactly one tool should be in charge of that controller. Let Steam Input own your Steam games, let InputMapper own everything else, and make sure the physical controller is hidden from games that should only see the virtual one, using HidHide as the modern hiding tool alongside InputMapper instead of its legacy HidGuardian-era approach.
Used that way, the two coexist well. Many DualShock 4 owners run exactly this split: Steam Input for the Steam library, InputMapper for emulators and other stores, and no conflicts, because the boundary is deliberate rather than accidental.
Verdict
If you live in Steam, use Steam Input: it is free, maintained, supports the DualSense, and probably already handles your controller. If you regularly play outside Steam, use emulators, or want a single mapping that applies across your whole PC, InputMapper still earns its place, with the honest caveat that it has been frozen since 2020 and never learned the DualSense. And if you use both, assign each game one owner. Most problems in this comparison are not really about which tool is better; they are about two good tools both trying to drive at once.
Frequently Asked Questions
Does Steam Input work with games outside Steam?
Only indirectly. Steam Input covers games launched through Steam, and you can add non-Steam games as shortcuts with some caveats, but it provides no standalone global driver-level mapping outside Steam.
Can I use InputMapper and Steam Input at the same time?
Yes, if each game has only one tool in charge of the controller. Letting both map the same controller in the same game causes double input and conflicts.
Which is better for a DualSense, InputMapper or Steam Input?
Steam Input. InputMapper does not support the DualSense because its final build was released in May 2020, before the DualSense existed, while Steam Input supports it.
Which tool should emulator users choose?
InputMapper is usually the better fit for emulators because it provides a system-wide virtual Xbox 360 controller that works however the emulator is launched.