Permissions-Policy says which browser features — camera, microphone, location, fullscreen and dozens more — your pages and the frames they embed may use. Switching off what you do not use means an embedded script or widget cannot ask for it either. It works in Chrome and Edge; Firefox and Safari do not support the header.
| Defined in | W3C Permissions Policy (formerly Feature Policy) |
| Syntax | feature=(allowlist), comma-separated |
| Browser support | Chrome and Edge; not Firefox or Safari |
| Replaces | The Feature-Policy header |
Check Permissions-Policy on your site
Enter a domain: we fetch its homepage and read every security header, this one first.
What it does
Each entry names a feature and who may use it: () for nobody, self for your own origin, a quoted origin for another site, * for everyone. A feature you do not mention defaults to allowed for everyone, which is why it is worth listing the ones you do not use.
The header governs your page and what it embeds; a cross-origin iframe also needs the permission in its allow attribute. It replaced the Feature-Policy header, whose syntax differs — Chrome still reads Feature-Policy, but Permissions-Policy wins when both are sent.
Directives and values
| Directive or value | What it does |
|---|---|
camera=() | Nobody may use the feature, the page included. |
geolocation=(self) | Only your own origin. |
geolocation=(self "https://maps.example") | Your origin and one other — origins are quoted. |
fullscreen=* | Every origin, including embedded ones. |
What to send
Permissions-Policy: camera=(), microphone=(), geolocation=()
That is OWASP’s example: list the features your site does not use. The OWASP Secure Headers Project publishes a much longer list that switches off almost everything.
How to set it
Apache
Header always set Permissions-Policy "camera=(), microphone=(), geolocation=()"
In the virtual host or .htaccess; needs mod_headers (and AllowOverride FileInfo for .htaccess). always also covers error pages and redirects, which plain Header set skips.
nginx
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;
In the server block. A location with any add_header of its own drops every add_header from the server block — repeat them there, or from nginx 1.29.3 use add_header_inherit merge;.
IIS (web.config)
<system.webServer>
<httpProtocol>
<customHeaders>
<add name="Permissions-Policy" value="camera=(), microphone=(), geolocation=()" />
</customHeaders>
</httpProtocol>
</system.webServer>
Caddy
header Permissions-Policy "camera=(), microphone=(), geolocation=()"
Cloudflare
Rules → Overview → Create rule → Response Header Transform Rule
Set static — header name: Permissions-Policy — value: camera=(), microphone=(), geolocation=()
On every plan, for records that are proxied through Cloudflare. Set replaces the header if your server already sends one.
WordPress
add_action( 'send_headers', function () {
header( 'Permissions-Policy: camera=(), microphone=(), geolocation=()' );
} );
In a small plugin or the theme’s functions.php. PHP only runs for pages WordPress builds, so images, scripts and other static files do not get the header — set it at the server or CDN to cover everything.
Common mistakes
- Writing it in the old Feature-Policy syntax (camera ‘none’; geolocation ‘self’) — a syntax error can make browsers ignore the whole header.
- Leaving an origin unquoted: geolocation=(self https://a.example) — the origin is ignored.
- Listing a cross-origin iframe’s origin in the header but not adding allow=”…” to the iframe.
- Expecting it to do anything in Firefox or Safari, which do not support the header.
What we recommend
Switch off at least camera, microphone and geolocation if the site does not use them. It is optional — our check marks it so — but it costs one line and limits what any embedded content can ask the visitor for.
Questions
What happened to Feature-Policy?
It was renamed Permissions-Policy, with a new syntax: camera ‘none’ became camera=(). The iframe allow attribute kept its syntax. Replace the old header with the new one.
Sources
Checked on 25 September 2026 against these official sources:
- Permissions Policy (W3C specification) — w3c.github.io
- Permissions Policy — developer.mozilla.org
- Control browser features with Permissions Policy — developer.chrome.com
- HTTP Headers — cheatsheetseries.owasp.org