Skip to Content
Platform.Ontology

Fenced frames

Embeds content that cannot talk to or be read by the page around it.

Works without askingThings a page can doIsolationWeb browsersWhile you use it

In one line

Can embed a box of content that the page around it cannot look into

Embeds content that cannot talk to or be read by the page around it.

Used by ad auctions so the embedding page cannot see which ad rendered. It separates the frame's storage and messaging from the parent to block link-back tracking.

What it can and can't do

What the user does: Nothing. It happens when the page loads, usually where an ad or a widget sits.

It can

  • Show an ad or widget inside the page
  • Keep the embedded content walled off from the host site
  • Let ad systems pick an ad without sharing your details with the page

It cannot

  • Share what is inside the box with the page around it
  • Send scrolling or clicks to the host site beyond what the rules allow
  • Work in Firefox or Safari, including on iPhone
  • Be used by every site yet; it is still limited and new

How it differs between platforms: Only Chrome based browsers support it today. Firefox and Safari do not.

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported1262024-06-11None
EdgeSupported1262024-06-13None
FirefoxNot supportedNot availableNot listedNone
SafariNot supportedNot availableNot listedNone
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidSupported1262024-06-11None
Samsung InternetSupported28.02025-04-02None

How a site asks for it

API<fencedframe>; HTMLFencedFrameElement; Fence API
Browser compat keyshtml.elements.fencedframe
api.HTMLFencedFrameElement
How access is grantednone
What the user seesNone (no browser prompt)
Needs a secure context (HTTPS)Yes
Needs a user gestureNo
Activationnone
How long it lastsWhile the frame lives
How to take it backNothing to revoke (no permission is stored)
Inside an iframeNeeds opt-in headers (Supports-Loading-Mode: fenced-frame)

Typical flow

  1. Page creates fencedframe
  2. Browser loads from URN or opaque URL
  3. Frame cannot read parent, parent cannot read frame

Data you get

Shape: none

No individual data fields. The signal is the access itself.

Technical limits

  • No postMessage or storage sharing with the embedder; no access to the DOM from the parent
  • Fixed size rules for opaque URLs (no custom size) when used with auctions
  • Privacy Sandbox APIs were deprecated by Google in 2025; the feature remains in Chrome but ecosystem use is shrinking (verify current status)
  • Supported only in Chromium

The story

What it is

A box inside a page that is sealed off, so neither side can read the other.

For you

You see an ad or embed as normal. What you cannot see is that the page around it is blocked from learning which ad it is, which was meant to stop sites linking your browsing across pages.

For makers

It lets ad tech pick an ad using your interests without handing your identity to the publisher. Advertisers still get counts of views and clicks through special reports, so measurement stays alive.

Where you see it

TypeExampleApps
adsAn interest based ad is chosen in your browser and shown in a sealed frame, so the news site cannot see which ad you were shown.Google Ads, Protected Audience
analyticsAn ad network counts that an ad was shown, using a limited summary report instead of a per person log.None named
securityA payment or login widget is shown in a frame that the host page cannot peek inside.None named
mediaA publisher runs an ad slot on an article page without ever learning your ad profile.None named
shoppingA retailer retargets you with a product you viewed, without the news site you are reading ever seeing it.None named
gamesA browser game shows rewarded video ads in a sealed frame so the ad cannot read the game page.None named

Risks

  • Hard to inspect ads
  • Still used for tracking

What the platform says

  • Google: Fenced Frame. Chrome's Privacy Sandbox docs describe it as a frame that can show content without sharing information with the embedding page.

Good uses and abuse

Legitimate uses

  • Privacy preserving ads

Known abuse

  • Opaque ads that hide content from site owners

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2024-06, Chrome 126: Fenced frames ship with Privacy Sandbox
  • 2025-10, Chrome 141: Google announces sunset of Privacy Sandbox ad APIs

Sources

How well checked: Based on official documentation.

On this page