Google’s Prompt API

No web standard should require you to agree to an advertising company’s “terms of use.”

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.

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…

What Comes After Chrome

I co-created the world's most popular browser. Now, I'm joining The Browser Co to fulfill an old dream.

12 November 2025 | Isolated Web Apps - Current state and future direction | Calendar

The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.

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...

Welcome to the Post-Naive Internet Era

The grand idealism of the free and open internet might be over for now, but in its place falls a more practical mindset. Just like Silicon Valley’s entrepreneurs are entering their “Hard Tech” era, the people building web alternatives are also entering their Post-Naive Era. Here are the names to know.

The True Cost of Browser Innovation: Why Chrome's Divestiture Wouldn't End the Open Web

It is crucial for the public to understand that the web’s growth and innovation need not depend on Google’s monopoly or control, writes Alissa Cooper.

The Web Can Thrive Without Google’s Search Monopoly

Viable browsers and meaningful contributions to web standards can be sustained with more modest revenue streams, writes Alissa Cooper.

Web Crypto’s SubtleCrypto: A Masterclass in Developer Hostility and How It Strangles the Modern Web

Not Subtle, Just Sabotage — An API Against the Web

Web Install API Dev Spec

Web Install API Dev Design Spec Author: Amanda Baker, Diego Gonzalez, Kristin Lee, Lia Hiscock Spec status: Last updated: Links: Explainer | Chrome Status | CR bug | UX changes review doc Feature Overview Introduction Goals Non-goals Concepts Interfaces and Interactions JS API changes navig...