How to Allow Microphone Permission in Chrome
Chrome needs permission at both the website level and the operating-system level before a page can use a microphone. If you previously chose Block, Chrome may stop showing the prompt until you change the site setting.
Test Chrome Microphone Access →Common causes
A blocked site permission, a global Chrome microphone setting, an operating-system privacy switch, an outdated tab that has not reloaded, or the wrong default input can all look like the same problem. Managed work or school devices may also enforce a policy you cannot change locally.
Recover access, then check the signal
Before changing permission, connect a real microphone and check its mute switch. An input name such as Realtek can exist without a connected physical microphone. This page has no microphone-device selector; choose the intended input in your operating system or browser settings.
- Open Microphone Test and choose Start test. If Chrome asks, allow this trusted site. Wait for the short background-measurement message to change before speaking.
- If access is blocked, open the site controls beside Chrome's address bar. Review this site's Microphone permission, change it only if you intend to allow access, then reload the test. Chrome's wording varies by version. If the control is absent, open Chrome Settings → Privacy and security → Site settings → Microphone. Review the default input and whether sites may ask. A managed setting may require your administrator; do not bypass it.
- Return to the test and choose Start test or Retest. Speak normally for about 3 seconds. A changing input level and waveform show that audio is reaching the browser; no fixed percentage is a pass threshold.
- Choose Record sample, speak briefly, then Stop recording. Use the local audio player's play control to review the sample. Do not report physical playback verified unless you actually hear it.
- Choose Stop test when finished. Retest begins a fresh check and clears the prior temporary recording. Revoke this site's permission afterward if desired.
If Chrome is allowed but access is still blocked
Windows 11
Open Start → Settings → Privacy & security → Microphone. Review Microphone access and Let apps access your microphone. For desktop Chrome, also review Let desktop apps access your microphone; Chrome may not have an individual app switch. Only enable access if you intend to use the microphone. Return to Chrome, reload the test and choose Retest.
Windows 10
Open Start → Settings → Privacy → Microphone. Review device access, app access and Allow desktop apps to access your microphone. The labels differ from Windows 11. Organization-managed controls may need your administrator.
macOS with System Settings
Open Apple menu → System Settings → Privacy & Security → Microphone. Review access for Google Chrome if it is listed. Follow any macOS prompt to reopen Chrome, then return to this site and retest. OS app access and Chrome's permission for this website are separate. If Chrome is not listed or the setting is locked, consult the official help or your administrator rather than changing unrelated permissions.
Menu names vary by OS language/version. These paths were checked against Microsoft's Windows microphone guide and Apple's Mac microphone guide. They are not a claim that every OS configuration was tested.
Example: permission is not the same as a working microphone
In a controlled Chromium test, synthetic audio can open a stream, move the level and produce a decodable recording. That verifies the software path only. On your device, Allow followed by a flat meter is still an unresolved input problem, not proof of a broken microphone. The 3-second interval above is simply a short observation period, not an audio-quality measurement.
What did you see? Do this next
- Permission denied
- Review this website's Chrome permission and the OS path above. Reload, then choose Retest. If an organization locks the setting, ask its administrator.
- No compatible input
- Connect a real microphone and check the OS input list. Permission changes cannot create a missing device.
- Input opens but the level stays flat
- Check mute, cable and selected OS input. Try a known working input. This result alone does not establish hardware failure.
- Level changes and recording plays
- The browser input and local playback path are working for this check. Stop test when done; test the microphone separately inside your meeting app if that is where it fails.
- Level changes but recording is unavailable
- Live input can work without recording support. Try a current supported browser; do not report playback success without a recording.
FAQ
Why does Allow still lead to an error?
Site permission is one layer. OS privacy, managed policy, device availability or another application can prevent access. Follow the displayed error rather than repeatedly changing unrelated settings.
Should I allow every site?
No. Limit changes to the site you trust. The tool cannot override Chrome or OS permission controls.
What the browser test can confirm
The microphone test can show whether permission now results in a live browser audio track and a changing input level. It cannot override organization policy, unlock an operating-system privacy restriction, or prove that Chrome will use the same input in every meeting application.
Limits and privacy
Grant access only to sites you trust. You can revoke this site permission after testing; Device Check does not upload test audio.
A successful browser result means the expected event or stream reached this page during the test. It is useful evidence, but it is not a repair, calibration, warranty, or manufacturer certification.
Related guides
Ready to verify the result?
Run the relevant Device Check tool after completing the steps above.
Test Chrome Microphone Access →