Opera Mini browser beta

The Data Savings Workflow in Action

Opera Mini beta handles web pages differently from most browsers. When a user enters a URL, the request goes to Opera's compression servers first. The servers fetch the page, compress it, and send a lightweight version back to the device. This process happens in milliseconds. The result is a page that loads quickly even on slow networks. The data savings mode is always active in the beta version. Users can see the data saved in real-time through a counter in the address bar. The app also includes a "Status saver" feature, which allows users to save their browsing state for later. The page translation feature is another new addition. It allows users to translate web pages into their preferred language with a single tap. The custom action button in the address bar lets users assign a quick action, such as sharing or bookmarking. The workflow is seamless for most browsing activities. However, a limitation emerges when the compression server interacts with the ad blocker. The ad blocker is built into the browser, but the compression happens server-side. This means that some ads are processed before the ad blocker can act. Users have reported seeing intrusive interstitial ads despite having the ad blocker enabled. The ads appear to be served through Opera's own servers, bypassing the local ad blocker. This creates a conflict between the data-saving feature and the privacy promise of ad blocking.

Server-Side Compression vs. Client-Side Ad Blocking

Most browsers, like Google Chrome or Mozilla Firefox, handle ad blocking on the device. The browser downloads the full page and then removes the ads locally. Opera Mini beta takes a different approach. It sends the page request to Opera's servers, which compress the page and remove some content before sending it to the device. This server-side processing is what enables the 90% data savings. However, it also creates a problem for ad blocking. The ad blocker in Opera Mini beta is designed to block ads at the device level. But if the ads are already processed and embedded in the compressed page by the server, the local ad blocker may not be able to remove them. This is why users have reported seeing ads despite having the ad blocker enabled. The ads are coming from Opera's own servers, not from the websites themselves. This is a fundamental difference between Opera Mini beta and other browsers. Chrome's Lite mode, for example, also uses server-side compression, but it relies on Google's servers. The ad blocking in Chrome is handled by extensions, which work at the device level. Opera Mini beta's ad blocker is built-in, but it cannot block ads that are injected by Opera's own compression servers. This creates a conflict of interest: the data-saving feature and the ad-blocking feature are at odds with each other. Users who want to save data may have to accept that some ads will slip through. Users who want ad-free browsing may need to disable the data-saving feature, which defeats the purpose of using Opera Mini beta.

What Actually Changed in Recent Updates

The version history shows a pattern of incremental updates with new features and stability fixes. Version 99.5.2254.1785, released in July 2026, introduced the "Status saver" feature. This allows users to save their browsing state, including open tabs and scroll positions. The same version also added a custom action button in the address bar and page translation. These features are designed to enhance the user experience. The changelog also mentions "various stability and performance fixes," which is a common phrase in beta releases. Version 99.3.2254.1106, released in June 2026, had similar updates: "New: Status saver" and "Various stability and performance fixes." The APK size has varied across versions. Version 99.5.2254.1785 is 41.49 MB, while version 99.3.2254.1106 is 47.8 MB. The Android requirement has also changed. Earlier versions supported Android 6.0+, but the latest version requires Android 9.0+. This suggests that the app is evolving and may drop support for older devices. The updates have not addressed the core complaints. Users continue to report intrusive ads and ad-blocking issues. The ad blocker is a major selling point of Opera Mini, but it is not functioning as expected in the beta version. The updates have focused on adding new features rather than fixing existing problems. This is a common pattern in beta software: new features are prioritized over bug fixes. The "Status saver" feature is a welcome addition, but it does not solve the ad-blocking problem.

The Curious Case of the Interstitial Ads and the 2-Week Delay

One of the most puzzling issues reported by users involves the appearance of interstitial ads. These are full-screen ads that appear between page loads. Users have reported that these ads do not appear immediately after installing Opera Mini beta. Instead, they start appearing after about two weeks of use. One user documented this on Android StackExchange. They noted that during the first few weeks of using Opera Mini beta, they never encountered the ads. But after a certain period, the ads started appearing regularly. The user suspected that the server might be changed after a trial period. The ads are served through a URL like interstitial.opera-mini.net:31222/adsense/default.html. This suggests that the ads are coming from Opera's own servers, not from the websites being visited. The user also noted that the built-in ad blocker did not block these ads. This is a bizarre use-case: the ads are self-generated by Opera, and they only appear after a delay. It is unclear whether this is intentional or a bug. It could be that the beta version includes a trial period without ads, and after that, the ads are enabled to generate revenue. Alternatively, it could be that the ad blocker is not fully functional in the beta version. Either way, this is a significant issue for users who value ad-free browsing. The fact that the ads are served through Opera's own servers makes them difficult to block with third-party tools. This is a unique problem that is specific to Opera Mini beta.