An origin trial is a time-limited arrangement that lets a website turn on an experimental browser feature for every visitor, in production, without those visitors changing a setting or installing a special build. The site registers a domain with the browser vendor, receives a cryptographically signed token, and serves that token on each page where the feature should operate. The browser inspects the token and exposes the feature. When the trial closes, the token stops validating and the capability disappears.

The scheme solves a standards problem rather than a developer-convenience one. Chrome's origin trials explainerdescribes the failure it was built against: earlier rounds of browser experimentation saw unfinished features become de facto standards, burned into production code, with rival vendors pressed to implement designs nobody had finished arguing about; vendor-prefixed CSS was the canonical example. Origin trials cap that risk by making participation deliberate, registered and expiring.

How a token works

Registration happens through a vendor's origin trials console, which lists the trials open. The token issued in return is a base64-encoded payload carrying the origin, the feature name, an expiry timestamp and a subdomain flag, wrapped in a signature. Verification is local: Chrome's developer guide states that tokens are self-contained and checked on-device, with no server call and no network access, at negligible cost.

Three placements are supported: a meta tag in the document head using the http-equiv attribute origin-trial, an Origin-Trial HTTP response header, or a meta element injected by script before the feature is touched. Multiple tokens may sit on one page, which matters for code served across several country domains, and the framework takes the first valid one. Invalid and expired tokens are ignored silently.

Two boundaries catch implementers. Iframes inherit nothing: each frame is a separate document needing a token that matches its own origin. Subdomain tokens exist, matching everything under the registered domain, but Chrome refuses to issue them for entries on the Public Suffix List, a restriction lifted only for deprecation trials.

Scale is what separates an origin trial from a normal feature launch. A Chrome trial switches itself off globally once the feature exceeds 0.5% of all Chrome page loads, measured against the statistics Chrome Platform Status publishes. The figure is not arbitrary: it is the threshold below which Chrome considers a feature deprecatable, so the cap keeps experiments beneath the line at which removal becomes contentious. Higher limits are granted in rare cases where statistical significance demands a larger sample. A second control, offered on some trials, excludes a small share of users, typically under 5%, even when a valid token is present. Deprecation trials carry no cap, since re-enabling something that already existed creates no new dependency.

Origin and evolution

The framework reached stable users in Chrome 54, released on October 18, 2016, where foreign fetch was among the first features offered. WebUSB ran from Chrome 54 to 56, then again from 57 to 59 under revised parameters, establishing the pattern of a repeat trial after design changes.

Mechanics shifted afterwards. Tokens issued before February 3, 2021 expired after six weeks regardless of how long the trial ran; later ones align to the trial end date. The breaking period, an interval during which a feature was withdrawn before further experimentation, was dropped in April 2022. Feedback became optional rather than mandatory on February 12, 2024. Chromium's guidance on running an origin trial puts typical duration at 12 to 16 weeks against a four-week release cycle, and routes each trial through an Intent to Experiment on the blink-dev list, approval from Blink API owners, then a trial creation request in Chrome Platform Status. Extensions require a separate intent and a fresh approval.

Two variants followed. Third-party origin trials, documented by Chrome for providers of embedded content, let one registration cover every site where a script runs, removing the need for a token per publisher. Chrome limits the option to features where embedding is a normal use case, reviews requests so problematic scripts cannot reach many sites at once, and requires the token to arrive from an external JavaScript file rather than a meta tag or header. Deprecation trials, sometimes called reverse origin trials, run the mechanism backwards: AppCache was removed in Chrome 85 and re-enabled through a trial until Chrome 93, and mutation events followed from Chrome 127. Firefox and Microsoft Edge operate their own equivalents.

Why the mechanism matters to advertising

