API unavailable in Safari or Chrome on Windows 11?

A website says a browser API is unavailable, or a feature works in Chrome but not Safari. The cause could be browser support, a permission, the operating system, or the way the site checks your browser.

Start by checking which browser and engine are actually running. TooLab’s Browser Info reports the browser version, engine, permissions, privacy settings, and supported features. One important detail: current Safari is not available as a supported browser for Windows 11, so a Safari label on a Windows PC does not prove that Safari is running.

Check which browser and features are available

1. Open Browser Info in the browser where the website has the problem.
2. Check the reported browser name, version, and engine. Make a note of them, then check the supported features and permissions shown by the tool.
3. Repeat the check in the other browser or device you want to compare. Keep the same network and open the same website in each one.
4. Return to the site and retry the action that needs the API. If it asks for permission, allow it and try again.

Browser Info reports the features it can inspect, but it may not list every web API. If the exact API is not shown, use the results to confirm the browser and its general capabilities, then continue with the checks below. For a broader explanation of missing browser features, see why a modern browser can still lack a required API.

What the result means

The feature is not supported in the browser

If the browser does not support the API, the site cannot use it there. This can happen when an API is new, removed, experimental, or limited to certain browser engines. Try a current version of a browser that supports it, if the site offers one. Updating will not help if that API is not supported by that browser at all.

The API is supported, but the site still reports an error

Support alone does not guarantee access. Some APIs need permission, a secure page loaded over HTTPS, a user action such as a click, or a specific device. The site may also be checking for the feature incorrectly or may have a bug.

Chrome works, but Safari does not

The browsers may use different engines and support different features. Chrome uses Chromium’s Blink engine. Safari uses WebKit. A site can also require a feature that Safari does not expose, or require a permission that was denied in Safari.

The site says Safari on a Windows 11 PC

Current Safari is not a supported Windows 11 browser. The site may be reading a changed user-agent, which is a browser-provided label, or you may be looking at a remote browser session. Changing that label does not install Safari or give Chrome Safari’s engine and capabilities. Use the browser and engine reported by Browser Info to identify the browser actually handling the page.

How to fix it

1. Update the browser. Install the latest available version, then close and reopen the browser. On Windows 11, Chrome’s update controls are in Chrome menu › Help › About Google Chrome. On macOS, check the browser’s own About screen. Safari updates through macOS updates.
2. Check the site’s permission. In Chrome, open Settings › Privacy and security › Site settings, choose the permission the API needs, and make sure the site is allowed. In Safari on a Mac, open Safari › Settings › Websites, select the relevant permission category, and review the setting for the site. A permission is only relevant when that API needs one.
3. Check operating-system access for cameras or microphones. On Windows 11, open Settings › Privacy & security › Camera or Settings › Privacy & security › Microphone and check access for apps. On macOS, open System Settings › Privacy & Security and choose Camera or Microphone. Reload the website after changing access.
4. Open the site over HTTPS. Some APIs are limited to secure contexts, meaning a protected page such as one beginning with https://. If the site is using an insecure address, try its secure version. A browser cannot make an insecure page eligible for an API that requires HTTPS.
5. Try a normal browser window. Private browsing, strict privacy settings, extensions, or a managed work policy can limit an API or its permissions. Test in a regular window with extensions temporarily disabled. If this is a work device, ask the administrator before changing managed settings.
6. Contact the website if only its page fails. If the API appears available, permissions are allowed, and the same browser works on other sites that use it, the website may be detecting support incorrectly. Include the browser version, engine, operating system, and the exact error when you report it.

Why Windows and Safari cannot be a direct comparison

To compare browser behavior fairly, test browsers that are actually available on the device. On Windows 11, compare Chrome with another supported Windows browser. To compare Safari, test it on a supported Apple device and note the Safari version and operating-system version. Browser APIs can depend on both the browser and the platform, so a result from Safari on a Mac may differ from Chrome on Windows even when both browsers are up to date.

Some APIs are also activated only after a direct user action, such as pressing a button. If a website tries to use one automatically when the page loads, the browser may block it even though it supports the API. Try the site’s own action again after clicking its control.

Browser Info checks the browser running on your device, but it cannot make an unsupported API available or diagnose the website’s code.