Device Tests

Permissions test: check what this site can access

Instantly see whether your camera, microphone, location, notifications, clipboard, and MIDI permissions are granted, blocked, or unset, then follow the exact steps to fix a blocked one.

Click any permission to trigger the real browser prompt, or use Request all for a whole section.

Granted 0 · Needs request 0 · Blocked 0 · Not supported 0

Media

System

Location & motion

Data & storage

Reset a blocked permission (your browser)

Open your browser's site settings from the address bar (usually a padlock or info icon) and reset the blocked permission, then reload the page.

Quick guide: how to use the Permissions Test

Takes under a minute
  1. 1Click a permission card to trigger the browser's real prompt.
  2. 2Choose Allow so the matching hardware test can run.
  3. 3If a card shows Blocked, open the padlock icon in the address bar and reset it.
  4. 4Reload the page after changing any permission.

Overview

Every modern browser sits between a website and your hardware, deciding on your behalf whether a page is allowed to see your camera feed, hear your microphone, read your rough location, or send you a notification. That decision is stored per site, per browser profile, and sometimes per device, which is exactly why the same website can behave differently on your work laptop than on your phone.

This page uses the standardized Permissions API, specifically navigator.permissions.query(), to read the current state of six commonly requested permissions directly from your browser. Nothing is simulated. If the badge says denied, your browser has genuinely blocked that permission for this exact page, and if it says granted, the underlying hardware or data would be available the instant a script asks for it.

The tool is meant to be the first stop when something that should work quietly fails, for example a video call that never shows your face, a site that can't find your location for store results, or a push notification that never arrives. Instead of guessing, you get a direct readout of the actual permission state, plus instructions tailored to the browser you're using right now.

How to read your results

The four states you'll see

  • Granted means the browser will hand over that capability immediately if a script asks, with no additional prompt. This is the state you want for anything you rely on regularly, like a webcam for meetings.
  • Blocked means a previous prompt was dismissed as "never allow," or an administrator or extension policy denies it outright. Scripts requesting this permission will fail immediately without even showing a dialog.
  • Not asked yet is the default state for a site you have never granted or denied anything to. The next time a script requests it, you will see the browser's native permission popup.
  • Not supported shows up when your particular browser does not implement a live query for that permission name. The permission itself might still work when actually requested; it just can't be checked in advance.

Why some rows never change state

Certain permissions, notably notifications and geolocation on some browsers, can only move from "Not asked yet" to granted or denied through an actual user interaction with the real permission dialog. This tool does not trigger those dialogs itself, since doing so on page load would be exactly the kind of intrusive behavior permission systems exist to prevent. Run the corresponding dedicated test, such as the Notification Test, to trigger the real prompt.

Troubleshooting a blocked permission

Blocked permissions are almost always fixable in under thirty seconds once you know where to look. The general pattern is the same across Chrome, Edge, Firefox, and Safari: find the site information control near the address bar, open the permission list for this specific page, and change the blocked entry.

Chrome and Edge

  1. Click the icon just left of the URL, it looks like a small padlock or a tune/adjustment icon.
  2. Choose "Permissions for this site" or "Site settings."
  3. Find the blocked permission in the list and change the dropdown from Block to Ask or Allow.
  4. Reload the tab. The new permission takes effect immediately on reload, not before.

Firefox

  1. Click the padlock icon in the address bar.
  2. Expand "Connection secure" or go straight to the permissions list shown underneath it.
  3. Click the small x next to the blocked permission to clear the saved choice.
  4. Reload the page so it can ask you fresh.

Safari on Mac

  1. Open the Safari menu, choose Settings, then the Websites tab.
  2. Pick the relevant category, such as Camera or Microphone, from the sidebar.
  3. Find this site in the list and change it from Deny to Ask or Allow.
  4. Close and reopen the tab.

When the browser fix doesn't help

If you have set the browser-level permission to Allow but hardware access still fails, the block is probably happening one layer down, at the operating system. Windows 10 and 11 both have a Camera privacy page and a Microphone privacy page under Settings, Privacy and security, and macOS has equivalent toggles under System Settings, Privacy and Security. Both need to allow your specific browser application, not just the website, before anything works end to end.

Permission by permission notes

Camera and microphone