Almost every browser change that reshaped digital advertising since 2019 arrived through an origin trial first. When Google announced the Privacy Sandbox, Chrome engineering director Justin Schuh said the first origin trials would begin that year, starting with conversion measurement. The FLoC trial ran across Chrome 89 to 91 in 2021 with a minimum cohort size of 2,000 and produced 33,872 cohorts. The partitioned cookie trial ran from March 31 to August 30, 2022 before CHIPS shipped by default in Chrome 114. A trial reducing the Accept-Language header to a single value, relevant to language targeting, opened with Chrome 109 in January 2023.

The largest was the Privacy Sandbox Relevance and Measurement trial, a single registration covering several APIs at once. It opened in Chrome 101 Beta in 2022 across Topics, FLEDGE and Attribution Reporting, with fenced frames and later Shared Storage added, and PPC Land covered the Canary-stage testing that preceded it. Traffic rose to 5% of Chrome Stable from October 26, 2022 for Attribution Reporting and Topics and from November 9 for the auction APIs. Google's documentation records that the trial ended on September 20, 2023, roughly seventeen months after it opened.

Microsoft used the same route. The Ad Selection API limited preview required an Edge origin trial registration plus an attestation file on the participant's domain, running from Edge 130.0.2808.0 outside the European Economic Area and the United Kingdom after a March 2024 announcement. Neither it nor the PARAKEET proposal before it reached general availability.

One deprecation trial drew the line at advertising explicitly. After Chrome restricted third-party cookies for 1% of usersfrom January 2024, it offered first-party and third-party trials that restored cookie access only for non-advertising breakage, screening applicants against Disconnect's tracker protection lists. Domains serving both advertising and other purposes were refused.

Limitations, criticisms and disputes

The usage cap is the most-cited protection and the least consistently applied. The Privacy Sandbox trial ran at 5% of Chrome Stable, an order of magnitude above the standard 0.5% ceiling, and the exemption was granted by the organisation that authored both the feature and the rule.

Interoperability is the second complaint. A feature in origin trial exists in one engine, and Chrome's share means adoption can outrun consensus. The dispute over the Prompt API, which exposes Chrome's on-device Gemini Nano model to JavaScript, made the argument explicit. Mozilla filed a negative standards position citing interoperability and model neutrality, and Apple's WebKit team filed in parallel. In the Intent to Ship thread, Microsoft Edge's Alex Russell argued in May 2026 that the feature should return to origin trial status; Blink API owners acknowledged significant cause for concern about interoperability in a non-deterministic API and shipped anyway in Chrome 148.

Silent failure is a practical weakness. Chrome ignores invalid tokens without a console error naming the header, so an unrenewed token keeps a header in place while the feature stops working. Third-party trials multiply that surface across every publisher carrying the script.

Finally, a completed trial guarantees nothing. Chrome retired most Privacy Sandbox technologies on October 17, 2025after years of trials, citing low adoption, six months after confirming third-party cookies would stay. Testing conducted during that period and published by the Competition and Markets Authority found publisher revenue per impression down 27% on Google Ad Manager and 15% on AdSense, with advertiser spend falling 14% on Display and Video 360.

Not the same as

Chrome flags enable a feature on one machine for one person, through the browser's own settings page. Origin trials enable it for every visitor to a registered site.

Chrome-facilitated testing disabled third-party cookies for a share of users and labelled browsers so ad tech firms could compare groups, as PPC Land documented when Google issued invalid traffic guidance. Participation was assigned by Chrome rather than requested with a token, and the label travelled in the OpenRTB device extension.

Privacy Sandbox enrolment and attestation is a separate gate requiring a JSON file on the participant's domain. It governs who may call the APIs, not which browsers expose them.

Deprecation trials are a subset of origin trials, not a synonym. They restore something already removed, and they carry no usage limit.

Recent developments

XSLT is the current test of the mechanism's publisher-facing edge. Chrome's removal plan opened a deprecation trial in Chrome 152 on August 25, 2026, stops XSLT working on stable releases in Chrome 158 on November 17, 2026, and closes both the trial and the enterprise policy escape hatch in Chrome 176 on August 17, 2027. Google cites memory-safety vulnerabilities in libxslt and usage at roughly 0.02% of page loads. The proposal drew objections over government and RSS feed rendering, and the consequences for feed publishers run through to 2027.

