Check status of all browser permissions including camera, microphone, geolocation, notifications, and more. Test permission requests, verify permission states, and troubleshoot permission-related issues. Essential for web apps that require device access.
Modern browsers implement a permission system to protect user privacy. Permissions can be in three states: granted, denied, or prompt (ask user). Some permissions like camera and microphone require secure contexts (HTTPS) to function. This tester helps you understand and manage your browser permissions.
Start with the live tester below. Supporting details, FAQs, and troubleshooting guidance are placed after the tool so the main action is easier to find and use immediately.
Check status of all browser permissions and request access if needed.
Common problems
If the live tester does not behave as expected, these are the first checks most users should try before assuming the hardware is broken.
Check all permission types
Test permission requests
Verify permission states
Check secure context requirements
Check status of all browser permissions including camera, microphone, geolocation, notifications, and more. Test permission requests, verify permission states, and troubleshoot permission-related issues. Essential for web apps that require device access.
Modern browsers implement a permission system to protect user privacy. Permissions can be in three states: granted, denied, or prompt (ask user). Some permissions like camera and microphone require secure contexts (HTTPS) to function. This tester helps you understand and manage your browser permissions.
Test your keyboard input, detect dead keys, and verify all keys are working correctly.
Test mouse buttons, scroll wheel, pointer tracking, and touch input.
Test your microphone input levels in real-time. Verify microphone is working.
Test your speakers or headphones with reference tones.
Helpful questions
Use these answers to understand results, browser limitations, permissions, and sensible next troubleshooting steps.
When a permission has already been denied, many browsers remember that choice for the site and keep returning the same blocked state until you change it manually in site settings. Reloading alone often does not reset the permission decision.
Sensitive capabilities such as camera, microphone, and in many cases geolocation generally require a secure context. If a permission test behaves differently between local development, HTTP, and HTTPS, the security context is one of the first things to check.
It helps separate permission state from device state. If the permission is denied or still prompting, the app cannot use the device yet. If permission is granted but the device still fails, the next likely causes are browser device selection, operating system privacy settings, or hardware problems.