Origin trials are a way to test a new or experimental web platform feature, and give feedback to the web standards community on the feature's usability, practicality, and effectiveness, before the feature is made available to all users.
Origin trials give you access to a new or experimental feature, to build functionality your users can try out for a limited time before the feature is made available to everyone.
When Chrome offers an origin trial for a feature, you can register for the trial to enable the feature for all users on your origin, without requiring them to toggle any flags or switch to an alternative build of Chrome (though they may need to upgrade). Origin trials enable developers to build demos and prototypes using new features. The trials also help Chrome engineers understand how new features are used, and how they may interact with other web technologies.
Origin trials are public and open to all developers. They are limited in duration and usage. Participation is a self-managed process with limited documentation and support. Participants should be willing and able to work relatively independently using the documentation available, which, at this stage, will likely be limited to API specifications and explainers, though web.dev tries to provide guidance whenever possible.
If you register for a trial, the Chrome team will periodically ask you for specific feedback on your use of the trial feature. Some features may undergo multiple origin trials, as learnings are incorporated and adjustments are made.
Third-party origin trials
Origin trials are usually only available on a first-party basis: they only work for a single registered origin. Third-party origin trials make it possible for providers of embedded content to try a new feature across multiple sites without requiring a token for every origin.
Find out more: What are third-party origin trials?.
<meta http-equiv="origin-trial" content="TOKEN_GOES_HERE">
Warning: Usually if an API lands unchanged after a successful origin trial, there is a short period between the end of the origin trial and the date the implementation ships in the browser when the API will not be available. This is by design. If Chrome were to avoid the mandatory total-breakage period, that would bias toward also avoiding breakages in the API surface, which are often needed to improve the API. The final shipping API might be worse for it.
In rare circumstances, if there was clear evidence that developers engaged with the origin trial and that their concerns were taken into account in the final API design and implementation, this breakage period may be skipped upon request.
Photo by Louis Reed on Unsplash.