Permissions-Policy Builder

Build a Permissions-Policy header to decide which browser features — camera, microphone, location, payments, USB, fullscreen and more — your site and any embedded iframes may use. Start from a recommended lockdown, adjust each feature, and copy the header with ready-to-paste Nginx and Apache lines.

Allowlist syntax

ValueMeaning
camera=()Disabled everywhere
camera=(self)Your origin only
camera=(self "https://a.com")Your origin and a.com
camera=*Any origin

When to use it

  1. Harden a site's security headers.
  2. Stop third-party iframes from asking for the camera or location.
  3. Allow a maps embed to use geolocation.
  4. Pass a security-header scan.

How to Use

  1. Pick a preset.
  2. Adjust each feature's allowlist.
  3. Copy the header or server config.

Features

  1. 30 features
  2. Presets
  3. Origin allowlists
  4. iframe allow output
  5. Nginx and Apache config
  6. Runs in your browser

FAQs

What does feature=() mean?

The feature is disabled for your page and every iframe.

Is Permissions-Policy the same as Feature-Policy?

It replaced Feature-Policy and uses a different syntax.

Do I need the iframe allow attribute too?

To let a cross-origin iframe use a feature, the header must allow its origin and the iframe needs allow.

Will unknown features break anything?

No. Browsers ignore names they don't recognize.

Does this cover all features?

It includes the 30 most relevant; you can untick ones you don't want in the header.

Technical Details

Each feature gets an allowlist written in the structured-header syntax the specification uses: feature=() disables it for the page and all embedded frames, feature=(self) allows only your own origin, feature=* allows any origin, and feature=(self "https://maps.example.com") adds specific origins, which are normalized to scheme://host[:port] and quoted while self is not. Directives are joined with commas. A matching iframe allow attribute is produced (in its own syntax, 'self' and bare origins separated by semicolons) for delegating features to embeds. The recommended preset disables powerful features such as camera, microphone, location, USB and the Topics API while keeping fullscreen, autoplay, clipboard-write and passkeys for your own origin.

Security Tools

Security Tools

  • htpasswd Generator
  • Common Port Reference
  • Google Dork Generator
  • Google Search Operators
  • CRC Generator
  • Vigen\u00e8re Cipher
  • TOTP Generator
  • Passphrase Generator