Opera Mini user agent
Opera Mini is a data-saving browser that routes page rendering through Opera's servers rather than fully on the device. Its requests carry an Opera Mini token, and because the rendering proxy fetches resources, the originating IP is Opera infrastructure rather than the end user's network. That makes it distinct from on-device browsers.
What this means
Opera Mini is built for low-bandwidth conditions. Instead of rendering entirely on the device, it sends the request to Opera's servers, which fetch and compress the page before delivering a lightweight version to the phone. This proxy model is why Opera Mini behaves unlike a normal on-device browser.
The practical consequence: the request that hits your origin comes from Opera's infrastructure, so the connecting IP is Opera's, and JavaScript and modern features may be limited compared with a full browser.
How it identifies itself
Look for an Opera Mini token in the user agent. Because the rendering happens on Opera's side, you will also see Opera infrastructure as the network source rather than a typical mobile carrier or residential network.
Do not treat the Opera server IP as datacenter automation to be blocked: this is a real human using a proxy browser. As always, the string is client-supplied and can be edited, so match the token but verify behaviour where it matters.
- Server-side proxy rendering on Opera's infrastructure
- User agent carries an Opera Mini token
- Source IP is Opera, not the visitor's own network
How it appears in analytics and logs
A user agent naming Opera Mini indicates a proxy browser that compresses and renders pages server-side. Requests reach you from Opera's data centres, so the source IP reflects Opera, not the human's location or device network.
Diagnostic use case
Recognise Opera Mini's proxy-rendered traffic, understand why its requests come from Opera servers, and avoid misreading that infrastructure as the visitor's own network.
What WebmasterID can help detect
WebmasterID recognises the Opera Mini token and its proxy nature, so its server-rendered requests are attributed to a real browser mode rather than mistaken for datacenter automation or the visitor's own network.
Common mistakes
- Blocking Opera Mini's Opera-server IPs as if they were scraping datacenters.
- Reading the Opera proxy IP as the visitor's location.
- Expecting full client-side JavaScript support from a proxy browser.
Privacy and accuracy notes
Opera Mini's proxy means the request IP belongs to Opera, not the visitor, so it must never be read as the user's precise location. WebmasterID treats the Opera Mini token as a browser-mode signal only.
Related pages
- Opera user agent
Opera switched to the Chromium engine, so its user agent resembles Chrome's but adds an OPR/ product token at the end. That OPR/ marker is how you tell Opera apart from Chrome and Edge in logs. This page covers the pattern and the historical Presto-era caveat.
- Mobile user agents: phones, tablets, in-app
Mobile user agents carry platform descriptors like iPhone or Android and often a Mobile token, but tablets and in-app browsers complicate the picture. An in-app browser (inside a social or messaging app) usually adds its own token to the string. This page explains the patterns and their pitfalls.
- Datacenter vs residential traffic signals
People often want to tell datacenter traffic from residential traffic, but the user-agent string carries no network information at all. Network type is a separate, IP-derived signal that must be paired with verification, and described carefully to stay privacy-safe. This page explains what the UA can and cannot tell you.
- Bot vs human
Separate proxy-browser humans from datacenter automation deterministically.
Sources and verification notes
- Opera — Opera MiniOfficial page; Opera Mini renders pages on Opera servers and is a data-saving proxy browser.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.