What Each Tool Does

InputMapper, from DSDCS, is closed-source freeware whose final build, 1.7.7452.13622, arrived in May 2020 and is unmaintained since. Its official input list covers 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. Around those inputs it layers profiles, macros, touchpad-as-mouse control, and lightbar and rumble settings, and it can output a virtual Xbox 360 controller, a virtual DS4, or keyboard and mouse input.

XOutput is a free, open-source mapper focused on converting generic DirectInput controllers to XInput. That focus is its identity: if you have an older or generic pad that Windows games refuse to recognise because it does not speak XInput, XOutput’s job is to present it as an Xbox-style controller they will accept. It is simpler and narrower than InputMapper by design, with no DS4-specific lightbar, touchpad, and profile ecosystem built around Sony hardware.

Both tools stand on the same foundation: ViGEmBus, the virtual controller driver whose final release, 1.22.0 in November 2023, is now archived. That shared base is why both remain usable, and also why both belong to a particular period in PC gaming history rather than to its future. More on the generic-pad side in our guide to generic DirectInput controllers with InputMapper.

At a Glance

Which Pads Each Tool Suits

Start with the controller in your hand. If it is a DualShock 4, original or V2, InputMapper is the natural fit of these two. It understands the hardware’s extras rather than treating the pad as a bag of buttons: the touchpad can drive the mouse, the lightbar and rumble are controllable, and profiles and macros let one pad behave differently per game. Those details are the reason DS4 owners chose InputMapper in the first place, and XOutput simply does not attempt that layer. If you are deciding between the two versions of Sony’s pad itself, our comparison of the DualShock 4 V1 vs V2 covers what differs.

If your controller is a generic DirectInput pad, an older stick, wheel, or no-name gamepad that games ignore, the balance flips. XOutput was built for exactly that device, and its narrower scope becomes an advantage: you are not navigating a DS4-centred application to achieve a single conversion. InputMapper also accepts generic DirectInput devices, so it can do this job too, and if you already have it installed for a DualShock 4 it may be the path of least resistance for an occasional second pad. But as a dedicated tool for generic hardware, XOutput is the more purposeful choice.

For other InputMapper-listed hardware, such as a DualShock 3 via a Magic-NS dongle or an Xbox controller you want remapped rather than merely recognised, InputMapper’s broader input list and profile system make it the relevant tool of the pair. And for modern controllers neither tool was built around, notably the DualSense, look elsewhere entirely, to DS4Windows or Steam Input; our alternatives overview maps those options, and you can still get InputMapper itself from the download page.

Profiles and Depth Versus Simplicity

The deeper difference is philosophy. InputMapper wants to be your controller’s home: a place where profiles live, macros are recorded, and device-specific behaviour is tuned. That pays off if you play several games with different layouts, use the touchpad as a mouse on the desktop, or care about lightbar and rumble behaviour. It costs learning time, and its interface reflects the era it was built in.

XOutput wants to be a converter. Its narrower job means less to learn and less to maintain in your head: connect a DirectInput device, map it, present it as XInput, play. For a single generic pad and a library of games that only speak XInput, that restraint is a feature, not a limitation. Problems begin only when users expect XOutput to behave like a full DS4 suite, or expect InputMapper’s depth to feel simple. Neither expectation is fair to either tool.

Both share the same practical caveats. Each relies on ViGEmBus to create its virtual controller, so installation involves that driver either way. And where a game might see both the real controller and the virtual one, the double-input problem can appear with either tool; the modern solution is HidHide, the current hiding tool, rather than the legacy HidGuardian stack associated with InputMapper’s original era. Our troubleshooting pages cover those shared issues.

An Honesty Note About Both Tools

Neither of these is a living, actively evolving product in the way Steam Input or a commercial mapper is. InputMapper is explicitly finished: final build in May 2020, no successor, no paid edition waiting in the wings. XOutput likewise belongs to the unmaintained-era generation of ViGEmBus-based tools, kept useful by the stability of the underlying driver and the fact that DirectInput and XInput themselves change slowly. That stability is real, older controllers do not stop working because software ages, but expectations should be set accordingly: if a future Windows change breaks something, fixes may not come from the original projects. Judge both as well-preserved tools for hardware of their era, not as platforms with a roadmap.

