Browser Feature Detector
Browser Feature Detector does my browser support webassembly web platform compatibility test detect browser APIsDetection runs locally and checks whether selected browser interfaces are exposed. It does not request access to location, notifications, or the clipboard.
| Feature | Status |
|---|---|
| Select the button to run checks. | |
Read an availability snapshot
Select Check browser features. Supported means the relevant global, method, or test context exists on this page. Not detected means this simple check could not find it; neither status guarantees a specific site's implementation will work.
Features included
The snapshot checks JavaScript modules, WebAssembly, WebGL 2, Web Crypto, local storage, IndexedDB, service workers, notifications, geolocation, and the async clipboard interface. These represent computation, graphics, storage, background capability, and permission-gated APIs often useful in troubleshooting.
Availability is not permission
An interface can exist while access is denied. Geolocation, notifications, and clipboard operations may require a secure context, a user gesture, an explicit permission choice, browser policy, and the right top-level context. This detector deliberately avoids prompting.
Worked example
If Geolocation says Supported, the browser exposes navigator.geolocation here. A map can still fail when location permission is blocked. If Service workers say Not detected on an insecure page, the same browser may support them on an HTTPS site.
How detection works
Most rows use direct feature detection instead of guessing from the user-agent string. WebGL 2 creates a temporary canvas and asks for a context. Local storage writes and removes one temporary value because merely finding the property does not show that storage is usable in the current context.
Troubleshooting differences
Browser version, operating system, secure transport, private mode, extensions, enterprise controls, experimental flags, embedded frames, and hardware can change results. Re-run the check in the same context where a problem occurs. A support table for another version is not a substitute for testing the actual visitor environment.
Limitations and privacy
The page does not inventory every web API, test standards conformance, benchmark performance, request permissions, identify polyfills, or send the matrix elsewhere. The temporary local-storage key is removed immediately. Future browser updates can change results.
Feature Detector FAQ
Does Supported mean a website can use my location?
No. Permission and context rules still apply.
Why can a feature be missing only in private mode?
Privacy modes may restrict storage or other capabilities.
Does this identify my browser?
No. Use What Is My User Agent for the browser-provided user-agent value.