Chrome Not Playing Audio: The Tab Mute You Probably Missed

When Chrome stops playing audio — videos load, the play button works, the progress bar moves, but there’s silence — the cause is almost always one of three things, none of which require reinstalling Chrome.

The most overlooked cause: the specific tab is muted. Right-click the tab itself (not the page) → ‘Unmute site’ or ‘Unmute tab.’ Chrome lets you mute individual tabs and the state is sticky — once muted, the site stays muted across browser restarts. This single fix resolves the problem for most people who have been troubleshooting for an hour.

If the tab isn’t muted, the next two checks: Windows Volume Mixer (Win+I → System → Sound → Volume mixer) — make sure Chrome’s volume is up and the correct output device is selected. Audio sometimes routes to a wrong/disconnected output device (Bluetooth headphones that disconnected, HDMI to a monitor that’s off). The full diagnostic below covers what to do if neither of these are the cause.

Chrome’s site-level audio permissions

Chrome can block audio from specific sites. chrome://settings/content/sound — check the “Not allowed to play sound” list. If the problem site is listed there, remove it. Also confirm “Sites can play sound” is selected as the default behaviour. For a broader walkthrough, our Google Chrome Errors is a good next read.

This setting persists and is easy to set accidentally. Clicking “Block sound” on a permission prompt once blocks the site permanently until manually removed from this list.

Autoplay policy causing the issue

Chrome blocks autoplay audio on sites that haven’t received user interaction (a click, scroll, or keypress). When a page tries to auto-play audio without interaction, Chrome silently prevents it. The page shows as playing but produces no sound because Chrome blocked the autoplay before it started.

Test: click somewhere on the page (not the play button, anywhere on the page itself counts as interaction) → then try playing audio. If sound starts: autoplay policy was the cause. To allow autoplay permanently for a specific site: click the padlock in the address bar → Site settings → Sound → Allow.

Audio output device selection in Chrome

Chrome can be set to use a specific audio output device that’s no longer connected. If headphones were recently disconnected, a Bluetooth speaker was unpaired, or a USB audio interface was removed: Chrome may still be trying to route audio to that absent device.

In the address bar of any tab playing audio: click the Cast/audio icon (if present) → select the correct output. Or more reliably: right-click the speaker icon in the taskbar → Sound settings → Advanced → “App volume and device preferences” → find Chrome → change the output device to the correct one. After selecting the correct output, audio routes immediately without requiring a Chrome restart.

Exclusive audio mode conflict

Another application may have exclusive control of the audio device, preventing Chrome from accessing it. Communication apps (Teams, Discord, Zoom) and audio production software (DAWs, virtual mixers) commonly use exclusive mode. When one application holds the audio device exclusively, other applications produce silence.

Close all other audio-using applications → test Chrome. If audio resumes, one of those applications was holding exclusive control. The permanent fix: right-click the speaker icon → Sound settings → More sound settings → Playback tab → right-click the output device → Properties → Advanced tab → uncheck “Allow applications to take exclusive control of this device.” This prevents any single application from blocking others from using the audio output.

Audio driver and Chrome interaction

Chrome uses the Windows Audio Session API (WASAPI). When audio drivers are outdated or corrupted, WASAPI can fail for Chrome while other applications work — because those applications use different audio APIs that are less demanding.

Update the audio driver from the laptop manufacturer’s support page (not Windows Update — Windows Update often provides generic Realtek or Intel drivers, while manufacturer drivers include laptop-specific tuning that affects how WASAPI functions). After installing and restarting: test Chrome audio.

Chrome’s internal audio debugging

Navigate to chrome://media-internals/ while a video is playing. The “Players” section shows active media playback with detailed status. If a video is “playing” but audio is absent: look at the audio decoder status. An audio decoder error or a “null audio renderer” message means Chrome specifically can’t route audio for that content — pointing at a driver or audio API issue rather than a permission or mute issue.

This page is more useful than it looks. It shows whether Chrome is even attempting to play audio (sometimes it thinks audio is playing when it isn’t) and what kind of audio codec the media uses — useful for identifying codec-specific failures.

Hardware acceleration and audio decoding

Chrome’s hardware acceleration affects video decoding, which is linked to audio in certain video formats. When hardware acceleration causes decoding problems: video may load but audio track processing fails silently. Settings → System → turn off “Use hardware acceleration when available” → Relaunch → test audio. If sound returns: GPU driver issues are affecting media decoding. Update the GPU driver and re-enable hardware acceleration.

Our guide on Chrome performance issues covers the hardware acceleration and GPU driver interactions in more depth. For audio problems across all applications (not just Chrome), our Windows audio troubleshooting guide covers the audio driver reinstall and Windows Audio service restart that fix system-wide sound issues. Google’s Chrome audio documentation covers the WebAudio API behaviour and the site permission model for autoplay audio in more technical detail.

Extensions interfering with audio

Extensions that modify or intercept page audio — volume equalizers, audio enhancers, noise filters — can cause audio to fail if they’re incompatible with the current Chrome version or the specific site’s audio implementation. An extension that worked fine for months can break after a Chrome update changes the audio API it hooks into.

Open an Incognito window (Ctrl+Shift+N, extensions off by default) → test audio on the failing site. If audio works in Incognito: an extension is the cause. Disable extensions one at a time in chrome://extensions, testing audio after each, until the failing extension is identified. Update it, or remove it if an update isn’t available.

DRM-protected audio

Services like Spotify Web Player, Amazon Music web, and some video platforms use Widevine DRM for audio playback. If Widevine is outdated or not loading correctly, the audio track fails to decode despite the video appearing to play. Navigate to chrome://components/ → Widevine Content Decryption Module → click “Check for update.” After updating: test the DRM-protected service. Also confirm that hardware DRM support (needed for highest quality on some services) is available: the same Widevine entry should show a version and “Up to date.”

