How to document controller defects for a return

A controller that drops inputs, drifts, or has a button that only works at an angle can be hard to describe to a seller. A short, clear record makes it easier to show what happens and when.

Use the Gamepad Test to check buttons, sticks, triggers, and vibration in your browser. Then capture the failure, note how the controller was connected, and send the evidence with your return request.

Test the controller and capture the fault

1. Open the Gamepad Test, connect the controller, and press a control once if it does not appear. Keep the controller connected the same way you normally use it, such as by USB or Bluetooth.
2. Check the controls one at a time. Press each button, move both sticks through their full range, and squeeze each trigger. Watch for a control that does not register, stays active after release, jumps, or reports input inconsistently.
3. Repeat the action that causes the problem several times. For stick drift, release the stick and leave the controller untouched for a few seconds. For an intermittent button, press and release it at a steady pace, then note how many attempts fail.
4. If the test offers a vibration check, try it and note whether vibration is absent, weak, or only works on one side. Vibration may not be available in every browser or for every controller.
5. Capture the test while the defect is visible. A screenshot can show a stick that remains off-center or a button that stays registered. A short video made with a phone can show both the physical press and the test response at the same time.
6. Run the same check once more after reconnecting the controller. Keep the second result, even if the fault does not happen again, and record that it was intermittent.

Do not edit the evidence in a way that hides the controller state or changes the sequence. If you need to trim a video for file size, keep the unedited original until the return is resolved.

What the result means

A button never registers, or remains active after release

If the same button misses presses or appears held down through repeated tests, that is useful evidence of an input fault. Try it in another browser or on another computer if you can. If the same problem follows the controller, it is less likely to be a browser-specific issue.

A stick reports movement while untouched

A stick that continues to show input near its resting position may have drift or a worn sensor. Record the untouched state and how it changes when you move and release the stick. A small reading can occur around the center on some controllers, so include what the connected game does rather than treating every nonzero value as proof of a defect.

The controller does not appear in the test

This alone does not prove the controller is broken. Try a different USB port or reconnect Bluetooth, then press a controller control again. A browser, cable, adapter, operating system, or pairing problem can prevent the test from receiving input.

Inputs work but vibration does not

Vibration support depends on the controller, browser, connection, and operating system. Note the exact setup and whether vibration works in a game or another device before calling it a hardware failure.

Make the return request easy to verify

1. Describe one defect at a time. Write what you press or move, what should happen, and what actually happens. For example: “The left stick continues to register upward input after I release it.”
2. Include the test setup. Note the controller model, computer or phone, browser, connection type, and date. If you changed a cable, port, or device during testing, mention that too.
3. Attach the clearest evidence. Include a screenshot or short video that shows the fault and the test page. Keep the file unedited when practical, and make sure the controller and its response are visible.
4. Explain whether the fault repeats. Say how often it happened and whether reconnecting changed anything. If the problem appears only after a few minutes or during a particular movement, describe that pattern.
5. Keep personal details private. Use the seller's official return form or support channel. Do not post a receipt, address, order number, or controller serial number publicly. Follow the seller's instructions about packaging, accessories, and shipping.

For a broader checklist of evidence to keep, see how to document hardware problems for warranty support.

Check the connection before you return it

1. Reconnect the controller. Unplug and reconnect a wired controller, or remove and pair a Bluetooth controller again. On Windows 11, check Settings › Bluetooth & devices › Devices. On macOS, check System Settings › Bluetooth.
2. Try another port or cable. A damaged cable or loose port can cause missed inputs or disconnects. If the controller has a removable cable, test with a known working data cable, not just a charging cable.
3. Test on another device. If possible, repeat the same button or stick check on a second computer. A fault that follows the controller is stronger evidence than a fault seen in one browser on one computer.
4. Stop before opening the controller. Do not disassemble it or attempt a repair while you are seeking a return unless the seller tells you to. Opening it may affect return eligibility.

When the controller is likely faulty

A defect is more convincing when the same input problem repeats across reconnects or on another device, while other controls continue to work. Include the failed and successful checks so the seller can see the difference. A browser test can show what input reaches the computer, but it cannot identify the exact damaged component or certify a repair diagnosis.

If the problem only happens in one game, check that game's control mapping before returning the controller. If the same physical control fails across games and devices, follow the seller's return or warranty process rather than trying to repair it yourself.