How to Fix Audio and Sound Not Working in Google Chrome

When Google Chrome fails to play sound—leaving YouTube videos, Spotify web players, Netflix streams, or video conferencing tabs completely silent while other computer applications produce normal audio—the issue stems from per-tab audio muting, Windows 11 Volume Mixer routing misconfigurations, conflicting browser extensions, or corrupted audio hardware acceleration flags. Because modern operating systems allow independent volume and audio device assignments for every running application, Chrome can be muted or routed to an inactive audio endpoint without triggering global system audio alerts. Resolving this issue involves auditing Chrome sound permissions, re-assigning playback devices, and resetting browser media flags.

Understanding Why Chrome Audio Fails

Chromium delegates audio rendering to the operating system’s low-level audio session manager (WASAPI on Windows and CoreAudio on macOS). Chrome registers an independent audio client session for each media-playing tab. If an extension flags the tab as muted, or if Windows assigns Chrome’s audio output stream to a disconnected digital display or virtual audio cable, the sound stream plays into an empty buffer.

Common causes of Chrome audio loss include:

• Muted Site or Tab State: Accidentally clicking “Mute site” or setting site permissions to block sound playback globally.
• Windows Volume Mixer Output Override: Windows 11 Volume Mixer assigning Google Chrome to an inactive monitor HDMI port or disabled Bluetooth headset. For related network socket freezes, see our guide on fixing ERR_CONNECTION_RESET in Google Chrome.
• Corrupted Audio Drivers / Spatial Audio Conflicts: Third-party audio enhancements (such as Dolby Atmos or Sonic Spatial Audio) crashing Chrome’s audio sandbox.
• Conflicting Extensions: Video speed controllers, volume boosters, or equalizer add-ins crashing the internal WebAudio pipeline. (Check our guide on fixing NET::ERR_CERT_DATE_INVALID in Chrome).

Audio Layer	Operational Role	Failure Symptom
Chrome Tab Controller	Manages individual tab media playback states	Speaker icon with slash displayed on tab header
Site Permissions (Content Settings)	Controls domain-level audio privileges	Specific websites muted while others play sound
Windows Volume Mixer (WASAPI)	Routes app sound to physical sound cards	Chrome volume slider at 0% or routed to wrong speaker
Audio Sandbox Process	Isolates audio decoding from browser kernel	Crash in utility process halts all sound across tabs

Step 1: Check Tab and Domain Sound Permissions

Chrome allows users to mute entire domains or individual tabs with a single click. Verifying that the target website is permitted to play sound is the logical starting point:

1. Navigate to the website where audio is silent (e.g., YouTube).
2. Right-click the tab header at the top of the browser.
3. If the context menu displays Unmute site, click it immediately.
4. Next, click the View site information icon (the sliders or padlock icon located directly to the left of the URL in the address bar).
5. Click Site settings.
6. Scroll down to the Sound permission and ensure it is set to Allow (default) rather than Mute.
7. Reload the tab and test playback.

Step 2: Check Windows 11 Volume Mixer and Output Device Routing

Windows 11 maintains discrete volume levels and output destinations for every individual application. If Chrome is routed to a disconnected peripheral, sound will not reach your physical speakers.

1. Ensure media is actively playing in Google Chrome (e.g., a playing YouTube video).
2. Right-click the Speaker icon in the Windows system tray and select Open volume mixer.
3. Scroll down to the Apps section and locate Google Chrome.
4. Verify that the volume slider is turned up to at least 80% and that the small speaker icon is not set to muted.
5. Click the expander arrow next to Google Chrome to reveal its Output device setting.
6. Ensure it is set to Default or explicitly select your physical speakers / headphones rather than an unused monitor or virtual sound driver.
7. Click the Reset button at the bottom of the Volume Mixer to restore default application audio routing across the operating system.

Step 3: Test Chrome in an Incognito Window

Audio extensions (like Volume Booster, Equalizer Pro, or ad-blockers) can seize exclusive control of Chrome’s HTML5 audio elements and fail silently.

1. Press Ctrl + Shift + N to launch an Incognito window.
2. Navigate to the media page and test sound.
3. If audio plays clearly in Incognito, an installed extension is responsible.
4. Type chrome://extensions in the address bar, press Enter, and disable all audio or video enhancements.
5. Relaunch Chrome.

Step 4: Disable Audio Sandbox in Chrome Flags

Chrome executes audio processing inside an isolated sandbox. On certain systems, driver conflicts cause this sandbox process to deadlock, muting all playback.

1. Open a new tab, type chrome://flags, and press Enter.
2. In the search box at the top, type audio.
3. Locate Audio Service Sandbox (or Run audio service in utility process).
4. Change the dropdown from Default to Disabled.
5. Click the Relaunch button at the bottom of the window to apply the change.

Step 5: Restart the Windows Audio Service and Update Drivers

If the low-level Windows audio endpoint builder stopped communicating with the browser process, restarting the core audio daemons restores the session links.

1. Press Windows Key + R, type services.msc, and press Enter.
2. Scroll down to locate Windows Audio.
3. Right-click Windows Audio and select Restart.
4. If prompted that dependent services (like Windows Audio Endpoint Builder) will also restart, click Yes.
5. Close and reopen Google Chrome. Audio streams will now synchronize seamlessly with your hardware output devices.