InputMapper is a closed-source freeware utility from DSDCS that takes a real controller connected to your PC and presents it to games as a different, virtual controller. Its history runs from DS4Tool in 2014, through DS4Windows, to InputMapper in 2015. The final build is 1.7.7452.13622, built in May 2020 and sized at 72.2 MB, with MD5 1b166e39787476748358cca460fe4225. That age matters: it still works for many players on Windows 10 and 11, but it is a discontinued tool, not a actively maintained one. This guide walks through the complete flow in the right order — requirements first, the virtual bus driver second, InputMapper itself third, then connecting a DualShock 4, building a profile, and testing it in a game.
What InputMapper Can and Cannot Do
According to the official input list, InputMapper accepts the DualShock 4, the DS4 V2, the Xbox 360 controller, the Xbox One controller, the DualShock 3 only via a Mayflash Magic-NS dongle, the PS Move Navigation controller via Magic-NS, and generic DirectInput and generic XInput devices. On the output side it can create a virtual Xbox 360 controller, a virtual DS4, or keyboard and mouse output — all through the ViGEmBus driver.
Two popular controllers are not on that list: the DualSense and the Nintendo Switch Pro Controller. The final build predates the DualSense launch in November 2020, so InputMapper never added support for it. If you own one of those controllers, read our guides to DualSense on PC and the Switch Pro Controller on PC instead of forcing them through InputMapper.
Requirements Before You Start
- A PC running Windows — InputMapper runs on Windows 10 and 11 in practice. Note that Windows 11 was never officially supported, because the final build predates it.
- .NET Framework 4.x installed. Windows normally includes a 4.x version, so do not hunt for a specific minor version.
- A supported controller, ideally a DualShock 4 or DS4 V2 for this guide.
- A micro-USB data cable for a wired first connection, or a Bluetooth adapter for wireless play.
- Administrator access, because driver installation requires it.
Download the installer only from a page you trust. Our download page links to the archived installer and to a clearly labeled mirror. Check the file size and hash above before you run anything, and never treat any mapper as automatically trustworthy — version 1.6.10 of InputMapper even has a recorded buffer-overflow vulnerability, CVE-2019-25464, which is one more reason to use the final build rather than an old copy found on a random forum.
Step 1: Install ViGEmBus First
InputMapper 1.7 does not create its virtual controllers by itself. It outputs through ViGEmBus, an independent open-source project by nefarius under the BSD-3 license. Installing ViGEmBus first avoids the most common first-run error, where InputMapper opens but cannot create a virtual device.
The final ViGEmBus release is 1.22.0, released on November 2, 2023, after which the repository was archived. Download it from its GitHub releases page, run the installer, accept the driver prompt, and restart the PC if Windows asks you to. Do not download ViGEmBus from vigem.org — that domain has changed hands and must not be used. Our ViGEmBus install guide covers each prompt in detail, and the virtual bus not found fix helps if you skipped this step.
Step 2: Install InputMapper
- Run the InputMapper installer for build 1.7.7452.13622.
- Accept the license terms and keep the default install location unless you have a reason to change it.
- Let the installer finish, then launch InputMapper from the Start menu.
- If Windows shows a SmartScreen prompt for an unrecognized app, verify the file name, size, and hash first. Only continue if they match what you expected to download.
On first launch, InputMapper looks plain: a device area at the top, a profiles area, and settings. Do not change advanced options yet. The goal of a first setup is a single working virtual Xbox 360 controller that a game can see. Extras such as macros and touchpad mapping come later, once the basic chain is proven.
Step 3: Connect Your DualShock 4
For a first connection, use a wire. Plug a micro-USB data cable into the DualShock 4 and into a USB port on the PC. Windows should detect the controller, and InputMapper should list it as a connected device shortly afterwards. A wired first test removes Bluetooth pairing, battery level, and wireless interference from the equation, so if something fails you know the problem is in the software chain, not the radio link.
Once wired mode works, you can pair over Bluetooth by holding Share and PS on the controller until the lightbar double-blinks, then adding “Wireless Controller” in Windows Bluetooth settings. Our dedicated guides to connecting a PS4 controller to PC and InputMapper Bluetooth pairing walk through both methods step by step.
Step 4: Create a Profile With Xbox 360 Output
- In InputMapper, create a new profile and give it a clear name, such as “Xbox 360 Default”.
- Set the output device to the virtual Xbox 360 controller. This is the output most PC games understand natively, because most were built around XInput.
- Leave the standard button mapping in place for now. Face buttons, triggers, sticks, and the D-pad should mirror the layout printed on an Xbox controller.
- Save the profile, then bind it to your connected DualShock 4 so the controller actually uses it.
Profiles are where InputMapper becomes useful beyond a simple adapter: each profile can hold different mappings, stick settings, and macros, and you can keep one profile per game. Our InputMapper profiles guide explains naming, binding, and per-game setups in depth, and it is worth reading before you build a large library.
Step 5: Test the Virtual Controller
With the profile active, open the Windows game controller panel by searching for “Set up USB game controllers” in the Start menu. You should see the virtual Xbox 360 controller listed. Open its properties and press buttons on the DualShock 4: the on-screen indicators should respond. If the real controller and the virtual controller both appear, that is expected — the real one is the input, the virtual one is what games should use.
Then launch a game with native Xbox controller support and test movement, camera, and menus. If inputs double up or the game sees two controllers at once, you are running into the classic double-input problem, which is about hiding the real controller, not about your mapping. Start with the double input fix rather than remapping buttons at random.
A Note on Exclusive Mode and Hiding the Real Controller
Older versions of InputMapper relied on exclusive mode and on HidGuardian plus HidCerberus to hide the physical DualShock 4 from games. That stack is legacy software from 2016 to 2018. The modern successor for hiding a controller is HidHide, currently at version 1.5.230 from May 11, 2024, for Windows 10 and 11 x64, available from GitHub releases. You do not need it for a first test — only add a hiding tool if a specific game actually shows double input. If InputMapper reports that it cannot take exclusive access, see exclusive mode failed for the order in which to close competing apps and services.
If you run into other problems, the troubleshooting hub and the Windows 11 notes collect the fixes that apply to this final, unmaintained build.
Connection Kit
A reliable wired cable and a decent Bluetooth adapter remove most first-setup headaches. A charge-only cable will never carry data, and a weak adapter drops connections mid-game, so these two small items are worth getting right.
Bluetooth Dongle on Amazon Micro-USB Data Cable on Amazon
Affiliate link — see our Affiliate Disclosure.
Frequently Asked Questions
Do I need to install ViGEmBus before InputMapper?
Yes, install ViGEmBus first. InputMapper 1.7 creates its virtual Xbox 360 and virtual DS4 outputs through ViGEmBus, so without that driver installed first, InputMapper can open but cannot create a working virtual controller.
Does InputMapper work with the DualSense controller?
No. The DualSense is not in InputMapper’s official input list, and the final build from May 2020 predates the DualSense launch in November 2020. Use a current tool for DualSense instead.
Why does my game see two controllers at once?
The game is seeing both your real DualShock 4 and the virtual Xbox 360 controller that InputMapper creates. That is the double-input problem, and it is fixed by hiding the real controller, for example with HidHide, not by changing your button mapping.
Is InputMapper officially supported on Windows 11?
No. InputMapper runs on Windows 10 and 11 in practice, but Windows 11 was never officially supported because the final build predates Windows 11. Expect occasional quirks and use the troubleshooting guides when they appear.