Skip to main content

Brave is bypassing Google AMP pages because they’re ‘harmful to users’

Brave is bypassing Google AMP pages because they’re ‘harmful to users’

/

Yet another nail in the AMP coffin

Share this story

If you buy something from a Verge link, Vox Media may earn a commission. See our ethics statement.

Illustration by Alex Castro / The Verge

Brave announced a new feature for its browser on Tuesday: De-AMP, which automatically jumps past any page rendered with Google’s Accelerated Mobile Pages framework and instead takes users straight to the original website. “Where possible, De-AMP will rewrite links and URLs to prevent users from visiting AMP pages altogether,” Brave said in a blog post. “And in cases where that is not possible, Brave will watch as pages are being fetched and redirect users away from AMP pages before the page is even rendered, preventing AMP / Google code from being loaded and executed.”

Brave framed De-AMP as a privacy feature and didn’t mince words about its stance toward Google’s version of the web. “In practice, AMP is harmful to users and to the Web at large,” Brave’s blog post said, before explaining that AMP gives Google even more knowledge of users’ browsing habits, confuses users, and can often be slower than normal web pages. And it warned that the next version of AMP — so far just called AMP 2.0 — will be even worse.

“In practice, AMP is harmful to users and to the Web at large”

Brave’s stance is a particularly strong one, but the tide has turned hard against AMP over the last couple of years. Google originally created the framework in order to simplify and speed up mobile websites, and AMP is now managed by a group of open-source contributors. It was controversial from the very beginning and smelled to some like Google trying to exert even more control over the web. Over time, more companies and users grew concerned about that control and chafed at the idea that Google would prioritize AMP pages in search results. Plus, the rest of the internet eventually figured out how to make good mobile sites, which made AMP — and similar projects like Facebook Instant Articles — less important.

A number of popular apps and browser extensions make it easy for users to skip over AMP pages, and in recent years, publishers (including The Verge’s parent company Vox Media) have moved away from using it altogether. AMP has even become part of the antitrust fight against Google: a lawsuit alleged that AMP helped centralize Google’s power as an ad exchange and that Google made non-AMP ads load slower.

In a statement provided to The Verge, Google spokesperson Lara Levin said that AMP is an open-source framework and continues to be helpful to developers. She said that Brave’s “allegations are misleading, conflate a number of different web projects and standards, and repeat a number of false claims.”

Still, nobody has gone after AMP quite as hard as Brave. De-AMP is somewhat reminiscent of Mozilla’s Facebook Container extension, which it created in 2018 as a way for Firefox users to prevent Facebook from tracking them across the web. It’s a statement of values in the form of a new feature. Google has been a target for Brave for years, too; Brave has published blog posts complaining about Google’s privacy features and even went so far as to build its own search engine. Brave has long billed itself as a privacy-first browser, so Google is a logical villain to choose.

Of course, for all Brave’s bravado and development, it holds only a tiny portion of the browser market, and Chrome continues to dominate. So no matter how much of the internet turns against it, AMP won’t die until Google kills it.

Update, March 21st, 9:20AM ET: Article updated with comment from Google.