← Back to Blog Chrome Audio Not Working? Find the Cause Before Resetting
· Updated · 3 min read

Chrome Audio Not Working? Find the Cause Before Resetting

Fix Chrome with no sound by checking the player, site permission, app mixer, output device and extensions. Follow a diagnosis that preserves your browser data.

chrometroubleshootingaudiobrowser

Quick answer

If Chrome has no sound, start playback manually and check the player's mute button, Chrome's site sound permission, and the operating system's output device and app volume. Compare a second site and another app before changing extensions or browser settings. A volume booster cannot repair a muted or missing audio signal.

Silence and low volume need different fixes. If you can already hear the recording, use the quiet browser audio checklist. If there is no sound, first find where playback stops. Keep the device volume comfortable: audio can return suddenly when you unmute the right control.

Is the problem one video, one site, Chrome, or the device?

Try a second recording on the same site, another site in Chrome, and audio in another app. Keep the output device unchanged. This comparison helps choose the next check; it does not prove a single cause.

What you observeCheck next
One recording is silent; others workIts player mute, audio track and source recording
Every recording on one site is silentSite sound permission, player settings and site-specific extensions
Several Chrome sites are silent; another app worksChrome’s app volume, output routing and extensions
Other apps are also silentDevice connection, system output and operating-system audio support
Sound disappears only when an enhancer startsStop capture, test original playback, then check the extension

1. Start playback and check the player

Click the actual Play button, then unmute the player’s speaker control. A moving video does not establish that its audio is enabled. Check whether the selected recording has an alternate audio track.

Chrome’s autoplay policy can prevent playback with sound before an interaction. Starting media explicitly is a useful first check. Allowing a site to play sound is a separate permission; it is not a universal override for every autoplay restriction.

2. Check the site’s sound permission

In Chrome Settings, open Privacy and security → Site settings → Additional content settings → Sound. Check the default and any exception for the affected site. You can also inspect the site’s permissions from the controls beside its address. Menu wording may vary by Chrome version.

Google’s sound-permission instructions describe whether a site may play sound. This screen is not a general output-device mixer. Choose speakers or headphones in the operating system, or in the specific app if it exposes an output selector.

3. Check the app level and output device

Windows 11: open Settings → System → Sound → Volume mixer while media is playing. Check Chrome’s mute state and app level, as well as the selected output. A normal system slider does not rule out a muted application. See Microsoft’s audio troubleshooting.

Mac: open System Settings → Sound → Output and select the device you intend to hear. Check its volume and mute state where available. Apple notes that controls depend on the output device. If you use a separate routing or mixing utility, inspect its Chrome settings too.

An HDMI display, Bluetooth headset or USB interface can be selected even when you expect the laptop speakers. Re-test after changing the route.

4. Stop audio capture and isolate extensions

If sound vanished when an audio extension started, stop its processing and reload the test page. Chrome’s tabCapture documentation explains that capture suppresses the tab’s original output; the extension must route captured audio back to an output. A failed capture or output path can therefore produce silence.

For other extension problems, record which extensions are enabled, temporarily disable the relevant ones through Chrome’s extension manager, and re-enable them one at a time. Start with tools that alter the affected page or its playback.

An Incognito comparison can help, but it is not conclusive. Extensions allowed in Incognito can still run there, and cookies, sign-in state and site behavior differ. Google’s playback troubleshooting uses this as an isolation step.

5. Escalate without deleting your profile

Save unfinished work, update Chrome and restart it. If only one site still fails, follow that site’s playback support. Clearing that site’s data may sign you out or remove local preferences and unsynced work, so review what will be removed first.

If other applications also fail, use the operating system’s audio troubleshooter or device manufacturer’s support. Avoid copying obsolete experimental flags or deleting Chrome’s user-data folder as a routine audio fix. A complete reset affects more than sound and should come after the narrower checks.

What if sound returns but is too quiet?

Now compare the same passage at a comfortable device level. The Chrome volume booster guide explains when extra gain is useful. Hearably Free offers up to 120% gain and grouped three-band EQ; Pro offers up to 800% and ten-band EQ. Higher gain can expose distortion and cannot fix a disconnected output or inaccessible playback.

If you need to process a desktop app instead, use the browser versus desktop comparison.

Sources and scope

Reviewed September 20, 2026 against Google, Microsoft and Apple documentation. This is a diagnostic workflow, not a claim that every fix was tested on every device. Hearably makes the extension discussed in the final section.

Try Hearably for free

Try up to 120% volume and a 3-band EQ on a supported browser tab. Additional controls are available with Pro.

Add to Chrome — Free