A Note on Modern Generic Pads

If you are shopping for a new generic pad rather than rescuing an old one, the simplest option is a modern controller with native XInput support, which needs no converter at all. The 8BitDo Ultimate controller is one example we link to for readers taking that route. Affiliate link — see our Affiliate Disclosure. Keep your DirectInput veterans for the games they suit, by all means, but do not buy new hardware that needs translation on day one.

Verdict

Choose InputMapper for a DualShock 4 and for its profiles, macros, touchpad, lightbar, and rumble controls, or when its broader legacy input list matters. Choose XOutput for a generic DirectInput controller that simply needs to appear as XInput, with the least machinery around that conversion. Both are free, both use ViGEmBus, and both deserve to be described as what they are: capable tools from a finished era, still solving real problems for the controllers they were built for.

Frequently Asked Questions

Is XOutput better than InputMapper for a DualShock 4?

No. InputMapper is the better fit for a DualShock 4 because it offers DS4-specific features such as touchpad-as-mouse, lightbar and rumble controls, profiles and macros that XOutput does not provide.

What is XOutput mainly used for?

XOutput is mainly used to convert generic DirectInput controllers into XInput devices, so that games expecting an Xbox-style controller will recognise them.

Do InputMapper and XOutput use the same driver?

Yes. Both tools create their virtual controllers through ViGEmBus, whose final release was version 1.22.0 in November 2023 and which is now archived.

Are InputMapper and XOutput still maintained?

InputMapper is unmaintained since its final build in May 2020, and XOutput is likewise a tool of that same unmaintained era, although both can still work because the underlying standards change slowly.

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

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.

A disclosure before we start, because it shapes how you should read this page: this site has no affiliate relationship with reWASD. We earn nothing if you buy it, and nothing if you do not. Where we mention it, we link its official homepage once, plainly, so you can check its current pricing and feature list for yourself rather than trusting our summary.

What Each Tool Is Trying to Be

InputMapper, from DSDCS, is closed-source freeware. It was built around a specific problem of its era: making Sony controllers, above all the DualShock 4, work in Windows games that expect an Xbox 360 controller. Its official input list covers 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. It outputs a virtual Xbox 360 controller or a virtual DS4 through the ViGEmBus driver, as well as keyboard and mouse input, and it wraps that in profiles and macros with touchpad-as-mouse, lightbar, and rumble controls.

reWASD aims wider. It is a paid, actively developed, all-round remapper rather than a DS4 specialist: broader device support than InputMapper, and advanced remapping features such as layered and shift mappings, where one button can change what every other button does. That breadth is the product. If you own several different controllers, or you build complex multi-layer layouts for specific games, reWASD is designed for you in a way InputMapper never tried to be.

For background on the free side of this comparison, see how to use InputMapper and our alternatives overview.

At a Glance

Where reWASD Is Genuinely Better

Honesty first: on most axes a buyer cares about in 2026, reWASD is ahead, because it is a living product and InputMapper is an archived one.

Current development matters. When Windows changes something, when a new controller appears, or when a bug shows up, an actively developed tool can respond. InputMapper cannot — its final build is from May 2020, and that will never change. The DualSense is the clearest example: InputMapper does not support it at all, simply because the controller did not exist when development stopped. If you have moved to a DualSense, or you mix Sony, Xbox, and Nintendo controllers on one PC, InputMapper’s device list will feel like a museum exhibit. Our guides to the DualSense on PC and the Switch Pro Controller on PC exist precisely because readers keep asking about hardware InputMapper cannot read.

Remapping depth is the second real advantage. InputMapper’s profiles and macros cover straightforward remapping well, but reWASD’s layered and shift mappings open up layouts that InputMapper was never designed for — effectively several control schemes stacked on one pad, switched by holding a shift button. For simulation games, MMOs, and accessibility-driven layouts, that difference is not cosmetic.

