Interactive diagnostic

Browser feature test

See which modern web capabilities are available in this browser and context, without requesting sensitive permissions.

Processed locally in this browser

Feature detection

Check modern web capabilities

The test checks whether browser APIs exist in this exact context. It does not request camera, microphone, notification, or clipboard permission.

19 browser capabilitiesRead-only checks · no permission prompts

Test guide

What this test proves—and what it cannot

This test inventories web-platform capabilities available in the current browser context. It distinguishes a missing feature from a permission prompt or restricted context, helping explain why one web app works in a full browser but not in private mode, an embedded view, or an older engine.

Last reviewed: 2026-09-01

Signals measured

WebGL, WebGL 2, WebGPU, and WebAssembly exposure
Service Worker, media-device, clipboard, and notification interfaces
Cookie, local-storage, and session-storage behavior
Secure-context state because several APIs require HTTPS

How the test works

Feature detection checks whether an interface exists before it is used.
Storage checks write and remove a temporary value; they do not read existing site content.
Permission-gated devices are reported as available interfaces without opening the camera or microphone.
Results apply to this browser, mode, origin, and policy—not automatically to every browser on the device.

Interpreting the results

SignalWhat it meansNext step

SupportedThe interface is exposed in this context.No change is needed unless the target site still fails.

Not supportedThe interface is absent or blocked in this context.Compare HTTPS, normal mode, a full browser, and a current version.

Permission requiredSupport may exist, but access needs a user decision.Grant access only inside the focused test that needs it.

Measurement limits

Feature presence does not prove that every website implements the feature correctly.
Enterprise policy, private browsing, extensions, and embedded browsers can change the result.
Optional APIs such as notifications should not be treated as general device-health requirements.

Missing or privacy-reduced detail is not scored as a fault by itself.

Questions about this test

Why does the same browser behave differently in private mode?

Private modes can limit persistent storage, Service Workers, history, permissions, or identifiers. A difference is often intentional privacy behavior rather than a defect.

Does missing WebGPU mean the browser is obsolete?

No. WebGPU availability still depends on browser, operating system, graphics stack, and rollout policy. Many sites continue to use WebGL.