A browser permission is a deliberate choice
A website does not receive camera access simply because it contains a video feature. The browser asks when the page calls for media input, and you decide whether to allow it. 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.
Before responding to a prompt, check the site address and the reason for the request. Gesture Synth asks for video only when you choose hand tracking. It uses that input to estimate hand position and finger count locally in the browser; you can instead use keyboard mode if you do not want to provide camera input.
Read the Chrome-specific steps →Use keyboard mode instead →Review camera permission basics →
Use a simple permission decision tree
First, decide whether you want the camera feature now. If yes, allow the specific site after checking its address. If no, choose Block or leave the feature unused. There is no need to grant a camera just because a page offers one. A clear alternate input method is a sign that you can choose based on your setting rather than pressure.
Second, observe what happens after the request. A visible preview with poor gesture recognition is a framing or lighting problem. A black preview or no device is more likely a permission, operating-system, or competing-app problem. This distinction prevents unnecessary changes to the wrong setting.
- Confirm you are on the intended HTTPS site.
- Start the feature that needs a camera and read the browser prompt.
- Choose Allow only for the camera use you want at that moment.
- If the feature fails, inspect the browser site setting before changing lighting or gestures.
- Check device privacy controls and close apps that may be using the camera.
Change a blocked decision without clearing everything
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.
Check the physical camera before blaming the page
A webcam can be unavailable because another app owns it, a privacy shutter is closed, a removable camera is disconnected, or the operating system has denied the browser. Close video meetings and capture tools, then test again. If appropriate, test the camera with a trusted local system app to see whether the device itself is available.
Do not accept a random browser extension or download just to fix a prompt. Permission problems are usually solved through the browser, operating system, or camera connection. Keeping the troubleshooting path simple also limits the chance of installing unwanted software.
Prepare the camera for hand tracking →Troubleshoot missing or laggy tracking →Learn what camera frames are used for →
Keep the choice reversible
You can revoke a camera permission after a session from browser site controls or broader browser settings. Reversibility matters on shared devices and when you are testing a new service. A trustworthy guide should make that path as visible as the Allow path.
Gesture Synth remains useful after you revoke video access because keyboard mode keeps the same guided musical structure. Use that route when privacy, lighting, device performance, or the room around you makes a camera session impractical.
Read the privacy policy →Make music with a keyboard →Open the player →