Any input.
Any controller.

PadForge passes Xbox impulse trigger data straight to the assigned physical Xbox One, Elite, or Series pad. The same data routes to DualSense as Adaptive Trigger Vibration, so a DualSense playing Forza buzzes the triggers in step with an Xbox pad doing the same. Plus audio-bass-driven trigger rumble, a constant trigger force, and a Trigger Routing card that feeds the main rumble motor into the trigger motors with per-trigger source, scale, and activator settings.

Seven adaptive trigger modes with a live preview that draws the resistance curve as you drag. Fourteen lightbar modes, six of them driven by your system audio (three Audio Pulse variants and three that follow the level). The DualSense lights and triggers light up in games that have never heard of a DualSense.

The DualSense and DualShock 4 have a speaker built in, and PadForge can drive it. Mirror a Windows audio output to the pad, or send a slot's macro sounds straight to it. DualSense over USB or Bluetooth, DualShock 4 over Bluetooth. Pads with haptic actuators instead of a speaker, like a Joy-Con, Switch Pro, Steam Controller, or Steam Deck, play the same sounds as a vibrating tone, and a combined Joy-Con pair plays it through the coil the game drives. A Wii Remote plays them through its own speaker.

The DualSense and DualShock 4 get a processing chain of their own: bs2b crossfeed for the headset jack with the classic presets, Jan Meier, and a custom cutoff and feed, a graphic parametric EQ you drag into shape or load from an AutoEq profile for your exact headphones, and a limiter so a boosted band never clips the pad's encoder. Follow Headphone Jack switches the pad's output the moment you plug in, with or without a virtual DualSense on the slot.

Route a slot's rumble to any Windows audio device as a low-frequency channel, so a transducer under the seat moves with the game. Independent low and high motor routing, per-voice gain, and a carrier frequency from 20 to 120 Hz with a sweep to find where your shaker responds. The pad keeps its own rumble.

When a game paints the lightbar on a virtual PlayStation controller, PadForge can send that same color out to your Razer Chroma devices and your Logitech LIGHTSYNC devices. Chroma goes through the local server Razer Synapse runs, and PadForge shows up in Synapse's Connect tab where you scope it to the devices you want. LIGHTSYNC calls the LED engine G HUB already registered on the machine, saves the lighting you had when it connects, and puts it back when it stops. PadForge ships no Razer or Logitech code for either one. Which controller is in your hands does not matter, because the color comes from the virtual pad the game is writing to.

Sensa HD haptics sit in a headset, a mouse, or a chair rather than in the pad. PadForge streams the loudest of a slot's four rumble voices into the Interhaptics engine Razer ships, which renders it on gear like the Wolverine V3 line, the Kraken V4 Pro, and the Freyja. What crosses is amplitude, as one looping effect between 65 and 300 Hz, with no left and right split. It needs Razer Synapse 4 with Sensa HD Haptics, and the device's Haptic Source set to Sensa HD Games.

A pad with haptic coils and no speaker normally gets a reduction. PadForge measures the loudest frequency in the sound each tick and plays that single tone, which lands beeps and cues and loses everything else. The 2026 Steam Controller does not need the reduction. Its four coils, two in the grips and two under the trackpads, take 8 kHz stereo audio over the pad's own reports, and PadForge streams the mix into them. A low-pass cutoff, 250 Hz by default, keeps the coils vibrating instead of audibly playing the sound, and you can raise it for sharper detail. Wired and over the dongle. A Bluetooth link falls back to the tone.

Driven in the wheel's own protocol. Logitech G29, G923, G27, G25, Driving Force, Driving Force Pro, Driving Force GT, MOMO Force, MOMO Racing and WingMan Formula Force GP. Thrustmaster T300RS, T-GT II, T248, TX, TS-XW and TS-PC Racer. Fanatec CSL DD, GT DD Pro, CSL Elite, ClubSport V2 and V2.5, Podium DD1 and DD2, CSR Elite and the Porsche 911 GT3 RS. Rotation range, autocenter and the LED strip come with it on the wheels that have them, and Fanatec ClubSport V3, CSL Elite and CSL Loadcell pedals get their own rumble.

