Why does a browser feature need a click first?

You open a page and a feature does nothing until you click or tap. Sound may not start, a full-screen view may be blocked, or a file picker may not appear. This can be normal browser security behavior, not a broken device.

Check what your browser supports and whether permissions are allowed with Browser Info. Then try the feature from a direct click and use the results below to narrow down what is stopping it.

Check the feature in your browser

1. Open Browser Info and look at the browser version, engine, permissions, and supported features. This helps you spot an outdated browser or a feature it does not offer.
2. Open the page that has the problem in a regular browser tab, rather than inside an email preview, another app, or an embedded frame.
3. Click the page's own control for the feature. For example, click its play control to start audio, or its full-screen control to expand the page. Do not rely on the feature starting automatically as the page loads.
4. If the browser asks for permission, allow it if you trust the site and the feature needs that access. Then try the control again.
5. Repeat the test in another up-to-date browser that supports the feature. If it works there, the difference is likely in browser support, permissions, or settings.

Browser Info can report support and permission details, but it cannot tell whether a particular page has correctly connected its feature to a click. The page's own behavior still matters.

What the result means

The feature works after you click

The browser is probably requiring a user action before it allows the feature. A click or tap gives the page temporary permission to begin certain actions. This is often called user activation. Browsers use it to stop pages from unexpectedly playing sound, opening pop-ups, or taking over the screen.

Browser Info reports that support is missing

The browser may not provide the required feature, or it may provide it only in limited circumstances. Try an updated browser that supports it. If the feature is part of a website or app, check its help information for supported browsers and devices.

The browser asks for permission, or permission is blocked

Permission and user activation are separate checks. A click may let a site request camera or microphone access, but the browser can still deny that access if you previously blocked it. Allow only the permissions needed for the feature.

A click makes no difference

The page may be trying to start the action too late, after a delay or another task. Some browser permissions also depend on whether the page is embedded in another site. The problem may be in the page's code or in a browser setting, rather than the hardware.

It works in a regular tab but not in an embedded page

An embedded frame can have extra restrictions. The site containing it may need to grant the frame access to a feature, and the click may need to happen inside that frame. The person viewing the page often cannot change those rules, so report the difference to the site owner.

How to fix it

1. Click the page's own control. Start the feature with a direct click or tap, and try it again if the page took a long time to load. A click somewhere else on the page may not count as permission to start a specific action.
2. Allow the needed site permission. Select the site controls next to the address bar and check the setting for the feature, such as Microphone or Camera. Set it to allow access, reload the page, and try again. The exact control name varies by browser.
3. Check system access for a camera or microphone. In Windows 11, open Settings › Privacy & security › Microphone or Settings › Privacy & security › Camera, then allow access for the browser. On macOS, open System Settings › Privacy & Security › Microphone or System Settings › Privacy & Security › Camera and allow your browser. On Android, check Settings › Apps › [your browser] › Permissions. On iPhone or iPad, check Settings › Privacy & Security › Microphone or Settings › Privacy & Security › Camera.
4. Open the page outside an embedded preview. Copy its address into a new browser tab. If the feature works there, the original frame or app may be restricting it.
5. Update the browser and reload the page. An older browser may lack an API, meaning a feature interface that websites use, or may have a bug that has since been fixed.
6. Try another supported browser. If the feature still fails after you allow permission and click its control, compare it in another current browser. If only one page fails, contact that page's support team and tell them which browser and feature you tested.

Why a click can matter even when permission is allowed

A permission prompt answers, “May this site use the camera?” User activation answers, “Did the person just ask for this action?” A site can have permission and still need a click to start sound, enter full screen, open a file picker, or show a pop-up.

The click also needs to be connected closely to the action. If a page waits for a network request, timer, or other task before it tries to start audio or open a window, the browser may no longer treat the action as part of the click. This is especially relevant to website developers. As a visitor, try the page's own control again and report if the feature only works after a particular sequence of clicks.

For sound that will not start until you interact with the page, see why autoplay with sound fails in some browsers.