Support is the third. A paid product comes with a vendor who has a commercial reason to answer you. InputMapper comes with community knowledge and sites like this one. For many people that is enough; for some, it is not, and that is a legitimate reason to pay.

Where InputMapper Still Wins

InputMapper’s case rests on three things: price, focus, and simplicity of ownership.

It is free — genuinely free, not a trial or a feature-limited tier. InputMapper was released as freeware supported by donations, and there has never been a paid edition. If your whole requirement is “make my DualShock 4 work in Windows games, with a couple of profiles,” paying for a commercial mapper buys you breadth you may never use.

It is also focused. Everything in InputMapper serves the DS4-to-XInput job: profiles, macros, the touchpad as a mouse, lightbar and rumble settings. There is no store, no account, and no licensing step between downloading it from our download page and using it. For a single-purpose tool on a gaming PC that rarely changes, that lack of ceremony has real appeal, and the software you learn today is the software you will still have in five years — because it will not change at all.

Finally, its underlying approach is well understood. InputMapper 1.7 works through ViGEmBus, the same virtual controller driver used by DS4Windows and XOutput, and the modern way to prevent double input alongside it is HidHide rather than the legacy HidGuardian stack from its own era. The ecosystem knowledge is stable and documented, including on this site’s troubleshooting pages.

Who Should Pay, and Who Should Not

Pay for reWASD if any of these describe you: you own a DualSense or several different modern controllers; you want layered or shift mappings; you play new games on a PC you keep updating, and you want a mapper that is updated with it; or you simply want a supported product. Those are good reasons, and we will not pretend a frozen 2020 freeware tool matches them.

Stay with InputMapper if you have a DualShock 4, a stable set of games, and modest remapping needs. In that narrow but common case, it still does its original job for free, and the money stays in your pocket.

You can check reWASD’s current pricing, trial terms, and device list at rewasd.com — again, we have no affiliate relationship with reWASD and earn nothing from that link. We would rather you verified a paid product’s claims on the vendor’s own site than took our word for them.

The Budget Alternative: Free Software Plus a Native Pad

There is a third way to spend — or not spend — this money. Instead of paying for mapping software to translate a PlayStation controller, you can pair free software for the pad you have with a native XInput controller that Windows games understand with no translation at all. A native pad removes the driver, hiding, and compatibility questions entirely. Two options we link commercially are the PowerA controller range on Amazon and PowerA controllers direct. Affiliate link — see our Affiliate Disclosure. Note the contrast we are drawing deliberately: those are affiliate links and we say so; the reWASD link above is not, and we say that too.

Frequently Asked Questions

Is InputMapper really free, or is there a paid edition?

InputMapper is completely free. It is closed-source freeware supported by donations, and there has never been a paid edition or premium tier.

Does this site earn money if I buy reWASD?

No. We have no affiliate relationship with reWASD and earn nothing from links to its site or from any purchase you make there.

Why would anyone pay for reWASD when InputMapper is free?

reWASD is actively developed, supports a broader range of modern devices including the DualSense, and offers advanced features such as layered and shift mappings that InputMapper does not have.

Can InputMapper and reWASD be used together?

Running two mappers that both create virtual controllers can cause conflicts and double input. Pick one mapper per controller and use it consistently.

Shared Roots: Two Branches of the Same Idea

Both tools trace back to the 2014 DS4Tool and early DS4Windows work, when the DualShock 4 was new and Windows had no useful native support for it. From that common root, development split. One branch became InputMapper, developed by DSDCS as closed-source freeware. The other stayed open source under the DS4Windows name, most famously in the Ryochan7 line.

That split explains both the similarities and the differences. The core job — translating DualShock 4 input into XInput, the Xbox controller standard Windows games understand — is the same. So are many of the concepts layered on top of it: per-game profiles, macros, using the touchpad as a mouse, and controlling the lightbar and rumble. Where the tools diverge is openness, device support, and, above all, what has happened since 2020.

