Chrome playing no audio — videos completely silent, no sound from web apps, Zoom working fine but YouTube silent, or the opposite — is almost always caused by something in the audio routing rather than Chrome itself being broken. The good news: five minutes of checking covers the most common causes in a predictable order. For the bigger picture, our Chrome How-To Guides pulls everything together.
Start with the Volume Mixer
Right-click the speaker icon in the Windows taskbar → “Open Volume Mixer.” Chrome should appear as a separate slider alongside system sounds and other applications. Is Chrome’s slider at zero? Is it muted (the speaker icon with an X)? If either: that’s your fix. Chrome’s Volume Mixer slider is independent of the system master volume — you can have system volume at 50 and Chrome at zero, producing silence in Chrome while everything else plays normally.
This accounts for more “Chrome audio not working” cases than anything else. The slider gets dragged accidentally, or a keyboard volume shortcut with Chrome focused only adjusts Chrome’s level rather than the system master volume.
Tab-specific muting
Chrome mutes individual tabs. Look at the tab where sound should be playing — does the tab icon show a speaker with a line through it? Right-click the tab → “Unmute tab.” The mute state persists after you close and reopen the tab on the same URL, which catches people out when a tab was muted and later reopened expecting sound.
Chrome’s own sound settings
chrome://settings/content/sound → confirm the default is “Sites can play sound.” If this is set to “Don’t allow sites to play sound” (the alternative): Chrome silently blocks all audio from all websites. Check this especially if sound stopped working suddenly with no obvious cause — this setting is rarely changed intentionally but occasionally gets toggled through a permissions prompt or settings exploration.
Also check: the same settings page shows a “Not allowed to play sound” list. If the site with silent audio is listed there: remove it from the blocked list → the site regains sound permission.
Windows audio output device
If Chrome is sending audio to the right device but that device isn’t what you’re using: silence results. Click the speaker icon in the Windows taskbar → the dropdown shows the current default audio output device. Check whether Chrome is using the correct one. If Chrome is outputting to “HDMI Output” while you’re using headphones connected to 3.5mm: you’ll hear nothing.
Windows 11 has app-level audio device assignment: Settings → System → Sound → Volume mixer → find Chrome → see which audio device it’s assigned to. If it shows a different device than your intended output: change it here. This affects Chrome specifically without changing other applications’ audio routing.
Site-specific audio permissions
Some sites require explicit camera/microphone access for audio to work in both directions. For WebRTC-based audio (video call platforms, online music tools, some games): if Chrome has blocked microphone access, the site’s audio may work in one direction (you hear them) but not the other (they hear you). This isn’t the same as the sound blocking setting above — it’s specifically about interactive audio.
chrome://settings/content/microphone → see which sites are blocked → if the site you’re troubleshooting is there: remove it and reload the site. Grant the microphone permission when prompted.
Hardware acceleration and audio rendering
A less obvious cause: hardware acceleration affects Chrome’s media pipeline, including audio for video content. On some GPU driver configurations, disabling hardware acceleration resolves audio problems on video platforms (YouTube, Netflix, Twitch). chrome://settings → System → disable hardware acceleration → Relaunch Chrome → test audio on the affected site.
If that fixes it: the GPU driver has an issue with Chrome’s media pipeline. Update the driver from the manufacturer’s site (nvidia.com, amd.com, intel.com) → re-enable hardware acceleration → confirm audio continues working with the updated driver.
Our guide on Chrome hardware acceleration settings covers the full GPU-related configuration, and our Chrome site permissions management covers the full permissions picture including sound. For Windows audio troubleshooting that extends beyond Chrome, Microsoft’s Windows audio documentation covers the system-level audio routing and Volume Mixer architecture.
Extensions interfering with audio
Ad blockers that block audio elements, content modification extensions that strip media from pages, and some privacy tools that intercept JavaScript can all prevent audio from playing. Test: disable all extensions → reload the silent page → test audio. If sound returns: an extension was blocking it. Re-enable extensions one at a time to find which.
uBlock Origin in aggressive mode, Privacy Badger, and some corporate security extensions have been known to block audio players as part of broader JavaScript or media element blocking. The extension’s own settings usually allow whitelisting specific sites while keeping protection active elsewhere.
Chrome audio and Bluetooth headsets
Bluetooth headsets have their own audio profile complication: A2DP (stereo music, high quality) and HFP (hands-free phone, lower quality). When a microphone-using application (video call, web app with microphone access) is active: Windows switches the Bluetooth audio to HFP profile, which sometimes causes audio quality to drop dramatically or audio to cut out in Chrome specifically.
Signs: audio works in Chrome without microphone-using apps open, but breaks when Zoom or Teams is also running. Fix: ensure the video call app’s microphone is set to a non-Bluetooth audio device (like the laptop’s built-in microphone) while Bluetooth headphones handle audio output only. This keeps the headset in A2DP mode rather than being forced to HFP for the microphone.
| Audio symptom | First place to check |
| No sound in Chrome, other apps work | Volume Mixer → Chrome’s slider/mute |
| One tab silent, others work | Right-click tab → Unmute tab |
| All sites silent, recently changed settings | chrome://settings/content/sound → default setting |
| Sound works, but wrong device playing it | Windows Volume Mixer → Chrome audio output device |
| Works without extensions, breaks with them | Disable extensions one at a time |
| Works with hardware acceleration off | Update GPU driver; re-enable acceleration |
Chrome audio problems almost always live in one of three places: Windows audio routing (Volume Mixer), Chrome’s own permissions (sound settings, tab mute), or an extension conflict. The Volume Mixer check takes 30 seconds and resolves the most common case. The tab mute check takes another 10. These two things together fix audio for the majority of users before they need to dig into permissions or extensions.
Autoplay and audio policies
Chrome blocks autoplay audio by default — sites can’t start playing sound without user interaction. This is a feature (it prevents obnoxious auto-playing ads) but can feel like a bug when you expect a page to start playing audio immediately. A subtle muted speaker icon appears in the tab when Chrome has blocked autoplay audio.
To allow autoplay audio on specific sites: lock icon in the address bar → Sound → Allow. Or at chrome://settings/content/sound → add the site to the “Allowed to play sound” list. Global setting change: if you prefer all sites to be able to autoplay: chrome://settings/content/sound → change from “Sites can play sound” to explicitly allowing — though Chrome’s current default actually allows sound with user interaction, which is the right balance for most users.
Web Audio API and JavaScript audio
Some sites generate audio through the Web Audio API rather than HTML audio/video elements. This is common in browser-based games, music creation tools, and interactive audio experiences. If a site uses Web Audio API: disabling JavaScript (never do this — it breaks most sites) or having a very aggressive content blocker can silence Web Audio API generated sounds even when standard audio from the same site works fine.
Test: open the site in an Incognito window with all extensions disabled. If Web Audio API sounds work there: an extension is blocking the JavaScript that generates the audio. The extension causing this is likely something that blocks or restricts JavaScript execution rather than a standard audio control.
Audio after Windows Update
Windows updates occasionally change how audio is routed between applications or install new audio drivers that change device names or routing. If Chrome audio stopped working after a Windows Update: check if the audio device is still correctly configured in the Windows Volume Mixer and whether Chrome’s assigned audio output still points to the right device.
A Windows Update that changed the default audio device (or added a new one and made it default) means Chrome may be sending audio to a device that’s no longer your primary output. Opening Volume Mixer and explicitly setting Chrome’s output device resolves this without any Chrome-specific changes.
Audio and virtual audio devices
Virtual audio devices (installed by tools like OBS, Discord’s audio processing, VoiceMeeter, or meeting software like Zoom) sometimes appear as audio output options in Chrome. If Chrome accidentally got assigned a virtual audio device that isn’t connected to any real speakers or headphones: audio goes nowhere.
Windows Volume Mixer → find Chrome → check which audio output is assigned. If it shows a virtual device name rather than your actual speakers/headphones: change it to the correct physical output. Virtual audio devices are useful for routing audio between applications, but Chrome assigned to one unexpectedly produces complete silence from the user’s perspective while technically “playing” audio correctly.
Chrome audio on Linux and macOS
On Linux: Chrome uses PulseAudio or PipeWire for audio. If Chrome produces no audio while other applications work: check PulseAudio volume settings (pavucontrol) → Chrome should appear in the “Playback” tab with its own volume slider — the same Volume Mixer concept as Windows, but accessed differently. Ensure Chrome’s level is non-zero and it’s outputting to the correct sink (audio output device).
On macOS: chrome audio issues are less common because macOS handles audio routing more centrally. If Chrome is silent on macOS: check System Preferences → Sound → Output → confirm the correct device is selected. The per-application audio level control in macOS is less granular than Windows’ Volume Mixer. Most Chrome audio issues on macOS trace to the site permission level (sound blocked for that site) rather than system routing.
The practical conclusion for Chrome audio troubleshooting: most issues are at the Windows routing level (Volume Mixer, device assignment) or at Chrome’s permission level (tab muted, site sound blocked). The GPU driver path and extension conflict paths exist but affect a minority of users. Working outward from the Volume Mixer check is the right starting approach, and it’s accurate often enough that most users won’t need to go further.
Checking Chrome’s audio pipeline directly
For technical users who want to confirm Chrome’s audio state: chrome://media-internals shows active media sessions in Chrome — every video, audio element, and WebRTC stream currently in any tab. Open a page with audio, then visit chrome://media-internals → you should see an entry for that tab’s audio. Click the entry → see detailed information including the audio output device, codec, bitrate, and error state.
If an entry shows an error state while audio is silent: the error message indicates whether the problem is device-level (can’t access output device), permission-level (blocked), or decoding-level (codec issue). This is the deepest non-developer diagnostic available for Chrome audio, and it produces unambiguous evidence of where in the audio pipeline the failure is occurring.
For most everyday audio problems: the Volume Mixer slider and the tab mute indicator are all you need. For stubborn cases that survive those checks: chrome://media-internals points directly at the remaining cause without additional guesswork.
One note on audio debugging that saves time: if audio works in other browsers (Edge, Firefox) but not Chrome on the same system — the issue is specifically Chrome’s configuration, not Windows audio. If audio doesn’t work in any browser: it’s a Windows audio routing issue. This cross-browser test takes 60 seconds and immediately tells you whether to focus on Chrome settings or on Windows settings, which points you to the right fix without working through both unnecessarily. Related: Chrome Cast.
And for completeness: if you’re troubleshooting Chrome audio in a video call specifically (Zoom, Teams, Meet in browser) and the other party can’t hear you: that’s a microphone permission issue, not a sound output issue. These guides address different systems — the microphone path requires checking chrome://settings/content/microphone permissions and the meeting app’s own audio device settings, rather than the Volume Mixer which controls what you hear rather than what you transmit. If this sounds familiar, Fix Chrome Sync Not Working is worth a look.
