navigator.permissions · live · local

Explore browser permissions

List every Permissions API entry your browser supports and request prompts for camera, geolocation, notifications, MIDI, sensors, and clipboard — entirely in your browser.

Permissions Explorer
Total
10
queried
Granted
0
allowed
Denied
0
blocked
Prompt
0
ask first
API support:navigator.permissions ✓
permissions · query
geolocation
—
notifications
—
camera
—
microphone
—
midi
—
accelerometer
—
gyroscope
—
magnetometer
—
clipboard-read
—
clipboard-write
—
output · summary (136 B)
geolocation	—
notifications	—
camera	—
microphone	—
midi	—
accelerometer	—
gyroscope	—
magnetometer	—
clipboard-read	—
clipboard-write	—
Quick Start

How to query and request permissions

The Permissions API queries the current state without prompting. Trigger a request through the relevant Web API to fire the browser prompt.

  1. 01

    Inspect state

    Each row shows granted, denied, or prompt as reported by navigator.permissions.query().

    Inputs are treated as UTF-8 throughout the pipeline and validated client-side as you type — nothing dispatches until the value is well-formed.

    queryinpututf-8client-sidevalidated
    name · textstate · set
    camera	prompt
    loaded · parsedclient-side
  2. 02

    Request a permission

    Click Request to fire the appropriate getUserMedia, Notification.requestPermission, or getCurrentPosition call.

    Each toggle re-computes through a memoised hook, so flipping options never resets your input and the UI stays snappy on large inputs.

    requestoptionslivememoisedtoggles
    click · memoisedRequest · live
    prompt → granted
    options set · memoisedlive
  3. 03

    Watch live changes

    Each query subscribes to onchange events — flipping a site permission in browser settings reflects instantly.

    Randomness — where used — comes from crypto.getRandomValues, never Math.random. Heavy work sits in useMemo.

    eventscomputeinstantlocaldeterministic
    onchange · instantlive · computed
    event: change
    computed · instantinstant
  4. 04

    Copy summary

    Grab the full state list as tab-separated text.

    Copy writes through navigator.clipboard and downloads use a Blob — zero network traffic. Same input plus same options always yield the same bytes.

    copydownloadzero-networkreproducible
    ok · copiedtxt · copied
    Copied
    shipped · ready to shipsuccess
Pro tips

Pro tips for everyday utilities

Reach for crypto.getRandomValues

Cryptographically random for IDs, tokens, salts. Math.random is for animation and games, not security.

Sort IDs lexicographically

UUID v4 has no time ordering. Use ULID or UUID v7 if you need sorted IDs.

Mock data with seeds

Faker-style libraries can be seeded so tests are reproducible. Embed the seed in the fixture file.

Reference cards beat memory

Cheatsheets for Vim, Git, Docker, Linux signals are faster than man pages when you’re mid-flow.

Browser APIs vary

Touch events, gamepads, and clipboard differ across vendors. Feature-detect before use.

Persist in the right place

localStorage for user preferences, sessionStorage for transient state, IndexedDB for structured data.

Use Cases

When to use the explorer

Debug permission prompts, verify privacy settings, QA progressive enhancements.

Permission debugging

See which APIs your browser exposes and their current site state. Random values come from crypto.getRandomValues — cryptographically secure for tokens, salts, and session IDs. Math.random is deterministic enough for animations but predictable enough to be a security bug.

CSPRNG-backed

QA install flows

Replay first-time prompt flows for camera and notifications. Pair with hashids, ULID, or UUID v7 when you need both random and sortable — useful for primary keys, public-facing IDs, and event log ordering without a sequence column.

reproducible

Progressive enhancement

Test what happens when a feature is denied without leaving the tool. Output is deterministic given the same seed, so fixtures and tests stay reproducible across CI runs and contributor machines. Embed the seed in the fixture file for full replay.

snappy

Sensor coverage

Verify accelerometer, gyroscope, and magnetometer support per device. Heavy work runs through useMemo so the UI stays snappy on large inputs. Same input + same options yields identical bytes — the kind of stability snapshot tests rely on.

feature-detected

Live state checks

Watch onchange events fire when permissions flip in browser settings. Storage tools persist to the right backend: localStorage for user preferences, sessionStorage for transient state, IndexedDB for structured data. Pick the right shelf and quota worries disappear.

deterministic

Cross-browser audit

Compare which entries each browser exposes via the Permissions API. Browser feature detection: clipboard, fullscreen, gamepad, and Web Bluetooth APIs gracefully fall back when unavailable. No surprise white screens on Safari or older Firefox.

production-ready
FAQ

Frequently asked questions

Some permissions (sensors like accelerometer) don't trigger a UI prompt — the state is determined by browser-level policies.
No — every state comes from your browser. Clearing site data resets prompts to their default.
Safari implements a subset and may throw for unsupported entries — those rows show 'unsupported'.
Most browsers require a recent user gesture (click/keypress) on the page before clipboard reads will resolve.
No. All queries run locally in your browser through the Permissions API.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!