Why Chromium Deprecated the Data Saver Lite Mode Proxy

This article explores the primary reasons behind the Chromium project's decision to deprecate the legacy Data Saver, later rebranded as Lite Mode, on mobile devices. Originally introduced to reduce data consumption and speed up page loads on slow networks through Google-operated compression proxies, the feature eventually became obsolete. A combination of widespread HTTPS adoption, Decreasing mobile data costs, advancements in native web performance, and evolving privacy standards ultimately led to the permanent removal of the Lite Mode proxy in early 2022.

The Rise of HTTPS Encryption

The fundamental architecture of the Data Saver proxy relied on intercepting unencrypted HTTP traffic, compressing the assets on Google's servers, and sending the lighter version to the user's device. However, as the web transitioned overwhelmingly to HTTPS, this method became ineffective. Because HTTPS encrypts the connection end-to-end between the user and the destination website, a middleman proxy cannot read or compress the content without breaking the encryption. Consequently, the proxy could no longer optimize the vast majority of modern web traffic, reducing its functionality to merely passing encrypted data through or relying on limited client-side tweaks.

Decreased Cost of Mobile Data

When Data Saver was introduced in 2014, mobile data was expensive, and many regions relied heavily on slow 2G and 3G networks. By 2022, global telecommunications infrastructure had improved drastically. The rollout of 4G and 5G networks, paired with a significant drop in the cost per gigabyte of mobile data worldwide, meant that users no longer needed aggressive, server-side compression just to browse the web affordably.

Native Browser and Web Optimizations

Over the years, the Chromium engine and general web standards evolved to handle data efficiency natively, eliminating the need for an external proxy. Modern web development introduced several features that achieve what Lite Mode used to do on a server:

  • Next-Gen Media Formats: The adoption of highly compressed image and video formats like WebP and AVIF drastically reduced page weights by default.
  • Native Lazy Loading: Browsers gained the ability to defer the loading of off-screen images and iframes until the user scrolls near them, saving data automatically.
  • Responsive Design: Modern websites use attributes like srcset to serve appropriately sized images based on the user's screen resolution, preventing mobile devices from downloading massive desktop-sized assets.

Privacy and Centralization Concerns

Routing user traffic through a centralized proxy server inherently raises privacy and security questions. Even for unencrypted HTTP traffic, funneling browsing histories and page content through a third-party server conflicted with the modern web's push toward greater user privacy. By deprecating the proxy, Chromium aligned itself better with modern privacy standards, ensuring that web traffic remains directly between the user and the host server they are visiting.

High Maintenance Overhead

Maintaining a global network of proxy servers required significant infrastructure and engineering resources. Inside the Chromium codebase, supporting Lite Mode required complex logic to determine when to trigger optimizations and how to handle broken pages resulting from aggressive transcoding. Because the actual data savings for users had dwindled to negligible amounts, the Chromium team concluded that the engineering effort was better spent on improving core browser performance directly on the device.