Data Saver stops ads, trackers, images and video before they download, rather than hiding them afterwards. It deploys by policy, needs no account, and reports nothing anywhere — because it has no server to report to.
Installs
6,469
lifetime, to September 2026
Weekly actives
2,352
organic, no marketing spend
Languages
25
interface and store listing
Servers
None
nothing leaves the device
The claim we will not make
Most tools in this category will quote you a percentage. We will not, and it is worth explaining why, because it is the same reason the product is worth deploying.
Chrome exposes no API that tells an extension how many bytes a blocked request would have transferred. Anyone quoting you a precise saving from inside a browser extension is estimating and presenting it as measurement. Your own network already measures this properly. So the offer is a pilot: deploy it to a slice of your fleet, read your own netflow or bandwidth reporting, and decide on your numbers rather than ours.
A 30-day pilot costs nothing and ends with a figure from your own monitoring.
Bandwidth is a direct cost line. Reducing page weight on subscriber devices reduces it at the source rather than at the network edge.
Schools & universities
Shared links that collapse at 9am. Blocking images and video on managed lab machines frees capacity without new hardware.
NGOs and field operations
Satellite and mobile-backhauled sites where every megabyte is metered and the connection is the constraint on the work.
Enterprises paying roaming
Travelling staff on tethered or foreign-network connections, where a single laptop can generate a surprising invoice.
Device makers
Entry-level hardware shipped into markets where data cost, not device cost, is what limits use. Ships preconfigured.
What a licence covers
Central deployment and lock-down. Every setting can be pinned by policy through Group Policy, MDM, or the Google Admin console. Locked settings are shown to the user as managed rather than silently enforced.
The maintained blocklist. Roughly 3,600 rules, rebuilt from upstream sources and shipped inside the package — no runtime fetch, so nothing breaks when your firewall blocks an update host.
Per-site rules. Block ads on a site while allowing its images, or the reverse, pinned centrally so an internal application keeps working.
Portable configuration. Work out a configuration on one machine, export it as JSON, and deploy that same file as policy.
A named contact for deployment questions during the pilot and the licence term.
Why it is safe to deploy
Manifest V3, no remote code. Every blocking rule ships inside the package and is evaluated by Chrome itself. The extension never fetches executable content.
No network egress of its own. No analytics, no telemetry, no licence call-home. There is nothing for your egress filtering to allow.
No data collection. Settings and blocked-request counts stay on the device. The one feature that records hostnames is off by default and local. See the privacy policy.
Public source. Every claim on this page can be checked against the code rather than taken on trust.
Already in production. Thousands of weekly users through the Chrome Web Store, which is the same build you would deploy.