Read the documentation for Web Platform APIs, some of which are experimental in Chrome. For example, origin and developer trials, or features only found in Canary.
Chrome Platform status
Learn how Chrome uses Canary, Dev, Beta, and Stable release channels to test new features, and roll out updates.
Read the doc
Activate additional debugging tools, or try out new or experimental features.
Read the doc
Chrome Variations or Chrome Field Trials are a mechanism to test new features or changes to the Chrome browser or to Chrome OS, the Chrome operating system that runs on Chromebooks.
Read the doc

Shipped APIs

Report information on whether a page was blocked from using the back/forward cache on navigation.
Allow a capturing web app to ergonomically and confidently identify the captured web app, if the captured web app has opted-in.
Conditionally focus a tab or window for better screen sharing on the web.
Allow web applications to use advanced handwriting recognition services to recognize text from handwritten input, in real time.
Modern client-side routing, which adds improved functionality to build single-page applications.

Page Lifecycle API

The Page Lifecycle API provides lifecycle hooks so your pages can safely handle when browser suspend or discard pages without affecting the user experience.
Display arbitrary HTML content in an always-on-top window.
Guide the user away from oversharing.
A performant and robust way to crop a video track.
Allow page transitions within single-page apps.
Manage the browser deals yourself with content occlusion, when a touch device's virtual keyboard appears.

Origin trials

Learn about testing a new or experimental web platform feature.
The Captured Surface Control API lets web apps scroll and zoom captured tabs.
The Element Capture API is a performant and robust way for transforming a capture of the current tab into a capture of a DOM subtree.
Control how your app is launched, for example, whether it uses an existing or a new window and whether the chosen window is navigated to the launch URL.
Experiment with JavaScript-driven, same-document navigations that use the history API or Navigation API, triggered by a user gesture and modifies the DOM.
Allow your implementation to use the right underlying hardware metrics to ensure that users can take advantage of all the processing power available to them.

Always updating

See what's included in Chrome's latest stable and beta releases.