Chrome Site Permissions: Review Camera, Microphone, and Location

Cybersecurity & Privacy / Browser controls / Desktop guide

To review a website’s camera, microphone, or location access in desktop Chrome, open the site, select the site-information control beside its address, and choose Site settings. Change only the permission you need. If a trusted calling site still cannot use a device, check the computer’s app permissions and the selected camera or microphone too.

A permission prompt is a decision about a particular feature, not a reason to grant every request. The useful question is whether that feature is necessary for what you are doing on that site now.

This guide covers desktop Chrome on Windows and Mac. Official Google, Microsoft, and Apple documentation was checked on 27 October 2026. Labels can vary by release and managed-device policy; phone and tablet menus differ.

Site access and computer app access are separate checks

Think of the website, the browser application, and the calling service as separate places to inspect. A setting that looks correct at one layer does not establish that the whole path is working.

This is a troubleshooting map, not a guarantee about every application’s implementation. For example, a hypothetical user may allow a meeting website’s microphone request but still have the headset muted. Repeatedly changing the website’s permission would not address that mute switch.

Browser extensions are another review area. Our browser-extension permissions guide covers installed add-ons. Keep that separate from granting a website access to a camera or microphone.

Review a specific site before changing global defaults

For one troublesome or unfamiliar website, start with its own setting. Google’s site-permission guide explains that a site can have settings that override the general default.

1. Open the intended website and check its address.
2. Select the site-information control to the left of the address.
3. Open Site settings.
4. Find the relevant permission and change that setting.
5. Return to the site and retry the specific feature, reloading if prompted.

Do not use an unrelated permission change as an experiment. If a meeting needs a microphone, that does not explain a separate request for location. Keep the change narrow enough that you can identify what helped.

For an audit, open Chrome Settings → Privacy and security → Site settings. Google’s camera and microphone documentation describes reviewing allowed and blocked sites within those categories and removing an existing exception.

Check the site names, not just familiar branding on the page. If an entry is unexpected, write down the address before making a decision. You can then compare it with the service’s official address without relying on memory.

Match access duration to the task

When prompted, read the access duration as well as the feature name. Decide whether you need a one-off grant, recurring access, or no access.

The Chrome developer explanation of one-time permissions discusses temporary access for geolocation, camera, and microphone. A temporary choice is useful when you need a feature for one task without deciding now that future visits should have the same access.

Choose based on the workflow:

• One-off task: consider temporary access when offered and necessary.
• Regular calling service: decide whether recurring access is justified, then review it when your use changes.
• Unrelated request: decline and check whether the intended task works without it.
• Unclear purpose: pause and inspect the service’s explanation before granting access.

These are decision examples, not instructions to trust a site because it offers a convenient permission option. A familiar-looking prompt still needs a meaningful connection to the feature you chose to use.

If the site asks again later, inspect the current setting rather than assuming a fault. The earlier choice may have been temporary. Avoid switching to longer-lived access merely to make a prompt disappear.

Location should have a clear purpose

Google’s desktop location guide says Chrome asks by default when a site wants location access. It recommends checking the site’s privacy policy before allowing it.

A useful decision starts with the task. Finding nearby collection points might benefit from a location estimate. Reading a product manual usually gives you less reason to supply one. Where a service offers a postcode, town, or address field, consider whether that is sufficient for your needs.

Google explains that, when allowed, Chrome can use Google Location Services to estimate your location and share that information with the requesting site. Do not treat a successful location permission as a promise of an exact position.

You can review the category under Site settings → Location. If Chrome reports that location is disabled in Windows or Mac preferences, Google directs you to System settings and the on-screen instructions. First decide whether you want the feature; a prompt to enable it is not an obligation.

For sensitive tasks, think about what you deliberately type into the service as well. Declining a browser permission is not a substitute for reviewing the address or other information you submit yourself.

Check the computer when Chrome’s permission looks correct

Windows 11

Microsoft’s camera and microphone privacy guidance puts the controls under Start → Settings → Privacy & security → Camera or Microphone. Desktop apps have different controls from individually listed Microsoft Store apps; the relevant desktop-app access setting may apply to a group rather than offering a separate Chrome toggle.

Read the setting before changing it, because the effect may extend beyond the browser. Microsoft also documents limitations and exceptions for desktop apps. These controls should not be treated as a complete inventory of everything an installed program can access.

Mac

Apple documents camera app access under System Settings → Privacy & Security → Camera. The equivalent Microphone panel controls microphone access for apps in its list. Review the browser’s entry and follow any restart instructions presented.

On a work or school computer, stop if a control is managed or unavailable. Google notes that administrators can configure Chrome camera and microphone settings. Ask the responsible administrator about the required service rather than trying to bypass the organization’s configuration.

Verify one feature at a time before the real call

Use a service’s preview or test screen when available, before joining a conversation that matters. Keep private documents and background conversations out of the test. The procedure below is a suggested checklist, not a claim of hands-on testing.

Google’s camera and microphone guide also explains choosing a default device in Chrome’s corresponding permission category. If the browser and calling service each expose a selector, compare both with the hardware you intend to use.

Change one thing, retry, and note the outcome. If a camera preview returns after reconnecting a webcam, do not leave unrelated permission experiments enabled. Restore those choices to the state you intended.

When testing is complete, end the test session. Review any new grant you made only for troubleshooting and decide whether it should remain.

Review old grants and use reset deliberately

Google’s site-settings instructions describe a Reset permissions button where available. Read this as a way to reset changed preferences for that site, not as an instruction to reset the entire browser for a single issue.

Before resetting, note your intended choices. Afterwards, check the resulting state instead of assuming every feature is blocked.

Chrome also removes permissions from sites that have not been used recently, as Google’s Safety Check explanation describes. That is useful housekeeping, but it does not replace your own review of an actively used site.

• Recognize the site and have a current reason for its access.
• Keep temporary access temporary when that matches the task.
• Check camera, microphone, and location separately.
• Record the change that solved a problem and undo unrelated experiments.
• Review saved grants after changing services or finishing a one-off task.

Do not treat revoking access as a data-deletion request. If you want information removed from a service, review its account and privacy tools separately. Permission management is one part of managing the relationship with that website.

Frequently asked questions