These two are the most consequential permissions on this list because they expose live audio and video. Browsers show a persistent visual indicator, usually a colored dot or camera icon in the tab or address bar, whenever either is actively in use, so you always have a way to confirm a site isn't secretly recording after you've navigated away from an active call.

Geolocation

Geolocation permission does not automatically mean pinpoint GPS accuracy. On a desktop without GPS hardware, the browser typically estimates location from your Wi-Fi network and IP address, which can be off by a few kilometers in dense areas or much further in rural ones. On mobile, an allowed permission combined with GPS hardware and a clear sky view will usually be accurate to within a few meters.

Notifications

A granted notifications permission lets a site push desktop or mobile alerts even when the tab isn't focused, which is powerful but also the permission most commonly abused by spammy sites. If you're regularly bombarded by notification requests you didn't want, it's worth periodically auditing your browser's full notifications permission list rather than only fixing one site at a time.

Clipboard read and MIDI

Clipboard read access lets a page pull whatever text or data you last copied, which is why browsers restrict it heavily and often only allow it in direct response to a button click rather than automatically. MIDI access, particularly with system exclusive messages, is a specialized permission used almost exclusively by music production tools, virtual synthesizers, and hardware controller configuration utilities, so seeing it unsupported or unrequested on typical browsing is completely normal.

Frequently asked questions

Why does my browser say a permission is denied even though I never clicked block?

Some browsers auto-deny a permission after you dismiss the prompt several times without choosing, or after another extension blocked it on your behalf. Sites can also inherit a blanket 'ask before accessing' policy set at the browser level that shows as denied until you explicitly allow it.

What does 'prompt' mean in the permission status list?

Prompt means the browser has not yet asked you for that permission on this site, so nothing is granted or blocked yet. The first time a page actually requests the camera, microphone, or another guarded API, you will see the real permission dialog.

Why is clipboard-read shown as unsupported in my browser?

The Permissions API only reports a small standardized set of names, and clipboard-read support varies by browser and by whether the page is served over HTTPS. Firefox and Safari currently return 'unsupported' for this query even though clipboard access itself may still work through a direct read call triggered by a user gesture.

How do I unblock the camera or microphone for one specific website?

Click the padlock or site information icon at the left of the address bar, open the site's permission settings, find the camera or microphone entry, and change it from Block to Ask or Allow. Reload the tab afterward so the new setting takes effect.

Does resetting a permission remove it for every website, or just this one?

The reset options built into a browser's address-bar padlock only affect the single site you are currently viewing. To reset permissions globally you need to go into the browser's full privacy settings page and clear site data or permissions across all sites, which is a much bigger action.

Why does this tool show different results in Incognito or a Private window?

Private browsing sessions typically start with no granted permissions and do not remember previous choices, so every permission will usually read as 'Not asked yet' until you interact with a feature that requires it during that private session.

I allowed the camera but my video call app still can't see it. What's going on?

Browser-level permission and operating system-level permission are two separate gates. Windows, macOS, and mobile OSes have their own camera and microphone privacy toggles per app, so you may need to check Settings > Privacy on your device in addition to the browser's own permission for this site.

Can a website silently turn on my camera or microphone without asking?

No modern browser allows silent access. A getUserMedia call for camera or microphone always triggers a visible permission prompt the first time, and if you have previously granted access most browsers keep a persistent indicator, such as a colored dot near the address bar, while the device is actually in use.

Why does geolocation show granted even though I'm not sharing my exact address?

Granted only means the browser is allowed to hand this site coordinates when asked, it does not mean your address book or device name is exposed. The accuracy of the coordinates depends on GPS, Wi-Fi positioning, or IP-based estimation, and you can always deny an individual location request even if the general permission is granted.

What's the difference between this permissions test and my browser's own settings page?

Your browser's settings page shows saved preferences for many sites at once and requires several clicks to navigate to. This tool queries the live permission state for the current page in real time using the standard Permissions API, giving you an instant, focused snapshot without digging through menus.

Does MIDI access get requested automatically, or only when a site needs it?

MIDI access, especially with system exclusive messages enabled, is only requested when a page explicitly calls the Web MIDI API, usually for music production tools, virtual instruments, or hardware controller software. Most everyday websites never trigger this prompt at all.

Related tests

Related guides

Written by Chhandita ShitReviewed by Buddheswar DandapatLast updated July 28, 2026