Opera for iOS Gets Data Saver, Compressing Pages on Opera’s Servers
Opera for iOS now has Data Saver, which compresses text and images on Opera’s servers. The company says it can cut data use by up to 80%. The feature is off by default.
Opera for iOS now has a data-saving mode called Data Saver. As Habr reported on November 15, 2026, Opera compresses images and text on its servers before sending them to an iPhone. The company says this can reduce data use when browsing the web by up to 80%. The mode is off by default.
What Gets Compressed—and What Doesn’t
Data Saver works on the text and images in web pages. Opera processes them on its servers before the data reaches the device. That matters if you want to know not just how large a page is after compression, but who handles it along the way. The description of the mode does not, however, support the claim that Opera processes all page content in the same way.
The words “up to 80%” are worth reading carefully: savings will not be the same on every site. What’s more, the mode does not compress audio, video or downloaded files. If those account for a significant share of your data use, you should not expect Data Saver to deliver the same savings across all browser traffic.
You cannot choose the compression level. There is no switch between preserving more image quality and saving more data. As a result, some images will appear in low quality. That matters more on pages where an image conveys information than on pages where its details are unimportant.
It is important not to claim more for the mode than we know. The source reports that text and images are compressed, but does not describe how this will affect every individual site. The news therefore does not tell us that every page will become harder to read—or, conversely, that the changes will be imperceptible. We know how the processing works, the stated maximum savings and the limitation affecting the quality of some images. The rest needs to be checked on the page in question.
How to Turn It On and Read the Counter
Data Saver does not start automatically: you have to turn it on in Opera. One way is to tap the three dots in the bottom-right corner and select the leaf-shaped “Data Saver” icon. Alternatively, open “Settings” → “Data Saver” and use the toggle. Switching the mode reloads the current tab.
Data Saver also works in private tabs. When the mode is on, private tabs are not exempt from text and image compression. That is a separate detail of how the feature works: the tab type alone does not tell you whether the browser is saving data.
Once the mode is on, you can see in Settings how much data it has saved. But the counter combines savings across different connections, including Wi‑Fi. It will not show mobile data savings separately, even if that is why you enabled the feature.
The counter’s readings are stored on the device and do not sync. This makes it a local record of the mode’s activity, not an overview of usage across multiple devices. Together with the inclusion of Wi‑Fi, that sets a straightforward limit on how to interpret the number: it shows the savings calculated by the browser, but not exactly how much mobile data remains in your plan.
What Site Owners Should Check
If important information on a page depends on an image, open it in Opera for iOS with Data Saver on and check whether the necessary details are still visible. It is especially useful to compare it with the page when the mode is off: the original file on the site and what a visitor sees after compression may not look the same. Testing is more reliable than guessing how noticeable the loss of quality will be.
My Take: Savings Without a Magic Button
I like it when a browser gives people a way to use less data. But there is a cost, and it is not buried in the fine print: Opera processes images and text on its servers, and users cannot choose the compression level. I would pay particular attention to pages where you have to make out fine details in an image to understand the point. If those details become hard to see after processing, knowing how much data they saved is unlikely to help visitors.
I also would not present the browser’s counter as a report on how much mobile data an audience has saved: it includes Wi‑Fi. Nor would I treat Data Saver as a substitute for working on the page itself. Hoping the browser will fix a page for its owner is a familiar infrastructure story: “it was blazing fast on staging,” and then the investigation begins. In my view, it makes more sense to make the page understandable without extra processing first, then check whether its meaning survives compression.
Sources
Where the news comes from. The text is a retelling in the author’s own words; the facts come from the source, the opinion is the author’s.
web infrastructure expert
I work on infrastructure, builds, and website speed, usually joining when “everything flew on staging.” I like automation if it still lets you figure out exactly what broke.
All posts by the authorRelated articles
Adaptive Dark Mode arrives in Safari 27.3 beta for light-themed sites
WebKit has added Adaptive Dark Mode to Safari 27.3 beta. When users choose it, the browser adapts light-themed sites for dark mode. Here’s what site owners should check.
Firefox Strengthens Protection Against Browser Fingerprinting
Mozilla has limited the information that helps websites recognize Firefox users without cookies. The new measures could affect analytics and visitor identification systems.
A Firefox Setting Helped the Author Resume Large Downloads
The author found that changing network.http.response.timeout helped him resume interrupted large downloads in Firefox. It’s an experimental tip, and resuming also depends on server support.
Discussion 4
Paweł Mazurek
For site owners, check whether the proxy changes image formats or request headers; cache rules and device-specific responses can behave differently when pages pass through Opera’s servers.
Aida Sarsenova
A proxy that quietly swaps image formats and nudges request headers is a lovely reminder that “same page” can mean “surprise, different cache variant.” I’d definitely test the Opera-served version before blaming the CDN for getting creative.
Urho Vainio
@pawel.marek I ran into this with image optimization proxies: a rewritten format or a missing device hint can make a cache serve the wrong variant, so I’d compare the actual request and response headers with Data Saver on and off—not just the page’s reported byte count. Since Opera says it processes text and images but doesn’t spell out every transformation, I’d also verify whether image dimensions and content negotiation survive the trip.
Eduardo P.
I’d be cautious about treating missing device hints as evidence that Opera’s proxy is serving the wrong variant; the article only confirms text and image processing, not which headers it forwards. Comparing headers is useful, but the response body and dimensions are stronger signals here.