Controller Won't Charge
Controllers that won't charge are usually failing at one of three layers: the cable (charge-only vs data-capable, worn USB-C connector), the controller's charge port (debris, bent pin, oxidation), or the battery cell itself (depleted below recovery, swollen, or end-of-life). Test each layer in order — cheapest fix first — before assuming the controller is dead.
Diagnose before you fix
Confirm the symptom and measure its severity first. The test result tells you whether to clean, recalibrate, or replace — different severities call for different fixes.
Battery Health
Once the controller charges enough to connect, run the battery health check to confirm whether the cell holds capacity normally. The tool reads live battery level over Web Bluetooth and tracks degradation over multiple readings. If the controller charges to 100% but drops to 30% within an hour of light use, the cell is the actual problem — not the charging path you just fixed.
Run the battery health- Multiple USB cables (test with at least two known-good data cables)
- Compressed air
- A wooden or plastic toothpick (do not use metal)
- A different USB power source (wall adapter, different PC port, console front port)
Step by step
Work through these in order. After the last step, run the diagnostic again to confirm the fix held.
- 01
Try a different cable first
The single most common cause of charging failure is the cable, not the controller. Many USB-C cables that ship with phones and accessories are charge-only at low wattage and can't deliver enough power to charge a depleted controller. Try at least two different cables — ideally the cable that came with the controller, plus a known-good data cable.
CautionCharge-only cables can be visually identical to data-capable cables. If a cable charges your phone but not the controller, that doesn't prove the cable is fine — phones and controllers have different power negotiation. Use the cable that shipped with the controller before declaring the controller broken.
- 02
Try a different power source
USB ports differ in how much power they deliver. A USB 2.0 port on an older laptop may not supply enough current to charge a fully depleted controller. Try plugging into the console's front USB port (Xbox/PS5 controllers), a USB wall adapter rated for at least 5V/2A, or a different computer. If the controller charges from a different source, the original port was the issue.
- 03
Inspect and clean the charge port
Look into the controller's USB-C or micro-USB port with a flashlight. Look for lint, dust, bent pins, or oxidation. Pocket lint compresses inside USB-C ports over time and prevents the cable from making full contact. Use compressed air first, then carefully dislodge debris with a wooden or plastic toothpick. Never use metal — it can short the contacts or bend pins.
CautionUSB-C ports have small pins on the inside top and bottom. Bent pins cause permanent intermittent contact. If a pin is visibly bent, do not try to straighten it yourself — the pin is part of a fragile assembly and breaking it means replacing the whole charging board.
- 04
Charge in a powered-off state
Some controllers refuse to charge while powered on if the cable can't supply both operating current and charging current simultaneously. Power the controller off completely (long-press the PS/Xbox/Home button or remove batteries), then plug it in. Leave it for at least 30 minutes before retesting. Deeply depleted lithium cells can take 10–20 minutes of trickle charging before they're stable enough to register as charging.
- 05
Reset the controller
A stuck firmware state can prevent the charging controller from recognizing input power. On DualSense, use the recessed reset button on the back. On Xbox controllers, hold the Xbox button for 6 seconds to power down completely. On Joy-Con, press and hold the SYNC button. After resetting, plug the controller in and check the charge LED behavior — a status LED that wasn't lighting before may begin lighting after reset.
- 06
Test on a different controller of the same model
If you have access to a second controller of the same model, swap the cable and power source you've been using. If the second controller charges with the same setup, the original controller's hardware is failing. If neither charges, the cable or power source is the actual issue. This isolation step is the cheapest way to confirm whether you need a repair or a new charging cable.
- 07
Decide: repair, warranty, or retire
If the controller is under warranty, request a repair through the manufacturer — Sony, Microsoft, and Nintendo all repair charging-port issues. Out of warranty, USB-C port replacements cost $20–50 at most repair shops or can be DIY with iFixit's guides. If the battery itself is swollen (visible bulge in the controller shell), retire the controller immediately — swollen lithium cells can vent or ignite.
CautionA controller with a visibly swollen body or shell that no longer closes flat has a damaged lithium cell. Stop using it, do not attempt to charge it further, and dispose of it through a battery recycling program (Best Buy, Home Depot, and most electronics retailers accept lithium batteries). Swollen cells are an active fire risk.
Where to go next
Persistent symptoms usually mean hardware wear that cleaning and recalibration can't reach. These resources cover repair, replacement, and warranty paths.
Other tests for the same controller
A symptom rarely arrives alone. Worn sticks often coincide with deadzone creep and reduced circularity — run the related diagnostics while the controller is already in your hands.
Variants of this symptom
The same underlying issue presents differently across controllers. These device-specific guides cover the variations.
battery questions
Stopping just short of full is normal lithium-ion behavior — manufacturers cap charging slightly below 100% to extend battery lifespan. The controller still functions normally and the display rounds up. If the controller stops charging at 80% or lower, that's a cell-degradation issue worth investigating with the battery health check.
Yes, if the cable is data-capable and the charger outputs at least 5V/1A. Most USB-PD phone chargers work fine. Avoid chargers rated below 1A — they may keep the controller alive but won't reliably charge a depleted cell. The cable matters more than the wall adapter for most charging failures.
Joy-Con don't have their own USB-C port — they charge through the Nintendo Switch's rail connector when attached, or through the official Joy-Con charging grip via USB-C. Third-party charging docks work via the rail connector too. If a Joy-Con won't charge in the dock, the rail contacts on the Joy-Con or dock are the issue, not a USB-C port.
DualSense: 6–12 hours of moderate use. Xbox Wireless Controller (AA): 30–40 hours on fresh alkalines. Xbox rechargeable pack: 10–20 hours. Switch Pro Controller: 30+ hours. 8BitDo Ultimate: 20 hours. If your runtime is dramatically below these, the cell is degraded — see the battery-drains-fast guide.
On most modern controllers, yes — iFixit has guides for DualSense, Xbox Wireless, Joy-Con, and Pro Controller battery replacements. The DualSense and Joy-Con batteries are about $15 each. The battery is usually soldered or spot-welded, so the difficulty varies. Always buy genuine replacement cells from reputable sources — counterfeit lithium cells are a serious fire risk.
The cell is end-of-life. Lithium batteries lose capacity over time — at the end of their service life, they can show 100% on the indicator but discharge within minutes of disconnection because the chemistry can no longer hold the stored energy. Replacement is the only fix; no amount of recalibration restores a chemically depleted cell.
Yes, modern controllers have charge-controller chips that stop drawing current once the cell is full. Trickle charging at 99–100% does add a small amount of stress over months and years, but the risk is negligible. The thing to avoid is leaving the controller plugged in to a damaged cable or a cable rated below the controller's input spec — that can heat the cable, not the controller.
Still seeing the issue?
Re-run the diagnostic to confirm whether the fix held or whether escalation is needed.
Run the test again