Security · browser capabilities
Permissions policy.
Build an allowlist for browser features, then validate the exact header value you plan to send. Everything runs locally; no policy text leaves this browser.
Generate a header
Generated header
The validator will flag duplicate features, malformed origins, and unsupported schemes.
Validate an existing policy
Paste only a policy you are authorized to inspect.Your validation result will appear here.
What this checks
- Recognised feature names and duplicate directives
- Structured allowlists such as
()and(self "https://example.com") - HTTP(S) origins, wildcard subdomains, ports, and rejected schemes
- Enforce vs report-only header naming
Standards note: Permissions Policy is still a W3C Working Draft and browser support varies. A valid header here is not proof that a browser, embedded frame, server, or application will behave as intended.
What this page is, and what it is not
This tool builds and checks a Permissions-Policy HTTP response header. That header lets your site switch browser features on or off for your own pages and for any frames embedded in them: the camera, microphone, geolocation, payment request, fullscreen and many more. It is not a privacy policy generator. A privacy policy is a legal document that tells visitors what personal data you collect, and this tool produces nothing of the kind. If you were looking for that, you need a template reviewed by a lawyer for your jurisdiction. If you want to limit what scripts and embeds can do in a visitor's browser, you are in the right place.
How the header is written
Each directive is a feature name, an equals sign and an allowlist. Directives are separated by commas. The allowlist is one of:
*to allow the feature in this document and in frames from any origin.(), an empty allowlist, to disable the feature everywhere. In the generator you pick "none" and it writes().selfto allow it in this document and in same-origin frames only.- One or more quoted origins, such as
"https://maps.example", to delegate it to specific other sites. Origins carry a scheme.
For example, Permissions-Policy: camera=(), microphone=(), geolocation=(self "https://maps.example") turns off the camera and microphone for everyone and allows geolocation for your own pages and one named mapping provider.
Worked example
Suppose your site is a blog with an embedded video and a contact form. You never use the camera, microphone, geolocation, payment request or USB features, but a video player in an iframe needs fullscreen. A sensible header is camera=(), microphone=(), geolocation=(), payment=(), usb=(), fullscreen=(self "https://video.example"). Paste that into the validator and it confirms each feature name, checks the structured-list syntax, and flags a duplicate directive if you accidentally list camera twice. Write the empty allowlist as () in the header. The quoted 'none' keyword belongs to the iframe allow attribute, not to the header.
Header versus the iframe allow attribute
The header controls your own page and what you permit frames to receive. A single frame can also be given or denied a feature with the allow attribute on the <iframe> tag. MDN notes the equivalent of an empty allowlist in the attribute is 'none', and that self keeps its meaning. The two work together: the W3C draft says a frame's inherited policy is based on the parent document's permissions policy as well as the frame's container policy (the allow attribute), so a feature has to be permitted on both sides.
Enforce or report-only
The generator can write either Permissions-Policy, which is enforced, or the report-only variant, Permissions-Policy-Report-Only, which is meant for testing. Report-only mode lets you send a draft policy and see what it would have blocked before it can break anything, using the reporting endpoint you configure. Start there on a site with many third-party embeds.
Common mistakes
- Putting
noneor'none'in the header where the empty list()belongs. - Leaving off the scheme on an origin, or using a wildcard where a precise origin is safer.
- Setting
*for a sensitive feature such as geolocation out of convenience. - Assuming every browser supports every feature name. Support varies by browser and feature, so an unknown directive is ignored.
- Treating the header as the only protection. It limits browser capabilities, not what your server sends, and it is separate from CSP.
What this tool does not cover
It does not test your live site or check how a browser will treat the header. The W3C specification is still a Working Draft and features change, so confirm against your target browsers. For related controls, see the CSP generator, the security headers analyzer and the Set-Cookie inspector.
Frequently asked questions
What is the Permissions-Policy header?
It is an HTTP response header that lets a site enable, restrict or disable browser features such as the camera, microphone and geolocation for its own pages and for embedded frames. Each directive names a feature and an allowlist of origins.
Is this a privacy policy generator?
No. A privacy policy is a legal document about the personal data your site collects. This tool only builds a technical HTTP header that controls browser features, and it does not produce any legal text.
How do I disable the camera and microphone for my whole site?
Send Permissions-Policy: camera=(), microphone=(). The empty parentheses are an empty allowlist, which disables the feature in your page and in all nested frames.
What is the difference between self and *?
Self allows the feature in your own document and in same-origin frames, but not in cross-origin frames. The wildcard * allows it for your document and for frames from any origin, so use it only when you mean it.
How do I allow a feature for one embedded site?
List its origin in the allowlist, for example geolocation=(self "https://maps.example"). Origins are quoted and include the scheme. The embedding iframe also needs a matching allow attribute.
What does the report-only header do?
Permissions-Policy-Report-Only lets you test a policy without enforcing it. Violations are reported to your configured endpoint, so you can see what a stricter policy would block before you switch to the enforced header.
Does every browser support every Permissions-Policy feature?
No. Support differs by browser and by feature, and the W3C specification is still a Working Draft. Features a browser does not know are ignored, so check the compatibility table for the features you rely on.
Sources
- MDN: Permissions-Policy header: syntax, allowlist values, directives, iframe allow equivalents, Report-Only variant (retrieved 2026-10).
- W3C: Permissions Policy (Working Draft): specification, serialization, header and allow attribute delivery, reporting (retrieved 2026-10).