vJoy vs reWASD: Free Driver Stack or Paid Remapper?
vJoy and reWASD are often listed side by side as if they were two versions of the same thing. They are not. vJoy is a free virtual joystick driver. reWASD is a paid remapping application that creates its own virtual gamepads. They overlap in one narrow place — both can put a virtual controller in front of a game — and diverge everywhere else. Picking between them starts with naming the job correctly.
What vJoy actually is
vJoy (the Shaul Eizikovich lineage this site documents) is a Windows kernel driver that creates generic DirectInput virtual joysticks: up to 16 devices, each with up to 8 axes, up to 128 buttons, and up to 4 POV hats. It has no remapping interface of its own beyond configuration in vJoyConf. A separate feeder application — Joystick Gremlin, UCR, FreePIE, or your own code using the SDK — writes the data. That two-part design (driver plus feeder) is more work to learn, and far more flexible: merging two physical sticks into one 128-button virtual device is exactly the kind of job it exists for. vJoy is free, and its licence should be stated carefully: SourceForge lists it as Public Domain while GitHub mirrors carry an MIT tag, so this site describes it as free and source-available rather than with a single flat label.
What reWASD actually is
reWASD is a polished commercial remapper for gamepads and other controllers. Per its own help documentation, it creates its own virtual controllers — virtual Xbox 360, Xbox One, DualShock 4, DualShock 3, and Switch Pro controllers — without needing vJoy at all. You map sticks, buttons, keyboard and mouse inputs onto those gamepads inside one tidy application, and games see a familiar console-style controller. For couch gaming, controller macros, and making a gamepad behave differently per game, that convenience is the product, and it is legitimately good at it.
The cost is literal and structural. reWASD is paid software (with a trial), while the vJoy stack is free. And structurally, everything reWASD creates is a gamepad: an Xbox-style or PlayStation-style controller with that family’s stick, trigger, and button layout.
The gap that decides it: the generic DirectInput joystick
reWASD does not provide a generic 128-button DirectInput joystick. If your simulator setup needs one virtual device with dozens of buttons merged from two sticks and a throttle, custom response curves per axis, mode layers that change what every button does, or a feeder script driving axes from a serial device, reWASD’s virtual gamepads simply do not model that device. Flight and space sims — DCS, Microsoft Flight Simulator, Star Citizen HOSAS setups — are where this gap bites, and it is the main reason the vJoy ecosystem still exists alongside a slicker commercial tool.
| Question | vJoy stack | reWASD |
|---|---|---|
| What it creates | Generic DirectInput joysticks (up to 128 buttons, 8 axes, 16 devices) | Virtual Xbox / DualShock / Switch Pro gamepads |
| Remapping built in? | No — a feeder (Gremlin, UCR, FreePIE) does it | Yes — remapping is the product |
| Price | Free (driver + free feeders) | Paid (trial available) |
| Best at | Sim cockpits, device merging, curves, modes, scripted feeding | Gamepad remapping, per-game profiles, convenience |
| Learning curve | Steeper: driver + feeder to configure | Shallower: one application |
Who should pick which
- Pick the vJoy stack if you fly or race with sim hardware, need to merge physical devices, need more buttons than a gamepad has, or need a feeder-driven virtual joystick for a DirectInput game. Start on the download page and then choose a feeder via the Feeders & Tools hub.
- Pick reWASD if your goal is gamepad-shaped: remapping a controller for games that expect an Xbox or PlayStation pad, adding macros and layers to a pad, and paying for one polished app instead of assembling a free stack.
- Some people run both — reWASD for gamepad games, vJoy plus Gremlin for the sim rig. They do not conflict by design, because they create different kinds of devices for different games.
A note on honesty, since comparison pages often hide it: this site earns nothing from reWASD. Its partner programme pays no cash commission, and there is no reWASD affiliate link anywhere in this article — the verdict above is based only on what each tool actually does. Where a tool genuinely fits a job better, we say so, paid or not.
Profiles, polish, and the honest trade-off
There is one more difference worth naming, because it decides the purchase for many readers: how the two stacks feel day to day. reWASD’s strength is presentation. Profiles are visual, switching behaviour per game is a first-class feature, and a new user can remap a pad in minutes without learning what a feeder is. The vJoy stack asks more of you up front — install a driver, configure devices in vJoyConf, then learn a feeder — and pays you back in ceiling rather than convenience: once Gremlin modes and curves exist for your cockpit, no gamepad-shaped tool replicates them.
Cost works the same way. The vJoy stack’s price is your time; reWASD’s price is money plus accepting its device model. Neither is a trick. If your evenings are scarce and your problem is gamepad-shaped, paying is rational. If your problem is a 100-button merged sim device, no payment makes reWASD model it — the free stack is not the budget option there, it is the only option. Judge the two on the device you actually need, not on which landing page looks newer.
Verdict
Different tools, different devices. Need a generic DirectInput virtual joystick with sim-grade merging and buttons to spare? That is vJoy plus a feeder, and reWASD cannot substitute for it. Need a virtual Xbox or DualShock pad with convenient remapping? That is reWASD’s home ground, and vJoy — which does not emulate XInput at all — cannot substitute for it either. For the gamepad-emulation side of the fence, see vJoy vs ViGEmBus vs XOutput, and browse the Alternatives & Comparisons hub for the rest of the comparisons. Still deciding on a build? Which vJoy Build Should You Download? settles which vJoy to install.