Recognized as wheels and mapped like one, with force feedback through the standard path: Logitech G920 and PRO Racing Wheel, Thrustmaster T500RS, Fanatec ClubSport V1, Moza R3, R5, R9, R12, R16 and R21, Simucube 1 and Simucube 2 Sport, Pro and Ultimate, Simagic M10, Alpha Mini, Alpha and Alpha U, Asetek Invicta, Forte, La Prima and Tony Kannan, Cammus C5 and C12, VRS DirectForce Pro, PXN VD6 and V900, the Xbox 360 Wireless Racing Wheel and OpenFFBoard builds.

Sticks: Thrustmaster HOTAS Warthog and T.16000M, Logitech Extreme 3D, Saitek Pro Flight X-56 Rhino, VIRPIL VPC MongoosT-50CM3 in both hands, VKB Gunfighter Mk.III Space Combat Edition in both hands, Turtle Beach VelocityOne Flightstick and the Yawman Arrow. Throttles: HOTAS Warthog, X-56 Rhino, VelocityOne and the VIRPIL VPC VMAX Prime.

Each is read as its own device, so a stick, a throttle and a set of pedals can feed one virtual controller at once, and a button on the throttle can chord with a button on the stick.

The page reads the phone's own gyroscope and accelerometer and streams them as motion, so tilting the handset aims. Browsers only hand out sensor data over a secure connection, so PadForge binds a self-signed certificate and serves the controller over HTTPS whenever it can. A QR code on the Dashboard gets the phone there without anyone typing an address.

The custom builder starts from a blank pad and lets you place sticks, buttons, triggers, D-pads and touch surfaces anywhere on it, then save it. Layouts are stored with your settings, so the phone loads yours the next time it connects.

Remote Link shares devices between PadForge PCs, on your network or across the internet. A controller, wheel, or HOTAS plugged into one PC drives a game on another, both directions at once, and the feedback comes home: rumble, force feedback, adaptive triggers, lightbar, player LEDs, and the controller speaker all play on the physical device wherever it lives. Pair once with a six-digit code on your network, or an eight-character single-use code over the internet. No VPN, no port forwarding. Trusted PCs reconnect on their own. A gamepad-only switch keeps a paired PC away from your keyboard, mouse, and macros.

PadForge reads MIDI input devices as mapping sources. Notes, Control Change knobs, pitch bend, and encoder dials from a MIDI keyboard or pad controller bind like any button or axis, so a piano key can press A and a mod wheel can pull a trigger. It rides the same Windows MIDI Services stack the MIDI virtual controller uses, with no bridge software.

Map sticks to Control Change messages. Map buttons to Note On / Note Off. Set velocity per slot. PadForge creates a real Windows MIDI endpoint that DAWs (Ableton Live, FL Studio, Reaper), VJ tools, and stage lighting apps can subscribe to. No loopMIDI bridge.

Turn on external control on the Profiles page and PadForge serves a named pipe on the local machine while the engine runs. Playnite, LaunchBox, a batch file, or anything that can write one line sends activate with a profile name, deactivate to fall back to Default, or query to ask what is loaded. A profile activated that way is held until the script releases it or you switch by hand, so a game-launch rule cannot pull it back out from under the script. PadForge's own executable takes the same instructions as arguments and forwards them down the pipe, so running it a second time is the command. The pipe is open to authenticated users on that machine and nowhere else, and the whole thing stays off until you turn it on.

The engine's poll interval is a global setting, and a profile can overrule it. Pick 1000, 500, 250, 125, or 62.5 Hz in the profile dialog and that rate applies while the profile is active, with every other profile falling back to the global value. The Settings page names the profile in charge under the knob. Nothing restarts on a switch, because the loop recomputes its target every cycle.

Sixteen slots, and XInput's four-pad ceiling stops being your ceiling: slots beyond four present as DirectInput or as other virtual shapes, so a room full of players all land in the same game. Every slot carries its own profile, its own layers, and its own feedback routing.