Remove an old website's Chrome camera and microphone access

A site allowed to use your camera or microphone can request them while you are on that site. A past meeting or support session may leave a remembered permission that is no longer needed. Chrome lets you review allowed and blocked origins separately for Camera and Microphone, and some prompts offer one-time access. Removing one site's exception is more precise than disabling all cameras at the operating-system level.

Before you start​

Identify the exact website you trust for upcoming calls and any old origins you no longer use. Do not use a call link from an unexpected message to test permissions. Have a harmless test call or device preview ready, and know that a work or school administrator may control some settings. Check whether a separate desktop app, not Chrome, is using the sensor.

Do it step by step​

1. From Chrome's menu, select Settings, then find Camera under Privacy and security, Site settings. Review the allowed and blocked website lists, looking for old meeting services and unexpected spellings.
2. Remove permission for an obsolete or suspicious origin. Repeat under Microphone; changing one sensor does not necessarily change the other.
3. For a trusted meeting site, decide whether Allow this time or Allow while visiting better matches your needs when Chrome asks again. Avoid blanket permission for unrelated sites.
4. Open the legitimate meeting site's device preview and confirm the chosen camera and microphone. If it cannot connect, inspect the site's Chrome permission before changing every system privacy control.
5. Check the operating-system camera and microphone privacy settings if Chrome cannot reach the hardware. Select the correct input devices in Chrome and the meeting service, and check the headset's physical mute switch.
6. After the call, revisit Site settings and remove the exception if it was temporary work. Note the trusted origin so a lookalike domain cannot be justified as a normal permission later.

Check the result​

Only current trusted meeting sites appear in Chrome's allowed sensor lists. A test call works when you grant the intended permission, and an obsolete site must ask again or is blocked.

If something goes wrong​

If the site is managed by an organization, ask the admin instead of editing hidden policies. If camera access fails despite Chrome permission, inspect OS settings, device selection, physical privacy shutter and other apps holding the sensor. A blank preview is not automatically a privacy breach.

Know the limit​

Removing a browser permission does not revoke a desktop app's permission or erase recordings a site already made. A camera indicator shows current use, not every possible future use. A permission granted to one origin should not be generalized to a similar-looking domain; verify the address before accepting a fresh prompt. Chrome camera and microphone Chrome site settings