If you are new to either tool, start with how to use InputMapper for the InputMapper side, and our DS4Windows install guide for the other. The rest of this page assumes you want help choosing, not a full setup walkthrough.

At a Glance

Device Support: DualSense Decides It for Many People

The single biggest practical difference is simple. InputMapper does not support the DualSense, Sony’s PlayStation 5 controller, and it never will in its final build — version 1.7 was released in May 2020, months before the DualSense existed. DS4Windows does support the DualSense, and that support is its headline advantage.

So if you own a DualSense, this comparison is already over: use DS4Windows, or use Steam Input, which also handles the DualSense well. Our guide to using a DualSense on PC covers both routes. Do not spend an afternoon trying to make InputMapper recognise a controller it was never built to read.

If you own a DualShock 4 — original or V2 — both tools read it properly, and the choice becomes about maintenance, workflow, and how much else you want to connect. InputMapper is actually the broader of the two on older hardware: alongside the DS4 it lists the 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. That breadth mattered in mixed-controller households, and for a retro desk with older pads it still can.

Drivers and Hiding: The Same Foundation

Underneath, both tools rely on the same virtual controller driver, ViGEmBus. It creates the virtual Xbox 360 or virtual DS4 device that games see. ViGEmBus itself reached its final release, 1.22.0, in November 2023 and its repository is now archived, but the driver remains the shared foundation for InputMapper 1.7, DS4Windows, and several other mappers.

Both tools also have to solve the double-input problem: if Windows sees your real DualShock 4 and the virtual Xbox pad at the same time, some games read both and your character gets two inputs for one press. The fix is to hide the physical controller from games while leaving it visible to the mapper. InputMapper’s era used Exclusive Mode and the legacy HidGuardian stack. The modern tool for this job is HidHide, now at v1.5.230, which DS4Windows uses and which also works as the modern companion alongside InputMapper. If you are setting either tool up today, read our HidHide guide rather than following old HidGuardian tutorials — that stack belongs to an earlier period and causes more confusion than it solves on current Windows installs.

Profiles, Macros, and Everyday Use

For day-to-day DualShock 4 gaming, the two tools are closer than their reputations suggest. Both let you save profiles, remap buttons, record macros, use the DS4 touchpad as a mouse, and adjust lightbar and rumble behaviour. If your mental model is “one profile for racing games, one for shooters, touchpad for menus,” either tool can do that with a DualShock 4.

The differences are in feel rather than feature checklists. InputMapper presents a single, focused application built around its profile system, and long-time users often describe it as the simpler of the two to understand once it is installed — everything lives in one place, and nothing has changed in years, for better and worse. DS4Windows exposes more device-specific detail for Sony controllers, especially around the DualSense, and its settings reflect hardware that InputMapper simply does not know about. Neither interface is modern, and neither will win a design award in 2026. Both are utilities from another era of Windows software, and both ask a little patience during first setup.

Maintenance Status in 2026: The Honest Part

InputMapper is finished software. The final build, 1.7.7452.13622 from May 2020, is unmaintained, and there is no paid edition, upgrade path, or announced successor — it was always freeware supported by donations. That does not make it broken: for a DualShock 4 on a stable Windows setup, archived software can keep working for years. It does mean that new controllers, new Windows changes, and new bugs will not be addressed.

DS4Windows has a more complicated story. The well-known Ryochan7 line ended at version 3.3.3 in December 2023, and that repository now returns a 404 — a fact that confuses many people searching for a download today. Development did not entirely stop, however: a maintained continuation, ds4windowsapp, reached v3.5 in February 2026. So DS4Windows, unlike InputMapper, still has a living branch, even if finding the right one takes more care than it used to. You can get InputMapper itself from our download page, with its final-build status stated plainly.

Verdict: Which Should You Use?

Our overall take: DS4Windows wins this comparison for most new readers in 2026, because of DualSense support and its continuing branch. InputMapper remains a legitimate, free choice for DualShock 4 owners who value its profile workflow or its legacy device list — which is exactly why this site documents it in detail, without pretending it is still in development.

