How to Allow Camera Access in Chrome and Other Browsers

A website does not receive camera access simply because it contains a video feature. The browser shows a permission prompt when the page requests media input, the prompt identifies the site, and the choice belongs to you. A page cannot grant itself access after you have blocked it; it must rely on your browser setting.

Modern browser media APIs are intended for secure contexts, which usually means an HTTPS page. If a page is not secure, browser camera features may be unavailable rather than silently working. For a hand-controlled instrument, camera permission should be requested when you choose to start the camera-based experience, not as a hidden background action.

A camera prompt is a request from the site currently shown in the address bar. Before choosing Allow, confirm that the domain is the one you intended to open and that the feature explains why it needs video. For Gesture Synth, the camera is used for hand tracking; the core music engine can also be used through keyboard mode without a camera.

Camera and microphone permissions are separate. Allowing video does not automatically grant microphone access. A page should request only the capability it needs, and a browser should make the request visible rather than turning on a camera silently.

Use Gesture Synth without a camera →Learn how hand tracking uses camera frames →

When a compatible page requests camera access, Chrome displays a prompt tied to that site. Choose Allow only if you want the feature to use the selected webcam. If you choose Block, Chrome remembers that decision for the site until you change it. That is expected behavior, not a failure of the page.

If the prompt never appears, do not keep refreshing. The site may already have a stored permission choice, or the camera may be unavailable. Use Chrome site controls first so you can see the current setting before changing anything else.

1. Open the intended page over HTTPS and wait for its camera request.
2. Confirm the address-bar domain before selecting Allow.
3. Select the intended camera if Chrome offers more than one device.
4. If you previously blocked the site, use the site controls beside the address bar, change Camera to Allow, then reload.

The same pattern holds in every modern browser, only the labels move. In Safari on macOS, camera requests appear as a system prompt, and per-site choices live under Safari Settings, then Websites, then Camera. Safari also asks once per browsing session for some sites, so a choice may need to be repeated after a full restart.

In Microsoft Edge, the flow mirrors Chrome: a prompt beside the address bar, site controls via the lock icon, and a broader list under Settings, then Cookies and site permissions, then Camera. In Firefox, the prompt appears near the address bar as well, and saved choices can be reviewed under Settings, then Privacy and Security, then Permissions. In all three, the rule is the same as Chrome: the page asks, you decide, and your decision can be changed later.

1. Confirm you are on the intended HTTPS site before responding to any prompt.
2. Start the feature that needs a camera and read the browser prompt.
3. Choose Allow only for the camera use you want at that moment.
4. If the feature fails, inspect the browser site setting before changing lighting or gestures.

If you clicked Block earlier, the browser normally stores that site-specific choice. Open the controls beside the address bar or the browser privacy settings, find the Camera permission for that site, change it to Allow or Ask, and reload. This is better than clearing all browsing data because it changes only the decision related to the feature you are trying to use.

The labels vary among browsers, but the pattern is consistent: site controls handle the web-page permission, while device privacy settings control whether the browser application can reach the physical camera. If the browser says it is allowed but cannot see a camera, inspect both layers.

Google Chrome Help documents a broader settings path for camera permissions: open Chrome Settings, choose Privacy and security, choose Site settings, then choose Camera. There you can select a default camera and review sites that are allowed or blocked. The exact wording can change between Chrome versions, so use the settings search if the labels differ slightly.

Remove only the exception you want to reset. Clearing every permission may be unnecessary and can sign you out or change unrelated preferences. After changing the setting, return to the page and reload so Chrome can make a fresh media request.

Chrome also needs permission from your operating system to use the physical camera. If Chrome site settings look correct but the preview is black or no camera is listed, inspect the system privacy control for Chrome and make sure camera access is enabled there. A browser cannot override a device-level privacy block.

Close video-call tools, system camera utilities, screen-recording software, and other browser tabs that may hold the webcam. A busy camera can look like a site-permission problem even when Chrome is allowed to use it. If appropriate, test the camera with a trusted local system app to see whether the device itself is available, and do not install a random browser extension just to fix a prompt—permission problems are solved through the browser, the operating system, or the camera connection.

Set up lighting and framing for hand tracking →Start a keyboard-only session →

Allowing a camera for one session does not mean you must leave it available forever. Use the same address-bar site controls or browser camera settings to block the site later. This is useful on a shared device, after a troubleshooting session, or whenever your preference changes. A trustworthy guide should make the revoke path as visible as the Allow path.

For Gesture Synth, revoking the camera does not remove the music workflow. Switch to keyboard mode and you can continue playing without video input. That separation makes it easier to make a privacy choice without losing access to the instrument entirely.

Read Gesture Synth privacy information →Play with keyboard mode →See all Guides →