







Chrome origin trials allow developers to safely experiment with web platform features
Announcing Supporters of Chromium-based Browsers
Since Google announced the Chromium project in 2008, we have been excited to build on the great foundations of open-source web browsers and contribute to the continued d…

Experiments with Google
Since 2009, coders have created thousands of amazing experiments using Chrome, Android, AI, WebVR, AR and more. We're showcasing projects here, along with helpful tools and resources, to inspire others to create new experiments.

Forget the Fate of Chrome, Focus on the Fate of the Browser
In debating what undoubtedly won't happen, we're looking past some key things that are -- and might...
Origin Code Hosting · Cursor
Origin begins rolling out today in early beta on all paid plans. We're starting with the essentials, designed for agent scale: repos, pull requests, code browsing, and GitHub sync. Agent-native features ship soon.

About Browser Choice Allliance
The issue Microsoft’s deceptive tacticsimpede consumer choiceFor years, Microsoft has manipulated desktop browser choice, using deceptive tactics to push Edge onto users. Instead of competing on quality, it relies on forced resets, misleading prompts, and hidden settings to trap people into using its browser. Every time Microsoft forces, pushes or…

Built-in AI | AI on Chrome | Chrome for Developers
Atlassian Buys The Browser Company, Browser Wars, Why Atlassian
Atlassian bought The Browser Company, seeking to deliver an AI-enabled browser for work. It’s a reasonable bet, but I’m skeptical that browsers are the future.

ChromeAlone: Transforming a Browser into a C2 Platform
Google is building an experimental new browser and a new kind of web app
Meet the GenTab, nothing like the plain ol’ browser tab.

2026 Web Engines Hackfest
Web Platform community event for people working on the different engines (Chromium/Blink/V8, Safari/WebKit/JSC, Firefox/Gecko/SpiderMonkey, Servo, Ladybird), on the testing side (WPT, Test262), on specifications (W3C, WhatWG, TC39), on web compat (webcompat.com), or on documentation (MDN Web Docs, web.dev).

2026 Web Engines Hackfest
Web Platform community event for people working on the different engines (Chromium/Blink/V8, Safari/WebKit/JSC, Firefox/Gecko/SpiderMonkey, Servo, Ladybird), on the testing side (WPT, Test262), on specifications (W3C, WhatWG, TC39), on web compat (webcompat.com), or on documentation (MDN Web Docs, web.dev).

Google’s Chrome Antitrust Paradox
This Article examines Google’s dominance of the browser market, highlighting how Google’s Chrome browser plays a critical role in reinforcing Google’s dominance in other markets. While Google portrays Chrome as a neutral platform built on open-source technologies, this Article shows that Chrome is, in fact, instrumental in Google’s strategy to reinforce its dominance in the online advertising, publishing, and browser markets. The examination of Google’s strategic acquisitions, anticompetitive practices, and the implementation of so-called “privacy controls” underlines that Chrome is far from a neutral gateway to the web. Rather, it serves as a key tool for Google to maintain and extend its market power, often to the detriment of competition and innovation in the digital economy.This Article illustrates how Chrome not only bolsters Google’s position in online advertising and publishing through practices such as coercion and self-preferencing, but also leverages its advertising clout to engage in a “pay-to-play” paradigm—the cornerstone of Google’s larger strategy of market control. It also outlines potential regulatory interventions and remedies by drawing on historical antitrust precedents. Lastly, this Article proposes a triad of solutions motivated by an analysis of Google’s abuse of Chrome, including behavioral remedies targeting specific anticompetitive practices, structural remedies involving an internal separation of Google’s divisions, and divestiture of Chrome from Google into an independent organization.Despite Chrome’s dominance and its critical role in Google’s ecosystem, as well as its recent legal troubles with the Department of Justice, it so far has avoided significant antitrust action. A key reason for this inaction lies in the long-standing precedent supporting the hegemony of technology firms and the uncertainty surrounding Chrome’s viability as a standalone entity. This Article attempts to address these issues to enable antitrust actions that are essential in remedying current market imbalances. Such actions are also critical to mitigate future threats to competition from an increasingly monopolistic technology landscape, thereby fostering a competitive digital environment that promotes innovation and protects consumer interests.
Stronger with every update: How we’re making Chrome and the web safer in the AI Era
Chrome uses Gemini AI to automate vulnerability discovery, triage, and patching, accelerating updates to match modern security risks.

Chrome looks set to ship an LLM Prompt API to the web platform. At Mozilla, we oppose this API. We feel it has a large interoperability risk, and Google imposing T&Cs on a web API sets a dangerous precedent. Full details: github.com/mozilla/standards-positions/i…
Prompt API · Issue #1213 · mozilla/standards-positions
github.com