Check the tab's mute state, Chrome's sound permission for that site, and the operating system's volume mixer. Compare another site before changing drivers or resetting Chrome.
Why this can happen
A silent tab can be muted individually, blocked by site permission, routed to another output device, or affected by the site's own player. Chrome sound permission and system audio are separate checks.
Use this order so you can identify the cause
- Play audio and look for the speaker icon on the tab; unmute that tab if it is muted.
- Open the site's lock or tune icon > Site settings and confirm Sound is allowed for that site.
- Check Windows Volume mixer and select the intended output device; Chrome can have its own app volume.
- Test another site and another browser. If only one site fails, inspect its player mute and account settings.
- Restart Chrome and test once without a sound-control extension if the problem began after installing one.
A quick way to narrow it down
All Chrome sites silent but system audio works points toward Chrome's site permission or mixer. One site silent points to that site's player or permission; every app silent points outside Chrome.
Changes to avoid until you know the cause
Do not reset all browser data or install audio extensions before checking the tab and site. Restore any temporary permission change after the test.
Retest the original failure
Play the same site again and confirm the tab is unmuted, Chrome appears in the volume mixer, and audio comes from the expected output.
When to use support or repair
If every Chrome site remains silent after permissions and mixer checks, update Chrome and use Google Chrome Help with the OS and browser version.
Confirm the active audio path before changing drivers or apps
For microphones and cameras, permission can be granted at both the operating-system level and inside the app or browser. A correct hardware connection will still fail if either permission layer blocks access.
A device can be paired without being the active input or output. Check the selected microphone, speaker or Bluetooth profile first, then reproduce the problem in a second app so you know whether the fault follows the accessory or only one application.
Bluetooth audio adds another layer: call audio and media audio can use different profiles, and multipoint devices can silently switch to another phone or computer. Disconnect extra devices during testing.
| What you observe | What it points to | Best next check |
|---|---|---|
| Cuts out or crackles | Signal, codec, driver or hardware path | Test closer, wired, or with another known-good device |
| Works in one app only | App permission or app-specific routing | Compare permissions and selected device |
| Paired but silent | Wrong output/profile or another device took focus | Select output manually and disconnect extras |
Frequently asked questions
Should I reset the whole device immediately?
Usually not. Compare a private window and another browser first. Reset Chrome only after checking the profile, extensions and sync.
How do I know when the fix is real?
For microphones and cameras, permission can be granted at both the operating-system level and inside the app or browser. A correct hardware connection will still fail if either permission layer blocks access.