Is Inputize safe? The honest ban-risk picture.
The question behind every "can I get banned" search. Short version: Inputize runs on the same Microsoft-signed driver as DS4Windows and Parsec, injects nothing into games — and the per-game picture (including the one title with a policy gate) is in the table below, named rather than hidden.
The three reasons this category sits in a tolerated zone
Why virtual controllers are treated differently from cheats.
1 · Mainstream shared driver
Inputize creates its controller through ViGEmBus — a Microsoft-signed virtual gamepad driver used by DS4Windows (millions of users), Parsec (mainstream remote play) and many other everyday apps. Flagging that driver would break all of them at once. Publishers are not in the business of banning millions of ordinary users overnight.
2 · Nothing hidden, nothing injected
Cheat software reads game memory, injects code or patches files. Inputize does none of that: it works purely at the Windows input layer, converting keyboard & mouse into a standard virtual Xbox 360 controller. The game sees exactly what it sees when a person plugs in a real gamepad.
3 · The signal is shaped, not exploited
SAB rebuilds every gesture as natural, human-paced stick movement instead of instant synthetic edges. That is about how the input feels — we are explicit that it is not an anti-cheat bypass and promise no undetectability. Honest tools state their limits.
Per-game ban-risk table
Where Inputize is confirmed working, and where the risk is real.
| Game | Works with Inputize | Ban history for virtual-pad software |
|---|---|---|
| Apex Legends | ● Yes — verified by players | None known to date |
| Warzone / CoD | ● Yes — verified by players | None known to date |
| Overwatch 2 | ● Yes — verified by players | None known to date |
| Fortnite | ● Yes — tested by us | None known to date |
| Rainbow Six Siege | ● Pad works — no aim assist in the PC pool | None known to date; MouseTrap targets spoofing hardware on console |
| The Finals | ● Yes — tested by us | No ban reports known; Embark's 1.4.1 line gates aim assist for re-mapping clients |
| WARDOGS | ● Yes — tested by us | No ban reports known; emulator and aim assist work |
| CS2 / R6 Siege | ● Yes — pad works | No ban reports known; game has no aim assist to engage |
"Works" = the emulator runs and, where the game grants controller aim assist on PC, the assist engages. "Ban history" = documented public reports of bans specifically tied to virtual-controller software in that title. Absence of reports is not proof of safety — policies differ per game and change over time; check the rules of what you play.
Source for the policy line (opens in a new tab, accessed 2026-09-18): Embark's official Hotfix 1.4.1 patch notes — "Clients running key re-mapping programs on PC will not have access to aim assist": a condition on aim assist, not a ban, and no ban reports tied to virtual-pad software in this title are known to us. Separate and unrelated to emulators: Epic's own help page on the broken "Lock Input Method As Mouse" setting — Fortnite-side input arbitration.
How to think about the risk yourself
A framework that stays true even after this page is outdated.
The driver question. Anti-cheats technically can enumerate drivers and flag anything. In practice, ViGEmBus is in the same trust bucket as your mouse vendor's software: signed, widely deployed, used by tools that have nothing to do with gaming advantage (remote play, accessibility, controller testing). A publisher that blocks it declares war on a large chunk of its own paying audience — which is why, years into this category's existence, no major title has done it.
The input block. There is no filter driver to install. While emulation is on, Inputize suppresses the physical keyboard & mouse on the normal/legacy path in user mode — a standard Windows low-level input hook plus its own Raw Input window — and the block disappears the moment emulation stops (F8) or the app closes. Raw Input (`WM_INPUT`) is a separate path, so a game that uses it still sees the physical mouse; MW4, for example, works without any kernel component of ours once its Aiming Input Device is set to Controller. Nothing is written into device-class filters, so there is no driver package, no UAC prompt, no reboot and no recovery script; the only driver involved is still ViGEmBus.
The behavior question. The realistic enforcement path is not driver-scanning but behavior: statistical analysis of input. That is the one layer where a tool like Inputize genuinely operates, and it is exactly why SAB exists — to make the signal's shape human rather than machine-perfect. We build that for feel and fairness of play, not as a stealth layer, and we do not pretend it is a shield.
The per-game question. Everything finally comes down to the specific game's rules, and those are the publisher's to set — sometimes explicitly (The Finals), usually silently. Check the rules of what you play, prefer titles with no enforcement history against this category if you are risk-averse, and treat any "undetectable" marketing from any vendor as the red flag it is.
Questions
Short answers to what people ask most.
Can I get banned for using Inputize?
No game has ever publicly banned for Inputize specifically. Its architecture is the least suspicious in the category: same Microsoft-signed ViGEmBus driver as DS4Windows and Parsec, no injection, no file access. The honest caveat: no tool in this category can promise immunity, and The Finals is the one title that restricts the category by policy — its 1.4.1 line ends aim assist for key re-mapping clients on PC. See the per-game table above.
Why would anti-cheats flag DS4Windows or Parsec users if they banned virtual controllers?
They share the exact same driver Inputize uses: ViGEmBus, a Microsoft-signed virtual gamepad driver installed on millions of machines. DS4Windows alone has millions of users; Parsec is a mainstream remote-play app. Flagging ViGEmBus would break all of those tools and their users at once — enormous collateral damage for a publisher. That shared mainstream driver is the core reason virtual controllers sit in a tolerated gray zone rather than the cheat bucket.
What makes Inputize different from cheat software?
Cheat software reads or writes game memory, injects code into the game process, or manipulates game files. Inputize does none of that: it works purely at the Windows input layer, converting your keyboard and mouse into a standard virtual Xbox 360 controller. To the game it is indistinguishable from a person using a real gamepad — because at the data level, that is exactly what it sees.
Which games carry a ban risk with virtual controllers?
No title in our compatibility table has public ban reports tied to virtual-pad software. The Finals is the one we flag for a different reason: Embark's patch 1.4.1 line ends aim assist for key re-mapping clients on PC, so read its guide before you play. Policies change, so check the rules of whatever you play.
Does SAB protect against bans?
No — and we never claim it does. SAB shapes the stick signal into natural, human-paced movement instead of instant synthetic edges. That is about the quality and feel of the signal, not about defeating anti-cheat analysis. Anti-cheat policies differ per game and change over time; no tool in this category promises undetectability.
Is there a trial or is it a subscription?
No subscription — €19.99 once with all updates included. Inputize is a digital key delivered instantly: all sales are final and the license is non-refundable, an unused key included.
One payment. Lifetime license.
Virtual controller with aim assist, anti-recoil and response curves — €19.99 once, updates free forever.
Buy Inputize — €19.99