Permissions-Policy Delegation Simulator

Explain which declared layer decides a supported Permissions Policy scenario.

On-device No sign-up Free to use

Model delegation controls

?

The origin of the page that embeds the frame. It decides which requests count as the same origin.

?

Up to 4,000 characters. Use the header form: comma between features and parentheses around the origins. Features that are absent fall back to their default allowlist.

?

The URL in the src attribute. Its origin is the declared origin used by the allow attribute.

?

Leave blank when the frame stays on its src origin. Enter an origin such as https://other.example when the frame redirects, because the rules are checked against the loaded origin.

?

Up to 4,000 characters. Use the attribute form: semicolon between features, and self, src, none or a quoted origin in each list. An empty list means src.

?

Optional. A frame can restrict a feature further in its own response. Leave blank when the frame sends none.

Processed in your browser. Your inputs stay on this device.

Showing an example. Change the fields, then use model delegation to update it.

Result

Showing an example.

Allow the declared maps frame to use geolocation while restricting the other modeled features.

1 of 4 features reach the frame.

Loading the tool. Your result will appear here.

https://usefreetools.net/permissions-policy-delegation-simulator · 20 November 2026

Was this helpful?

How to use Permissions-Policy Delegation Simulator

  1. Enter the top-page origin and its Permissions-Policy response-header value, using the header syntax shown beside the field.
  2. Enter the iframe src URL and allow attribute. If the frame loaded a different origin after navigation, enter that loaded origin too.
  3. Optionally enter the frame’s own Permissions-Policy header, then run Model delegation.
  4. Read each feature’s result and deciding layer: top-page policy, iframe allow list or child response policy. Eligible does not mean the user granted permission or the API will work.

Example: Permissions-Policy Delegation Simulator

Allow the declared maps frame to use geolocation while restricting the other modeled features.

You add
Top page origin: https://app.example.com; Permissions-Policy response header of the top page: geolocation=(self "https://maps.embed.example"), camera=(self), microphone=(); iframe src (declared URL): https://maps.embed.example/view?place=dhaka; iframe allow attribute: geolocation 'src'; camera 'none'; fullscreen 'self'
You get
1 of 4 features reach the frame.

Options

Top page origin
The origin of the page that embeds the frame. It decides which requests count as the same origin.
Permissions-Policy response header of the top page
Up to 4,000 characters. Use the header form: comma between features and parentheses around the origins. Features that are absent fall back to their default allowlist.
iframe src (declared URL)
The URL in the src attribute. Its origin is the declared origin used by the allow attribute.
Origin the frame actually loaded
Leave blank when the frame stays on its src origin. Enter an origin such as https://other.example when the frame redirects, because the rules are checked against the loaded origin.
iframe allow attribute
Up to 4,000 characters. Use the attribute form: semicolon between features, and self, src, none or a quoted origin in each list. An empty list means src.
Permissions-Policy response header of the frame
Optional. A frame can restrict a feature further in its own response. Leave blank when the frame sends none.

Supported inputs and limits

  • One top page and one iframe, modeling camera, microphone, geolocation and fullscreen only.
  • Each header/allow input is limited to 4,000 characters and the supported exact-origin/keyword syntax.
  • Missing declarations use the tool’s recorded feature defaults; unsupported features or expressions are not inferred as allowed.
  • No nested frame tree, device API, permission prompt or live browser policy test is performed.

Where your input is processed

This tool does not upload your inputs. See the limits for anything saved on your device.

Policy eligibility is separate from permission

A modeled feature can be eligible under the supplied policy while a real browser still refuses it because of user permission, document state or platform support. The supported one-iframe scenario does not model an entire frame tree. Unsupported features or structures remain outside the result.

Questions about Permissions-Policy Delegation Simulator

Does eligible mean the camera will work?

No. User permission, browser support and document conditions are separate.

Can a child override an ancestor denial?

No. The modeled restrictions are intersected.

Can it model nested frames?

No. This page covers its explicitly declared one-iframe scenario.

Page updated · Project managed by Tony Hines · Report a problem with Permissions-Policy Delegation Simulator