The Third Option: A Native XInput Controller

There is a way to skip mapping software altogether: use a controller that Windows games already understand natively as XInput. A native Xbox-style pad needs no virtual driver, no hiding tool, and no profile translation layer, so there is nothing to break when Windows updates. If you are tired of maintaining a mapping setup, consider a PowerA controller or the 8BitDo Ultimate controller as that third option, and keep your DualShock 4 for the PlayStation. Affiliate link — see our Affiliate Disclosure.

Frequently Asked Questions

Does InputMapper support the DualSense controller?

No. InputMapper’s final build was released in May 2020, before the DualSense launched, so the DualSense is not supported. Use DS4Windows or Steam Input for a DualSense on PC.

Is DS4Windows still maintained in 2026?

The Ryochan7 line ended at version 3.3.3 in December 2023 and its repository is gone, but a maintained continuation called ds4windowsapp reached version 3.5 in February 2026.

Are InputMapper and DS4Windows both free?

Yes. InputMapper is closed-source freeware supported by donations with no paid edition, and DS4Windows is free and open source.

Why do I get double input with both tools?

Double input happens when a game sees both your real controller and the virtual Xbox 360 controller at the same time. Hiding the physical controller with HidHide is the modern fix for both tools.

Best Free Mapper for a DualShock 4: InputMapper or DS4Windows

For the classic job, making a DualShock 4 work across Windows games that expect an Xbox controller, you have two free tools with shared 2014 roots in DS4Tool and the early DS4Windows project.

InputMapper, from DSDCS, is closed-source freeware, always free with donations accepted and no paid edition. Its final build, 1.7.7452.13622 from May 2020, is unmaintained, but it offers a focused package: DS4 and DS4 V2 support, a broader legacy input list including Xbox 360, Xbox One, DualShock 3 via a Magic-NS dongle and generic devices, virtual Xbox 360 and virtual DS4 output through ViGEmBus, and profiles, macros, touchpad-as-mouse, and lightbar and rumble controls.

DS4Windows is the open-source branch of the same family. Its famous Ryochan7 line ended at 3.3.3 in December 2023 and that repository is gone, but the ds4windowsapp continuation reached v3.5 in February 2026, so it is the living option of the two, and it uses ViGEmBus with HidHide for hiding the physical controller. For a pure DualShock 4 setup, either works; DS4Windows is the safer long-term default, InputMapper a reasonable and arguably simpler archive path for owners who like its profile workflow. Our full head-to-head, InputMapper vs DS4Windows, works through the trade-offs, and our DS4Windows install guide covers setup.

Best for DualSense: DS4Windows or Steam Input

The DualSense redraws the map, because InputMapper does not support it at all: its development ended months before Sony’s PlayStation 5 controller existed. If you own a DualSense, your realistic free choices are DS4Windows, which supports both the DualShock 4 and the DualSense and makes that support its headline advantage, and Steam Input, Valve’s free mapper inside the Steam client, which also handles the DualSense well.

Choose DS4Windows if you want a standalone, system-wide tool that works however your games are launched. Choose Steam Input if your library lives in Steam and you prefer per-game configuration with nothing extra to install. Our DualSense on PC guide compares both routes in practice.

Best Paid All-Rounder: reWASD

If you want one actively developed mapper with broad device support and advanced remapping, including layered and shift mappings, the commercial option in this roundup is reWASD. It is a paid product, and what the money buys is exactly what the free legacy tools cannot offer: ongoing development, current device support, and depth for complex layouts across several different controllers.

We want to be plain about our position here: this site has no affiliate relationship with reWASD and earns nothing from it. We link its official homepage plainly at rewasd.com so you can check its current pricing and device list yourself. Our detailed, deliberately even-handed comparison is InputMapper vs reWASD. If your needs are just a DualShock 4 and a couple of profiles, you do not need to pay for anything; if you run multiple modern controllers and layered layouts, reWASD is the pick in this category.

