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.
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
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Partial | 126 | 2024-06-11 | Stub planned in 156 |
| Edge | Not supported | Not available | Not listed | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Partial | 126 | 2024-06-11 | None |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | <fencedframe>, HTMLFencedFrameElement, window.fence |
| Browser compat keys | api.HTMLFencedFrameElement |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Per frame |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not 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
| Type | Example | Apps |
|---|---|---|
| ads | A news site shows a retargeted ad in a fenced frame, so the page owner cannot see which shop it is for. | Google Ad Manager |
| analytics | A test measured clicks inside a fenced frame without sharing page data to the ad. | None named |
| games | A game site tried sealed ads, so an ad for a rival game would not leak your play history. | None named |
| shopping | A shop's ad in a frame did not let the host page see which product you looked at before. | Criteo |
| media | A video site tried sealed ad slots to protect viewer interests from the publisher. | None named |
| security | Sealed 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
- Google Chrome: Fenced Frames. Chrome pitched fenced frames as a way to show ads chosen from private data without leaking to the page.
Good uses and abuse
Legitimate uses
- Embedding private-audience ads (historical)
Known abuse
- Hiding tracking beacons inside opaque frames
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough 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
Related capabilities
Related
- Protected Audience (FLEDGE, retired). Can't run ads in Chrome based on your interests, since the plan was retired
- Shared Storage API (retired). Can't store cross site data for ads in Chrome anymore, since it was retired in 2025
Sources
- Privacy Sandbox feature status page (updated Aug 14, 2026)
- Privacy Sandbox history and removal timeline (checked Oct 2, 2026)
- Fenced Frame spec
How well checked: Checked against real behavior.