Online Tool Store
Permissions Policy Builder
Choose block or allow for browser features like camera and geolocation to generate a valid Permissions-Policy header. Runs entirely in your browser.
This works right here on your device — nothing gets sent out.
Features
Header
Example shown — adjust the features above for your own site.
How it works
- Choose block or allow for each browser feature.
- The Permissions-Policy header value is assembled automatically.
- Add the header to your server configuration.
Building maps each feature's chosen setting to its
Permissions-Policy directive syntax —
feature=() to block, feature=(self) to
allow only your origin — and joins them into one valid header value.
FAQ
Is my site data uploaded anywhere?
No. The header is generated entirely in your browser — nothing is sent to a server.
What is the Permissions-Policy header for?
It controls which browser features — camera, microphone, geolocation, and more — a page and any embedded iframes are allowed to use.
What do "Block all" and "Allow self" mean?
"Block all" disables the feature everywhere on the page; "Allow self" permits it only for your own origin, blocking third-party iframes from using it.
Where do I add the generated header?
In your web server or CDN configuration, or via a meta tag if your hosting doesn't support custom HTTP headers.
How we compare
| Feature | Online Tool Store | Writing the header by hand | Security scanner reports |
|---|---|---|---|
| No syntax to memorize | ✓ | Easy to typo a directive | Flags missing headers, doesn't build them |
| Free, no setup | ✓ | ✓ | Varies |
A security scanner tells you a header is missing but not how to write it. Permissions Policy Builder produces the exact header value from a simple checklist.