Check modern browser feature support online across CSS layout and color, camera and microphone, screen and media APIs, pointer and gamepad input, storage, workers, sharing, and permissions.
Every check runs against this browser locally
Waiting for the first check
Results describe this browser and the current page context.
Complete tool guide
Use this browser compatibility checker to test the APIs and CSS features available in the current browser and page context, including whether HTTPS, permission state, or page policy is blocking an otherwise supported capability.
Your input is processed in the current browser tab and is not sent to the application server.
Open this page in the browser you want to check.
Review the results, grouped by what the feature is for.
Look at the permission state where one is shown.
Refresh the checks after changing a browser setting.
The summary counts capabilities available in this exact browser and page context. Refresh checks reruns feature, security, policy, and readable permission tests after you update the browser or change a site setting.
Checks CSS Grid, container queries, color-mix(), wide-gamut CSS color, and JavaScript media queries—the building blocks behind responsive layouts and modern color interfaces.
Checks camera, microphone, screen capture, MediaRecorder, Web Audio, screen orientation, and system EyeDropper support. Secure-context and policy restrictions are reported separately where relevant.
Checks Pointer Events, Pointer Lock, Gamepad, Vibration, Web Share, clipboard writing, geolocation, and device motion capabilities used by games, editors, sharing flows, and touch or sensor-based interfaces.
Checks IndexedDB, storage quota estimates, service workers, Web Workers, WebAssembly, File System Access, and Fullscreen—the browser APIs behind offline apps, background work, local files, and immersive interfaces.
The underlying feature exists and the current context passes known HTTPS, page-policy, and denied-permission checks. It does not guarantee that every advanced subfeature or connected device will work.
API unavailable means the browser does not expose the tested interface. Requires HTTPS means the feature may exist but browsers refuse to expose it on an insecure page.
Policy blocked means this page is not allowed to use the feature. Permission denied means the browser has a stored refusal for this site; change site permissions, then refresh the checks.
Granted, denied, or prompt reflects an existing readable permission state. Query unavailable or cannot be queried means the browser withholds that status; the checker never opens a new permission prompt.
A feature is marked available only when the browser exposes it, the page is on a secure connection where one is required, the page policy allows it, and no permission has been denied.
The checker reads existing permission states where the browser allows it. It never requests camera, microphone, location, or clipboard access, so no prompts appear.
A site can restrict which features its own pages may use. A feature marked as blocked by page policy works in your browser but is switched off for this page.
Update your browser first, since support usually arrives with a new version. If it still shows as unsupported, that feature has not shipped in this browser and a different browser will be needed.
Those features need your explicit consent. The state shown is what the browser has already recorded for this site — granted, denied, or not yet asked.
No. Every check runs locally in this tab and the results are only displayed to you.
Keep working
Continue with another focused tool from the same collection.