v151 · Web APIs · Permissions Policy

Policy Header Builder

Toggle the directives you need and instantly see the correct Permissions-Policy header for both old Chrome (with direct-sockets-private) and Chrome 151+ (merged into local-network and loopback-network). Use this to plan your header migration.

Chrome 151 merges direct-sockets-private into local-network + loopback-network. Sites that set direct-sockets-private in their policy headers must update to the new directives — the old name is no longer recognised.

Before Chrome 151

direct-sockets

direct-sockets-private deprecated

local-network

loopback-network

allow-list:

Chrome 151+

direct-sockets

direct-sockets-private removed

local-network covers private

loopback-network covers loopback

allow-list:

Generated header — old

Generated header — Chrome 151+

feature detection

document.featurePolicy—

local-network allowed—

loopback-network allowed—

direct-sockets allowed—

migration checklist

Replace every direct-sockets-private=* in your Permissions-Policy headers with local-network=* and loopback-network=*.
If you only need private (RFC 1918) access and not loopback, you can omit loopback-network.
If you only need loopback (127.0.0.1) access, you can omit local-network.
The direct-sockets directive (for Isolated Web Apps) is unchanged — keep it as-is.
Test with both old and new headers before cutting over in production; Chrome 151 ignores direct-sockets-private silently.

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