Permissions
Browser permissions checker online. Check camera, microphone, location, notification permissions. See what browser has access to—free tool.
Features
- Check camera and microphone permission status
- View location and notification permissions
- Test clipboard, geolocation, and sensor access
- Request permissions directly from the tool
- See permission state (granted, denied, prompt)
- Privacy-focused permission management
Common Use Cases
- Debug why an app can't access camera
- Check if location permission is granted
- Verify notification permissions before sending
- Test permission prompts in your web app
- Audit browser permissions for privacy review
Browser Permissions API Explained
The Permissions API lets web apps query the status of browser permissions without triggering prompts. This improves UX by showing appropriate UI before requesting sensitive access.
Permission states:
- Granted - User allowed access; app can use the feature immediately
- Denied - User blocked access; app should show alternative UI
- Prompt - User hasn't decided; app can request permission via API
Common permissions: Camera, microphone, notifications, geolocation, clipboard, persistent storage, background sync, and more. Each has different privacy implications.
Best practice: Check permission status before calling the API. If denied, don't repeatedly prompt—explain why you need it and let users change it in browser settings. Respect user privacy preferences.
This tool shows current permission states and lets you test requesting permissions to see how browsers prompt users.
Examples
Camera: prompt
→ User hasn't decided
→ Can request via getUserMedia()Geolocation: granted
→ Can call navigator.geolocation immediately
→ No prompt neededNotifications: denied
→ User declined notifications
→ Must change in browser settingsFrequently Asked Questions
"Prompt" means the user hasn't made a decision yet. The next time your app requests this permission, the browser will show a permission dialog. If the user allows or denies, the state changes to "granted" or "denied".
No. Once a user denies a permission, it can only be reset in browser settings (usually in the address bar lock icon or site settings). This prevents websites from bypassing user decisions.
For privacy, the Permissions API only works for a limited subset of permissions. Sensitive permissions like camera/microphone can only be queried after being requested with getUserMedia().
Checking (via Permissions API) tells you the current state without prompting. Requesting (via feature API like getUserMedia()) triggers a browser dialog if state is "prompt". Always check first to avoid unnecessary prompts.
Permission states can contribute to browser fingerprinting, but modern browsers mitigate this. The Permissions API is designed to improve UX without exposing more information than feature detection already reveals.
💡 Tips
- Always check permission status before requesting to avoid annoying users with repetitive prompts
- If permission is denied, show a helpful message explaining why you need it and how to enable it in settings
- Permissions are origin-specific—https://example.com and https://www.example.com have separate permissions
- Some permissions (like camera) require secure context (HTTPS); they won't work on HTTP except localhost