Controller Headphone Jack Not Working
Controller headphone jack failure has two most-common causes: audio isn't routed to the controller (Windows or the console is still sending audio to the TV or default speakers), or you're using Bluetooth on PC — DualSense audio passthrough only works wired on PC. Physical jack issues come third, after both routing paths are checked.
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.
Audio Latency
If headphones work through the controller but audio feels laggy, the audio latency test measures actual delay between input and output through the controller's audio path. Latency significantly higher than normal points at Bluetooth-routed audio (already a limitation on PC) or a driver conflict. Silent output entirely means the audio path isn't reaching the controller at all — treat as a routing issue.
Run the audio latencyMic Test
The mic test verifies the controller's audio subsystem is connected to the OS at all. If the mic test detects audio input from the controller, the OS-level audio path is active — meaning output should work too and the failure is a routing setting. If the mic test also shows nothing, the entire audio subsystem isn't reaching the OS and the issue is deeper than jack-specific.
Run the mic test- A known-good 3.5mm headphone or earbuds (to isolate cable/plug issues)
- A USB data cable (DualSense on PC — audio passthrough is wired-only)
- Compressed air (for jack debris)
Step by step
Work through these in order. After the last step, run the diagnostic again to confirm the fix held.
- 01
Confirm the audio destination in system settings
On Windows, right-click the speaker icon → Sound settings → Output. Set the controller (usually 'Wireless Controller' or 'DualSense Wireless Controller') as the default output. Windows almost always keeps your existing speakers as default even after the controller connects. On PS5: Settings → Sound → Audio Output → Output Device → 'Headphones Connected to Controller.' Most 'jack not working' cases resolve here without touching anything physical.
- 02
On PC, connect the DualSense wired (Bluetooth doesn't pass audio)
This is the biggest single fact competing guides miss. On PC, the DualSense's 3.5mm audio passthrough only works over USB — Bluetooth does not carry audio to the controller. If you're on Bluetooth and headphones aren't producing sound, the fix is a USB data cable, not a driver update. This limitation is documented on PCGamingWiki and hasn't changed across firmware revisions.
- 03
Test with different headphones
A dead 3.5mm jack in the controller and dead headphones look identical. Plug a known-good second pair of headphones or earbuds into the controller. If they work, the original headphones are the issue. If they also fail, the failure is upstream of the physical jack. This rules out one of the cheapest possible causes in 30 seconds.
- 04
Clean the jack with compressed air
Pocket lint and dust settle into the 3.5mm port and prevent full contact with the plug — resulting in no audio or only one channel working. Blast the jack briefly with compressed air (upright can, quick pulses), then reinsert the headphone plug firmly and rotate it slightly to check for contact intermittency. A jack that produces audio only when the plug is rotated to a specific angle has worn contacts and needs shell service.
CautionKeep the compressed air can upright at all times. Tilting releases liquid propellant that can damage the jack contacts or nearby components.
- 05
Update controller firmware and try DS4Windows
Occasionally an audio-routing bug ships in a firmware revision and is fixed in a later one. Update via the PS5's accessories settings or the PC firmware updater. For persistent PC audio issues with the DualSense, DS4Windows presents the controller as an Xbox pad and reroutes audio via Windows' standard audio stack, which is more predictable than the DualSense's native Windows routing.
- 06
Verify balance and mute state
One-side-only audio is often a balance slider set fully to one side, not a broken jack. On PS5: Settings → Sound → Audio Output → check volume and balance. On Windows: right-click the speaker icon → Sound settings → click the controller under Output → Device properties → check the balance sliders and confirm neither channel is muted. This catches an audio-not-working case that has nothing to do with the controller.
- 07
Physical jack fault — repair or replace
If routing is confirmed correct, the controller is wired on PC, and multiple known-good headphones fail on both channels, the physical jack has failed. iFixit publishes 3.5mm jack replacement guides for DualSense and DualSense Edge — the port is a discrete component and can be replaced with intermediate soldering skill. For in-warranty controllers, pursue Sony service instead. Standard Xbox controllers use headset audio through the controller's dedicated headset port rather than a 3.5mm jack, which has its own separate failure modes.
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.
audio questions
The single most common cause on PC is that you're connected over Bluetooth. DualSense's 3.5mm audio passthrough is documented as USB-only on PC — Bluetooth does not carry audio to the controller regardless of driver. Connect a USB data cable and headphones through the jack will start working, provided Windows has the controller set as the output device.
Because the PS5 automatically routes audio to headphones connected to the DualSense as soon as they're plugged in, while Windows keeps its previous default output active and requires you to manually change it. Right-click the speaker icon → Sound settings → Output → pick the controller as the default. On the PS5, the console handles this without user intervention; on PC, you have to.
Two possibilities. Balance slider set to one side in Windows sound settings or PS5 audio settings is the cheapest cause to check first. Physical jack wear where one contact has degraded is the second, and shows a distinctive symptom: audio comes through both ears if you press or rotate the plug in a specific direction. That points at contact wear, and shell-level jack replacement is the durable fix.
Yes — same 3.5mm jack behavior, same Bluetooth-audio-passthrough limitation on PC, same wired-only requirement for audio out on PC. The Edge's additional features (back buttons, replaceable stick modules, profile switching) don't change how its audio subsystem behaves. Everything on this page applies to both controllers identically.
You can plug a wireless-transmitter dongle into the 3.5mm jack (like the ones some wireless headphones ship with), and the DualSense passes audio through it exactly as it would to wired headphones. The controller doesn't care what's on the other end of the jack. Same rules apply — wired connection to the console/PC, correct output routing.
Yes, both Xbox Series X/S controllers and Elite Series 2 have a 3.5mm jack for headsets. It handles both audio out and mic in for headset combos. Unlike the DualSense, it uses the Xbox Wireless protocol for audio (not Bluetooth), so it works wirelessly on the console. On PC via Bluetooth, similar limitations apply as with the DualSense — audio routing gets flaky, and the Xbox Wireless Adapter or wired connection is more reliable.
Not through the controller's native path — Bluetooth audio passthrough to the DualSense isn't supported on PC and this hasn't changed across firmware updates. Third-party tools like DS4Windows don't override this limitation because it's in how the controller and Windows negotiate audio profiles over Bluetooth. If wireless audio matters to you, use standalone Bluetooth headphones connected to Windows directly, and use the DualSense only for controller input.
Still seeing the issue?
Re-run the diagnostic to confirm whether the fix held or whether escalation is needed.
Run the test again