Sample rate mismatch

Chrome outputs audio at the sample rate configured for the Windows audio device. If the device is set to an unusual sample rate (192000 Hz for studio recording purposes, for example) and the web content is encoded at a different rate: the resampling occasionally fails silently in specific Chrome versions. Right-click speaker → Sound settings → More sound settings → Playback → right-click output device → Properties → Advanced → Default Format → try 24-bit, 48000 Hz (Studio Quality) as a baseline. After changing: restart Chrome and test.

Windows Audio service restart

The Windows Audio service occasionally gets into a state where it accepts connections but fails to route audio correctly — Chrome appears to have audio permission but produces no output. Win + R → services.msc → “Windows Audio” → right-click → Restart. Also restart “Windows Audio Endpoint Builder.” After restarting both services: test Chrome audio without restarting Chrome — the services reconnect to running applications.

If the services can’t be restarted because they’re stopping then failing to start: this indicates a deeper audio infrastructure issue. SFC /scannow (administrator Command Prompt) checks for corrupted Windows audio system files and repairs them if found.

Multiple user profiles and audio isolation

Chrome profiles are audio-isolated. Audio settings, blocked sites, and volume mixer settings for one Chrome profile don’t affect another. If Chrome is signed into the “wrong” profile: the audio settings saved for the expected profile aren’t active. Check the profile icon in the top right — confirm it’s the expected profile. Switch profiles if needed and recheck the tab mute status and site audio permissions in the correct profile.

Spatial audio and format conversion

Windows 11’s spatial audio feature (Settings → Sound → Spatial audio, or right-click sound icon → Spatial sound → Windows Sonic for Headphones / Dolby Atmos) processes audio through a spatial rendering pipeline before it reaches headphones or speakers. Incompatibilities between Chrome’s audio output format and the spatial audio processor occasionally cause silence or distorted audio specifically in Chrome while other applications work.

Test: Settings → System → Sound → scroll to device properties → Spatial audio → Off → test Chrome. If audio resumes: the spatial audio processor was incompatible with Chrome’s audio output. Use spatial audio only when it works with all applications, or configure it off when using Chrome for audio-intensive tasks.

System sounds working but Chrome silent after reboot

This specific pattern — system sounds fine, Chrome silent after restart — often means Chrome’s volume in the Windows Volume Mixer was set to zero and persisted. The Volume Mixer remembers per-application volume settings between sessions. Open the Volume Mixer (right-click taskbar speaker icon → Open Volume Mixer) while Chrome is running: look for the Chrome slider. If it’s at zero or visually different from other applications: drag it to 100% and test.

Windows resets the Volume Mixer after updates sometimes, but more commonly the slider was set low by accident — Chrome was muted while adjusting volume for another application and the mute stuck. This three-second fix in the Volume Mixer resolves a disproportionately large number of “Chrome has no sound” support requests.

Web Audio API vs HTML5 audio — different failure modes

Web applications use two different audio systems: HTML5 Audio (the standard <audio> element) and Web Audio API (a more powerful programmatic audio system). These have different permission handling and failure modes in Chrome. A site using Web Audio API may be silent even when HTML5 audio works correctly on the same machine.

How to tell which a site uses: F12 → Console → look for “AudioContext” errors. Web Audio API sites that are failing often log errors about AudioContext being suspended or about user gesture requirements. These errors point directly at the autoplay policy issue — Chrome suspended the AudioContext because there was no user interaction, and the developer hasn’t handled this correctly. Clicking on the page before expecting sound often resolves this class of issue.

Chrome policy restricting audio

Enterprise Chrome policies can restrict audio in specific ways — blocking audio on specific categories of sites, or forcing audio permissions to always be denied for certain URLs. Navigate to chrome://policy/ → look for “AudioCaptureAllowed” or “DefaultSoundSetting” policies. If these appear with restrictive values on a personal machine (they shouldn’t be there without enterprise management): the machine may have enterprise Chrome policies applied, possibly through a previous domain join or management tool that wasn’t fully removed.

On truly personal machines, chrome://policy/ should show no enterprise policies. If it does show policies: removing the machine from domain management or using the Chrome Policy Remover tool removes orphaned enterprise policies that are restricting audio and other permissions.

The quick diagnostic checklist

Before spending time on driver updates and audio service restarts: take two minutes to confirm the obvious. Right-click the Chrome tab → is there a speaker icon with an X? Unmute. Open Volume Mixer → is Chrome at zero? Raise it. Open chrome://settings/content/sound → is the failing site in the blocked list? Remove it. Click somewhere on the page before pressing play → does audio start? The autoplay policy was blocking it.

These four checks resolve at least half of Chrome audio problems and each takes under 30 seconds. The driver, hardware acceleration, and service restart approaches are genuinely necessary for the remaining cases — but trying them before the simple checks wastes time on fixes that don’t apply to the actual cause.

For persistent Chrome audio failures where the simple fixes don’t help and the driver is current: try creating a new Chrome profile (Profile icon → Add → Continue without signing in) and testing audio in the new profile. If audio works in the new profile, the old profile has corrupted audio settings or extension configurations that can’t be fixed from within the profile. Migrating to the new profile by signing in with a Google account restores synced data, while leaving the problematic audio configuration behind.

One last thing worth noting: some streaming sites intentionally mute their content during ad periods on free tiers, or apply audio ducking when specific conditions are met. If the “no audio” occurs only at specific moments in playback (starts of videos, specific time codes) rather than all the time: this is likely the site’s design rather than a Chrome or system problem. Refreshing the page or switching to a paid tier on those services resolves site-controlled audio management rather than any Chrome configuration change.