Browser Permission Checker

See the real, current permission status this site has for camera, microphone, notifications, clipboard, and location - read live from the browser's own Permissions API.

Current site · Private browser-side check

Your browser permission overview

Checking existing states never opens a permission prompt. Access requests run only if you click an individual test button below.

Checking browser permission states without requesting access…
—Granted
—Prompt
—Denied
—Unknown / failed

Camera

Video camera access for this site.

Checking…

Checking API support…

Microphone

Audio input access for this site.

Checking…

Checking API support…

Notifications

Permission to show notifications. No test notification is sent.

Checking…

Checking API support…

Geolocation

One-time location request; coordinates are discarded immediately.

Checking…

Checking API support…

Clipboard Read

Status only. This tool never reads your clipboard.

Checking…

Checking API support…

No request button: checking this permission does not require accessing private clipboard contents.

Clipboard Write

Can the site copy text? Clicking below replaces clipboard contents with a safe test phrase.

Checking…

Checking API support…

★ ★ ★ ★ ★
No ratings yet — be the first

What Is a Browser Permission Checker?

This tool shows the permission states that your browser currently reports for this website: camera, microphone, notifications, geolocation, clipboard read, and clipboard write. It reads browser-reported decisions rather than trying to guess whether your device has a working camera, microphone, or location provider. A granted permission does not guarantee that the hardware is connected or available.

Permission checks run locally in your browser. The tool does not upload camera content, microphone audio, location coordinates, or clipboard contents. It never accesses those features automatically; the optional test buttons only perform their clearly labeled action after you click.

How to Use the Browser Permission Checker

  1. Open this page on HTTPS. Wait for the six permission rows to finish their read-only check. The automatic scan does not request access or open browser permission prompts.
  2. Review the status and source for each feature. GRANTED, PROMPT, and DENIED come from the browser. NOT QUERYABLE or QUERY FAILED means the state cannot be verified here, not that permission is necessarily denied.
  3. Check feature availability separately. A permission can show GRANTED while the corresponding hardware or action API is unavailable. The page also notes observable Permissions Policy restrictions and secure-context limitations.
  4. Use Re-check after changing browser site settings. Where supported, state changes can also update live.
  5. Optionally click an individual request button. Camera and microphone requests start and immediately stop the resulting tracks. Location requests discard the coordinates; notification access sends no notification. Clipboard Write replaces your clipboard with a clearly labeled, harmless test phrase. Clipboard Read is status-only and never opens the clipboard.
  6. Use Copy summary if you want a text snapshot of the displayed states. This copies only status information (not media, location coordinates, or clipboard contents) and replaces your current clipboard text.

How It Works

The checker first calls navigator.permissions.query() with each supported permission name. These queries do not trigger a permission prompt. Where the Notifications permission descriptor cannot be queried, the checker may instead read Notification.permission and labels that source. Some browser/API combinations do not expose a queryable state at all; these are shown as unavailable to query rather than falsely reported as denied.

For optional, user-triggered checks, the page calls the corresponding browser API only after you press its button: getUserMedia(), getCurrentPosition(), Notification.requestPermission(), or navigator.clipboard.writeText(). Such calls may open a browser prompt, fail because of settings or policy, or work without granting a persistent permission. Results are followed by a fresh permission query.

Understanding Your Results

  • GRANTED: The browser reports that this origin currently has permission. The physical device or API may still fail for unrelated reasons.
  • PROMPT: Permission has not been granted or denied for the current context, or an API reports its default state. A user-triggered request may show a browser prompt, but browsers can also suppress prompts.
  • DENIED: The browser reports a blocked state. It can be caused by user preferences, browser rules, or an embedding policy; it does not always mean you manually clicked Block.
  • NOT QUERYABLE: This browser does not expose a query result for that permission, or the Permissions API is not available. The feature itself may still work.
  • QUERY FAILED: The permissions query was rejected or returned an unrecognized state, so the tool cannot truthfully determine the decision.

Browser Limitations

Not every browser supports the same permission descriptors or request APIs. Safari and Firefox may differ from Chromium in which camera, microphone, or clipboard states they expose. Clipboard writes can work during a user gesture without a lasting GRANTED state; clipboard reads may require extra interaction or may not be queryable. Notification prompting can be restricted on mobile or inside iframes.

The displayed states describe this page's origin, not permission settings for every website or app on your device. A browser's Permissions Policy, HTTPS requirement, device availability, operating-system permissions, privacy extensions, and browser privacy rules can also affect whether a request works. Where policy inspection is unavailable, the tool explicitly says so rather than guessing.

Common Mistakes to Avoid

  • Treating GRANTED as a hardware test: It describes a browser permission decision, not camera quality, microphone input level, or GPS accuracy.
  • Treating NOT QUERYABLE as DENIED: Missing permission-query support is not proof that a feature is blocked.
  • Expecting a prompt from Re-check: Only an individual request button can attempt access, and the browser controls whether a prompt actually appears.
  • Assuming this page can force Allow or Block: Browsers control permission decisions. To revoke or reset a permission, open the site settings from your browser's address bar or settings menu.
  • Overlooking clipboard effects: The clipboard write test and Copy summary intentionally replace the text currently on your clipboard. Clipboard Read is never performed.

Frequently Asked Questions

Can I change a permission from this page directly?

You can optionally press a request button to ask the browser for access to a supported feature, but this page cannot force an Allow decision or revoke an existing decision. Use browser site settings to manually reset or block permissions. Merely opening the page or clicking Re-check does not ask for access.

Why does a permission show "denied" that I don't remember blocking?

The browser may apply a default rule, privacy setting, policy restriction, or a response to repeated dismissed prompts. Review your browser's site settings and try Re-check. DENIED does not by itself identify who or what blocked the request.

Are these permissions specific to this website only?

Yes. The checker reports the browser's state for the current origin and document context. A decision for this website does not grant permissions to another website, and browser or operating-system settings may still apply.

Is any of this permission data sent anywhere?

No permission status report is uploaded by this checker. The browser reads and displays states locally. When you explicitly request location, camera, or microphone access, that browser API is invoked locally and any obtained coordinates or media streams are immediately discarded or stopped. The page does not record or transmit their contents.

Why doesn't clipboard permission show up correctly in my browser?

Clipboard permission-query support varies across browsers and can depend on a user gesture. The checker separates the ability to query a permission from the availability of clipboard actions. The Clipboard Read row never reads your private clipboard, while the explicit Clipboard Write test can show whether a write works at the moment you click it.

Conclusion

Use this checker to understand the browser-reported permissions for the current website, without confusing a missing query result with an explicit denial. If a permission-sensitive tool still fails, investigate its browser support, device availability, and site settings. For a separate connection-security check, use the HTTPS Checker.