Search
Have an existing account?
Sign In
Gamepad Viewer Button Remapping
Rebind any controller button or axis to a different input. Fix mismatched mappings, swap controls, remap D-pad POV hats, and export your custom configuration as a shareable URL for OBS overlays.
No mappings yet
Click "Add Mapping" to create your first button rebind
Exported URL
How Button Remapping Works
Gamepad Viewer remapping lets you reassign any physical controller input to a different visual output on the overlay. This is essential when your controller reports buttons in a non-standard order or when using third-party adapters like the MayFlash GameCube adapter.
01
Select Controller
Choose which connected player (P1 through P4) you want to create mappings for from the dropdown above.
02
Add a Mapping
Click "Add Mapping" and select the input type: Button for face buttons and bumpers, Axis for sticks and triggers, or DPAD for directional pad hats.
03
Choose Source Input
Select which button or axis you want to remap from the dropdown. For example, choose A/Cross if your A button is reporting as a different input.
04
Capture Target
Click "Click to Set" and press the physical button on your controller within 3 seconds. The tool captures which raw input your controller sends.
05
Apply or Export
Hit "Apply Mapping" to activate it live, or "Export to URL" to generate a shareable link with your remapping baked into the URL parameters.
06
Use in OBS
Paste the exported URL into an OBS Browser Source. Your custom button mapping loads automatically every time the overlay opens.
Button and Axis Reference
Standard Gamepad API mapping used by Gamepad Viewer. Your controller may report inputs in a different order depending on the manufacturer and driver.
Standard Button Index Map
Face Buttons
A / Cross
Button 0B / Circle
Button 1X / Square
Button 2Y / Triangle
Button 3Bumpers and Triggers
LB / L1
Button 4RB / R1
Button 5LT / L2
Button 6RT / R2
Button 7System and Sticks
Select / Back
Button 8Start
Button 9LS / L3
Button 10RS / R3
Button 11D-Pad
D-Pad Up
Button 12D-Pad Down
Button 13D-Pad Left
Button 14D-Pad Right
Button 15Frequently Asked Questions
Why do I need button remapping?
Some controllers report buttons in a different order than the standard Gamepad API expects. This is common with third-party controllers, adapters like MayFlash, and older gamepads. Remapping fixes the visual display so the correct button lights up when pressed.
What is D-Pad POV Hat mapping?
Some controllers report D-pad input as a single axis value (a Point-of-View Hat Switch) rather than four separate buttons. The DPAD mapping type handles this by reading the axis value and splitting it into individual Up, Down, Left, and Right inputs for the visual overlay.
How does "Click to Set" capture work?
When you click the capture button, it enters a 3-second listening mode. During this window, press the physical button on your controller that you want to map. The tool reads the raw input index from the Gamepad API and assigns it to the selected visual output. If no input is detected within 3 seconds, the capture times out.
Can I disable a button from being mapped?
Yes. Each mapping row has an enable/disable toggle. When disabled, that mapping is ignored without deleting it. This is useful when you have a drifting axis that keeps interfering with the remapping process. Disable it, complete your other mappings, then re-enable it afterward.
Can I remap half of an axis (positive or negative only)?
No. Axis remapping applies to the full range of the axis (both positive and negative). Partial axis mapping is not supported and will be ignored by the system. You must map the complete axis.
How do I use my remapping in OBS?
Click Export to URL to generate a link with your mappings encoded as URL parameters. Copy that URL and paste it into an OBS Studio Browser Source. The mappings load automatically when OBS opens the viewer. You can also bookmark the URL for future sessions.
My GameCube controller shows wrong trigger values. How do I fix it?
MayFlash GameCube adapters often send trigger and stick data on non-standard axes. Add axis mappings for LT, RT, and both sticks, then use the capture feature to set each one to the correct physical input. This realigns the visual display to match your actual controller layout.
