How to use Permissions-Policy analyser
Read feature allowlists from a pasted Permissions-Policy response header. The check runs when you submit the form. Its inputs are processed in this browser.
How the check works
The parser reads feature=(allowlist) declarations and wildcard values. It distinguishes an empty list, self, explicit origins and an unrestricted wildcard.
The Overview tab explains the findings. Measured data lets you search individual fields and values, while JSON report shows the complete export. Export JSON to retain a baseline, or print the findings for your own records. Review the report before sharing it: browser characteristics, token claims, and file names can reveal information about your setup.
Read the result in context
A policy can restrict a feature even when the browser implements it. Allowing a feature in this header does not itself grant user permission.
Understand the limits
Feature support differs between browsers. Inherited policy and iframe allow attributes also matter; this tool parses only the supplied header.
Common questions
Where is the input processed?
In this browser tab. This tool does not submit its input to the site server or a third-party service.
What should I keep with a result?
Record the selected options, browser and time. Review exported values before sharing them. Generated passwords, tokens and HMAC secret keys are excluded from report exports.