On the other side of the ledger, Chrome 149 opened an origin trial for WebMCP after the May 19, 2026 announcement, letting sites declare structured tools that browser-based AI agents can call and moving the standard onto production traffic for the first time. Apple's Safari MCP server reached similar ground by a different architectural route. Chrome's built-in AI APIs arrive the same way: Writer and Rewriter trials run from Chrome 137 to 148, Proofreader from 141 to 145.

Timeline

  • October 18, 2016: Chrome 54 ships the origin trials framework to stable users, with foreign fetch among the first features offered.
  • March 14, 2017: WebUSB begins a second trial in Chrome 57 after design changes, establishing the repeat-trial pattern.
  • August 2019: Chrome announces the Privacy Sandbox and says conversion measurement will be the first origin trial.
  • September 2020: AppCache is removed in Chrome 85 and made available through a deprecation trial until Chrome 93.
  • February 3, 2021: Token expiry is aligned to trial end dates, replacing fixed six-week tokens.
  • April 2022: The breaking-period requirement is removed from the Blink launch process.
  • March 31, 2022: The CHIPS partitioned-cookie trial opens, running to August 30.
  • April 2022: The Privacy Sandbox Relevance and Measurement trial opens in Chrome 101 Beta.
  • October 26, 2022: Privacy Sandbox trial traffic rises to 5% of Chrome Stable for Attribution Reporting and Topics.
  • January 2023: The Accept-Language reduction trial opens with Chrome 109.
  • September 20, 2023: The Privacy Sandbox Relevance and Measurement trial ends.
  • January 16, 2024: Chrome opens the first-party third-party-cookie deprecation trial for top-level sites.
  • February 12, 2024: Feedback becomes optional for trial participants.
  • October 8, 2024: The Ad Selection API enters limited preview in Edge 130 via origin trial, excluding the EEA and the UK.
  • October 17, 2025: Chrome retires most Privacy Sandbox technologies after low adoption.
  • May 5, 2026: Chrome 148 ships the Prompt API over negative standards positions and a request to revert it to origin trial status.
  • May 19, 2026: Google announces a WebMCP origin trial in Chrome 149.
  • August 25, 2026: The XSLT deprecation trial opens in Chrome 152.
  • November 17, 2026: XSLT is scheduled to stop working on Chrome stable outside the trial.
  • August 17, 2027: The XSLT trial and enterprise policy are scheduled to close.

Summary

Who: Browser vendors run the programmes. Google Chrome operates the largest, with equivalents at Microsoft Edge and Mozilla Firefox. Participants are site operators and, through third-party trials, providers of embedded scripts, which in practice means ad tech vendors, analytics firms and consent platforms.

What: An origin trial is a registered, expiring permission to run an experimental browser feature on live traffic. A signed token naming the origin, feature and expiry is served in a meta tag, an HTTP header or via script, and verified on-device. Chrome disables a trial globally once usage passes 0.5% of page loads, a cap deprecation trials do not carry.

When: The framework shipped with Chrome 54 on October 18, 2016. Trials now typically run 12 to 16 weeks against a four-week release cycle, though the Privacy Sandbox trial ran from April 2022 to September 20, 2023.

Where: On any site served over HTTPS whose operator registers, with the feature active only on pages carrying a valid token and only in the browser running the trial.

Why: Browser engineers want production feedback before a design is frozen, and they want to avoid the earlier pattern in which unfinished features became permanent through unchecked adoption. For advertising, the mechanism matters because it is the gate every proposed replacement for third-party cookies has had to pass through, and because the timetable a trial sets determines when buyers, sellers and measurement vendors have to commit engineering effort to a standard that may never ship.