Best Built-In Option: Steam Input

The best mapper is sometimes the one you already have. Steam Input is free, built into the Steam client, configured per game, and works with most controllers including the DualShock 4 and DualSense. For a Steam-centred library it is the lowest-friction choice in this entire roundup, and it is maintained as part of an actively developed client.

Its boundary is equally clear: it covers games launched through Steam, plus non-Steam shortcuts added to Steam with caveats, and it offers no standalone global driver-level mapping for the rest of your PC. Emulators and other stores launched directly are outside its natural territory. Our comparison InputMapper vs Steam Input explains when that boundary matters and how to run both tools together, one owner per game, without double input. For many readers, “try Steam Input first” is the single most useful sentence on this page.

Best for Generic DirectInput Pads: XOutput

Not every controller is a Sony or Xbox pad. For older and generic DirectInput controllers, gamepads, sticks and wheels that modern games ignore because they do not speak XInput, the focused free answer is XOutput, an open-source mapper that converts generic DirectInput devices to XInput through ViGEmBus. It is deliberately simpler and narrower than InputMapper, with no DS4-specific lightbar, touchpad, and profile ecosystem, and for a single conversion job that narrowness is a virtue.

InputMapper also accepts generic DirectInput devices and can serve here if you already use it, which our guide to generic DirectInput controllers with InputMapper explains. But as a dedicated converter, XOutput is the category pick. Our head-to-head, InputMapper vs XOutput, helps you decide which of the two matches your pad.

Best for Mapping a Controller to Keyboard and Mouse: AntiMicroX

Some mapping jobs are not about making one controller look like another. If your goal is to drive keyboard and mouse input from a gamepad, for a game with no controller support at all, or for desktop control, the relevant category is keyboard-mapping tools, and the free open-source name to know here is AntiMicroX, a mapper focused on exactly that keyboard and mouse mapping work. InputMapper also offers keyboard and mouse output alongside its virtual controllers, so existing users may not need a second tool, but readers whose primary job is pad-to-keyboard mapping should start with a tool built around that job.

Summary: Picks by Use Case

A shared foundation is worth knowing before you choose: InputMapper 1.7, DS4Windows, and XOutput all create virtual controllers through ViGEmBus, whose final 1.22.0 release from November 2023 is archived, and the modern companion for hiding the physical controller is HidHide, now at v1.5.230. Whichever free tool you pick from that family, expect that driver, and expect the double-input questions that come with it, covered in our troubleshooting section. You can download InputMapper from our download page, and browse the full field in our alternatives overview.

When the Best Mapper Is No Mapper

Every tool above exists to translate. A native XInput controller needs no translation: no virtual driver, no hiding tool, no per-tool conflicts, and nothing to maintain when Windows changes. If you are buying hardware anyway, or you are simply tired of mapper upkeep, a native pad can be the best decision in this entire roundup. Options we link commercially include a PowerA controller, Logitech G gear for the wider desk setup, and the 8BitDo Ultimate controller. Affiliate link — see our Affiliate Disclosure. Keep your DualShock 4 for the games and tools above; just know that opting out of mapping entirely is a legitimate verdict too.

Frequently Asked Questions

What is the best free controller mapper for PC?

It depends on your controller. DS4Windows and InputMapper are the leading free options for a DualShock 4, Steam Input is the best free built-in option for Steam games, and XOutput is the free pick for generic DirectInput pads.

Which controller mapper works with the DualSense?

DS4Windows and Steam Input both work with the DualSense. InputMapper does not support the DualSense because its final build was released in May 2020, before that controller existed.

Is a paid mapper like reWASD worth it?

reWASD is worth considering if you want actively developed software, broad modern device support, and advanced features such as layered and shift mappings. For a single DualShock 4 with simple profiles, free tools are usually enough.

Do I need a mapper at all with a native XInput controller?

No. A native XInput controller is understood by Windows games directly, so it needs no mapping software, virtual driver, or hiding tool.