Skip to Content
Platform.Ontology

Fenced Frames (being phased out)

A sandboxed ad frame that cannot talk to the page around it. Chrome is turning it into a stub in 2026.

Works without askingTracking across apps and sitesPrivacy SandboxWeb browsersWhile you use it

In one line

Can't fully show an ad in a sealed frame, as Chrome makes it a stub

A sandboxed ad frame that cannot talk to the page around it. Chrome is turning it into a stub in 2026.

Embedded content that blocks communication with the embedder so ads chosen from private data cannot leak who saw them. Moved to Deprecate and remove on Aug 14 2026; stub in Chrome 156 (stable Oct 20 2026).

What it can and can't do

What the user does: Nothing. It would have happened when an ad loaded on a page

It can

  • Show an ad in a frame that cannot talk to the page around it
  • Let a page display an ad without learning who you are, in tests of Protected Audience

It cannot

  • Work in Edge, Firefox, Safari or Samsung Internet
  • Keep working in Chrome once the 2026 change makes it a stub
  • Share data with the page around it
  • Be used widely, since it was part of retired ad tests

How it differs between platforms: Only Chrome ever supported it, and Chrome is turning it into a stub in 2026.

Browser support

BrowserStatusFirst versionReleasedNote
ChromePartial1262024-06-11Stub planned in 156
EdgeNot supportedNot availableNot listedNone
FirefoxNot supportedNot availableNot listedNone
SafariNot supportedNot availableNot listedNone
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidPartial1262024-06-11None
Samsung InternetNot supportedNot availableNot listedNone

How a site asks for it

API<fencedframe>, HTMLFencedFrameElement, window.fence
Browser compat keysapi.HTMLFencedFrameElement
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsPer frame
How to take it backClear site data, browser privacy settings
Inside an iframeNot listed

Data you get

What comes back: Frame config
Shape: object
How often: per ad render

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

Technical limits

  • No postMessage to the embedder
  • URL is an opaque config object
  • Chrome only

The story

What it is

A walled off box for an ad that cannot talk to the page around it. Being phased out.

For you

You never see the box as different. An ad or embedded item loads inside a sealed frame, so the page cannot read what it shows. Chrome is turning it into a stub in 2026.

For makers

It was built for the Protected Audience ad auctions, so the page could not learn which interest based ad was shown. With that retired, there is less need. Makers who prepared must plan for removal.

Where you see it

TypeExampleApps
adsA news site shows a retargeted ad in a fenced frame, so the page owner cannot see which shop it is for.Google Ad Manager
analyticsA test measured clicks inside a fenced frame without sharing page data to the ad.None named
gamesA game site tried sealed ads, so an ad for a rival game would not leak your play history.None named
shoppingA shop's ad in a frame did not let the host page see which product you looked at before.Criteo
mediaA video site tried sealed ad slots to protect viewer interests from the publisher.None named
securitySealed frames block clickjacking style tricks where a page reads or overlays an ad.None named

Risks

  • Being turned off in Chrome
  • Little real world use

What the platform says

Good uses and abuse

Legitimate uses

  • Embedding private-audience ads (historical)

Known abuse

  • Hiding tracking beacons inside opaque frames

Scores

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

History

  • 2024-06, Chrome 126: Shipped for Protected Audience and Shared Storage (verify milestone)
  • 2026-08, Chrome 155: Aug 14 2026 status changed to Deprecate and remove
  • 2026-10, Chrome 156: Becomes a stub in stable scheduled Oct 20 2026; stub-removal experiments from 157

Sources

How well checked: Checked against real behavior.

On this page