Chrome Audio Not Working? 12 Proven Fixes (2026)

Chrome handles audio differently than other browsers. It routes all audio through its own internal mixer, applies per-tab volume policies, enforces autoplay restrictions, and manages audio device connections independently of the operating system. When any part of this chain breaks, you get silence.

Here are 12 fixes, ordered from fastest to most involved. Start at the top and work down.

Fix 1: Check If the Tab Is Muted

Look at the tab title bar. If you see a speaker icon with a line through it, the tab is muted.

How to unmute: Right-click the tab and select “Unmute Site.” Note that Chrome mutes at the site level, not the tab level — so muting one YouTube tab mutes all YouTube tabs.

Check the site list: Go to chrome://settings/content/sound. Sites can be added to a permanent “Muted” list. If the site you are trying to hear is listed there, remove it.

Fix 2: Check System Volume and Mixer

This sounds obvious, but the volume mixer has multiple sliders, and Chrome has its own.

Windows: Right-click the taskbar speaker icon > “Open Volume Mixer.” Find Chrome in the list. It might be at zero even if your master volume is at 100%.

macOS: macOS does not have a per-app mixer natively, but check System Settings > Sound > Output. Make sure the correct output device is selected and the volume is up. If you use a third-party app like SoundSource, check Chrome’s level there.

Linux: Open PulseAudio Volume Control (pavucontrol). Check the “Playback” tab for Chrome’s audio stream.

Fix 3: Check Chrome’s Output Device

Chrome can output audio to a different device than your system default.

Go to chrome://settings/content/sound and check the “Output” dropdown. If it says “Default” but your system default is wrong, or if it points to a disconnected device (like Bluetooth headphones you turned off), that is your problem.

Fix: Set it explicitly to the device you want, or change your system default.

Fix 4: Try an Incognito Window

Open an Incognito window (Ctrl+Shift+N / Cmd+Shift+N) and navigate to the same page. If audio works in Incognito, the problem is caused by an extension or a cached setting.

This immediately narrows the diagnosis: it is not a system issue, driver issue, or Chrome bug. It is something in your profile.

Fix 5: Disable Extensions One by One

Extensions can interfere with audio in ways that are not obvious. Ad blockers can block audio elements that are embedded in ad containers. Privacy extensions can block WebRTC connections that carry audio. Some extensions inject CSS that hides media players.

Disable all extensions (chrome://extensions/), then re-enable them one at a time, testing audio after each one. The culprit is usually an ad blocker or privacy tool.

Fix 6: Clear Site Data for the Specific Site

Some websites store audio preferences in localStorage or IndexedDB. If these get corrupted, audio can fail silently.

Go to chrome://settings/content/all and find the site in question. Click on it and select “Clear data.” This resets the site’s stored preferences without affecting your bookmarks or passwords.

Fix 7: Check Chrome’s Autoplay Policy

Since Chrome 66, autoplay with audio is blocked by default on most sites. Chrome uses an internal metric called the “Media Engagement Index” (MEI) to decide which sites can autoplay audio. Sites you frequently interact with get autoplay privileges; unfamiliar sites do not.

To check: Go to chrome://media-engagement/. This shows every site’s engagement score. Sites with a score below the threshold will have autoplay blocked.

To fix for a specific site: Interact with the page first (click anywhere), then try playing the media. Alternatively, go to chrome://settings/content/sound and add the site to the “Allowed to play sound” list.

Fix 8: Reset Chrome’s Audio Flags

Chrome has internal flags that affect audio behavior. If any have been changed (intentionally or by another guide), they might be causing issues.

Go to chrome://flags/ and search for “audio.” Look for any flags that are not set to “Default.” Common problematic flags:

• #enable-audio-service-sandbox — if disabled, can cause audio routing issues
• #audio-service-out-of-process — affects how Chrome manages audio processes

Click “Reset all” at the top of the flags page to return everything to defaults, then restart Chrome.

Fix 9: Update Audio Drivers

Outdated audio drivers are a common cause of Chrome-specific audio issues, especially on Windows after a major OS update.

Windows:

1. Open Device Manager (Win+X > Device Manager).
2. Expand “Sound, video and game controllers.”
3. Right-click your audio device > “Update driver.”
4. Select “Search automatically for drivers.”
5. If no update is found, visit your audio hardware manufacturer’s website for the latest driver.

macOS: Audio drivers on macOS are managed by the system. Run Software Update to ensure you have the latest.

After updating: Restart your computer (not just Chrome). Audio drivers often require a full restart to take effect.

Fix 10: Restart the Windows Audio Service

On Windows, Chrome’s audio runs through the Windows Audio service. If this service hangs, Chrome loses audio while other applications might still work.

Open Command Prompt as Administrator and run:

net stop audiosrv
net start audiosrv

Or open Services (Win+R > services.msc), find “Windows Audio,” right-click, and select “Restart.”

Fix 11: Reset Chrome Completely

If nothing else works, reset Chrome to its default settings.

Go to chrome://settings/reset and click “Restore settings to their original defaults.”

This resets:

• Default search engine
• Homepage and startup pages
• Content settings (including sound permissions)
• Cookies and site data
• Extensions (disabled but not deleted)

It does NOT reset:

• Bookmarks
• History
• Saved passwords

After resetting, test audio before re-enabling any extensions.

Fix 12: Reinstall Chrome

The nuclear option. If Chrome’s audio is broken and nothing above fixes it, a clean reinstall can resolve corrupted binary issues.

1. Uninstall Chrome through your OS.
2. Delete the Chrome user data directory:
   • Windows: %LOCALAPPDATA%\Google\Chrome\User Data
   • macOS: ~/Library/Application Support/Google/Chrome
   • Linux: ~/.config/google-chrome
3. Download and install Chrome fresh from google.com/chrome.
4. Sign in to restore bookmarks, passwords, and extensions from your Google account.

Important: Deleting the user data directory removes everything, including local-only data that is not synced. Back up anything you need first.

The Audio Still Works but Is Too Quiet

If Chrome’s audio is working but just not loud enough, that is a different problem. Chrome limits output to 100% of the source volume — it cannot amplify. If the source content is mastered quietly (common with lectures, webinars, and older videos), 100% system volume might not be enough.

A browser audio enhancer can intercept Chrome’s audio pipeline and apply amplification beyond the 100% limit. Hearably’s extension uses a 3-band crossover with per-band compression and a look-ahead limiter to push volume up to 800% without clipping or distortion.

Diagnostic Quick Reference

Symptom	Most Likely Cause	Fix #
No sound on one site	Tab/site muted	1
No sound on any site	System mixer or output device	2, 3
Works in Incognito	Extension conflict	4, 5
Sound stopped after Chrome update	Flags reset or driver conflict	8, 9
Intermittent audio dropouts	Audio service hang or driver	10, 9
No sound after OS update	Driver update needed	9
Nothing works	Reset or reinstall Chrome	11, 12

Start with Fix 1. Most Chrome audio problems are caused by muted tabs or incorrect output devices — problems that take 10 seconds to resolve.