DeviceOK
SearchDevice checks
Home / Fixes / Speaker or Headphone Crackling

audio · evidence-led troubleshooting

Speaker or Headphone Crackling

Test known left/right or frequency audio before changing drivers or replacing speakers when audio contains crackles, pops, or distortion. The result should determine which troubleshooting layer comes next.

Reviewed 2026-08-116 diagnostic steps1 official sources
Run Speaker testSee fault tree ↓

What this symptom means

Noise is different from silence. Compare another port, cable, wireless path, power source, and app to learn whether the noise follows the device or the environment.

Diagnostic principleSeparate device selection, mute/volume, channel routing, Bluetooth profile, cable/contact faults and transducer failure. A working left/right test is strong evidence against total output-device failure.

Fault tree

Speaker/headphone fault tree

Use the observation that best matches what you can reproduce. Do not treat every cause as equally likely.

1
Wrong output/routing

Evidence: Another output plays or DeviceOK works while one app is silent.

Next: Align OS and app output selection, per-app volume and Bluetooth routing.

2
Channel/contact problem

Evidence: One side is missing or changes when a plug/cable moves.

Next: Use left/right test, reseat connectors, compare cable/device.

3
Bluetooth profile/state

Evidence: Quality changes sharply when microphone use starts or one app opens voice mode.

Next: Check Bluetooth audio profile/device mode and app input/output selection.

4
Physical driver failure

Evidence: One channel remains dead on multiple sources/cables.

Next: Service/replace only after routing and connector checks.

Interpret the result

Evidence matrix

A test result is useful only if it changes the next troubleshooting branch.

ObservationWhat it supportsPrioritize next
Both test channels audibleThe browser can render audio and the selected output path is functioning.Affected app, routing, codec/profile or content.
Only one side audibleA channel-specific failure exists somewhere from source routing to the physical driver.Balance setting, plug/cable/contact, adapter or speaker/headphone channel.
No browser sound, system sounds workThe hardware can play audio but browser output is affected.Browser/site mute, per-app volume, output selection or policy.
No sound anywhereThe failure is wider than one site.OS output, connection, power, driver/firmware or hardware.

Fast baseline

Rule out the simple causes first

  1. 1

    Run the DeviceOK speaker/headphone test and note which channel or tone is affected.

  2. 2

    Confirm the correct output device is selected and volume/mute controls are set correctly.

  3. 3

    Reconnect the cable/Bluetooth device and test another port when applicable.

Full sequence

Work from reversible checks to invasive ones

Do not assume every noise problem is a driver problem; analog cables, grounding, RF interference, connectors and physical damage can create similar symptoms.

  1. 1

    Run the DeviceOK speaker/headphone test and note which channel or tone is affected.

  2. 2

    Confirm the correct output device is selected and volume/mute controls are set correctly.

  3. 3

    Reconnect the cable/Bluetooth device and test another port when applicable.

  4. 4

    Check whether audio works in another trusted app.

  5. 5

    Review operating-system output, balance, and enhancement settings.

  6. 6

    If the same channel/device fails everywhere, consult the manufacturer's official support path.

Platform branches

Where the setting lives

Windows

  • System → Sound → Output
  • Volume mixer per-app routing
  • Disable/compare spatial/enhancement processing only as a controlled test

macOS

  • System Settings → Sound → Output
  • Check Audio MIDI Setup only for sample/channel configuration issues
  • Compare wired vs Bluetooth path

Browser

  • Check tab/site mute
  • Play left/right test at safe volume
  • Select a different OS output then return to the intended device if routing is stale
If it works in DeviceOK

Known browser audio reaching the expected output makes a completely dead playback path less likely. If the original symptom remains, keep the next checks above the hardware layer until evidence says otherwise.

If it also fails here

Silence or channel failure across trusted sources broadens the problem to routing, connection, driver or hardware. Compare the simplest direct connection and official diagnostic path before replacement.

Escalation threshold

When software troubleshooting has stopped being high value

  • One channel dead across multiple sources
  • Audible distortion at low safe volume across sources
  • Battery swelling or overheating in wireless headphones
  • Connector physically damaged
Changed one variable?The noise should disappear or materially drop in a repeatable comparison, not just during one quiet moment. Retest under the same condition so the result is comparable.
Retest Speaker test