Browser Capability Test

Quick steps

• • Run the test and look for green checks on media, storage, and graphics.
• • Open any failing item to see the exact capability or error message.
• • Click the page once to allow autoplay if audio checks show blocked.
• • Rerun after changing settings so the results refresh.

If media tests fail

• • Allow mic and camera in the browser prompt or via the lock icon, then rerun.
• • Use HTTPS; media devices are blocked on insecure origins.
• • Try another browser profile without strict privacy extensions.
• • On Linux, ensure PulseAudio or PipeWire is running and devices are visible.

Enable hardware acceleration

• • Chrome or Edge: Settings > System > Use hardware acceleration when available, then relaunch.
• • Firefox: Settings > General > Performance > Use recommended performance settings, then restart.
• • If graphics drivers are outdated, update them and reboot.
• • Virtual machines may block acceleration; test on the host if possible.

Autoplay and sound

• • If audio tests show blocked, click the site info icon and allow sound, then reload.
• • Play any short sound in another tab, then return and rerun; some browsers need a user gesture first.
• • Disable autoplay-blocking extensions while testing media readiness.

Clear blocked site settings

• • Click the lock icon and reset permissions for mic, camera, and sound, then reload.
• • Chrome: Settings > Privacy and security > Site settings > View permissions and data stored across sites; search for deviceprep.com and clear overrides.
• • Firefox: Settings > Privacy & Security > Permissions to remove site exceptions.

Managed or school devices

• • IT policies can disable camera, mic, or WebRTC. If you see a policy message, contact your admin.
• • Try another profile without forced extensions if allowed.
• • If nothing works, run the test on a personal device to isolate the policy impact.

Storage and cookies

• • Allow cookies and local storage or use the standard tracking protection level while testing.
• • If storage is disabled, some tests cannot remember your device picks between runs.
• • Private browsing clears storage on close; switch to a normal window if you need persistence.

Mobile browser tips

• • Use Chrome or Safari with the latest version for the best media support.
• • Stay on Wi-Fi rather than cellular if you also plan to run the network test.
• • Keep the screen awake so capability checks complete without pausing.

Cache and restart

• • After toggling flags or permissions, close all browser windows and reopen before retesting.
• • If results seem stale, clear site data for deviceprep.com and reload.
• • On low-memory devices, restart the machine to restore GPU features disabled after a crash.

When to use this test

• • Before an interview or presentation on a new machine.
• • When video apps fail to access your camera or mic and you need to isolate browser issues.
• • Before enabling advanced effects that rely on WebGL or hardware acceleration.
• • After changing security or privacy settings that could block media APIs.

Safety and privacy

• • Capability checks run in your browser only; results are not uploaded.
• • You control mic and camera prompts; deny them if you only need capability info.
• • Use a private window to clear permissions after you finish.

Related tools