What's the Latest Version of Opera User Agents

Latest Opera Mobile User Agent Strings (Android & iOS)

The table below is a copy-paste reference of the default user agent string every Opera mobile browser sends, last verified on July 17, 2026 — covering Opera for Android, Opera for iOS on iPhone and iPad, Opera GX Mobile, and Opera Mini.

How to read these strings. The Mobile token is what tells websites to serve a phone layout — Android tablet and desktop strings drop it. The OPR/ token identifies standard Opera inside an otherwise Chrome-identical Chromium string; on Opera for Android both the platform and the versions are reduced for privacy, so you see the frozen “Android 10; K” placeholder and zeroed versions (Chrome/148.0.0.0, OPR/100.0.0.0) no matter which phone or Android release you actually run. Opera GX Mobile on Android is the notable exception: it still sends the real device model, firmware build, and full Chromium build alongside its OPX/ token (the GX app version).

On iOS, Apple requires every browser to use the WebKit engine, so Opera’s iPhone and iPad strings mimic Safari — AppleWebKit/605.1.15, Mobile/15E148 — with the app identifier at the end: OPT/ for Opera (a leftover from its Opera Touch origins), OPX/ for Opera GX, and OPiOS/ for Opera Mini. On devices running iOS 26, WebKit freezes the OS token at “18_7” while the Version/ token carries the real Safari 26.x version. Opera Mini on Android reports through the system WebView (note the “wv” marker), which is why it shows a real device model and a full OPR build number — its current 99.x releases use the same format as the captured v96 string above.

About the Widely Cited “SM-M426B” Opera User Agent

You will see this string quoted across user agent databases and AI-generated answers as “the Opera Mobile user agent” — but no Opera product has ever sent it. It grafts Opera Desktop 117 build numbers (117.0.5408.39, from February 2025, with the prior build’s Chromium 132.0.6834.207) onto a Samsung Galaxy M42 5G (SM-M426B) Android 13 device token, and it breaks Chromium’s user-agent reduction three ways: a real device model, a full Chrome build, and a full OPR build would never appear in a genuine default string. It most likely originates from desktop DevTools mobile emulation or a bot generator, recycled through aggregator sites. If you need a real Opera Mobile user agent for testing, use the reduced Opera for Android string from the table above.

What's the Latest Version of Opera User Agents?

The Opera user agent is a string that the Opera browser sends to websites to identify itself. It includes essential details such as the browser version, operating system, and rendering engine, helping websites ensure compatibility and display correctly on Opera.

Opera User Agent Format

Example (Opera 133 stable on Windows, July 2026): Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36 OPR/133.0.0.0

Breakdown:

• Mozilla/5.0

A legacy identifier for compatibility with older browsers, used by most modern browsers, including Opera.

• (Windows NT 10.0; Win64; x64)

Windows NT 10.0: Indicates the operating system (Windows 10 or 11).

Win64: Specifies the 64-bit version of Windows.

x64: Denotes the CPU architecture (64-bit).

• AppleWebKit/537.36 (KHTML, like Gecko)

A frozen compatibility token. Opera actually renders pages with Chromium’s Blink engine (a fork of WebKit); the value never changes from 537.36 and simply keeps WebKit-sniffing websites working.

• Chrome/149.0.0.0

Reflects the Chromium version Opera is built on. Only the major version (149) is real — the minor numbers are zeroed out by user-agent reduction, so a genuine string never shows a full build number here.

• Safari/537.36

A WebKit-specific token for compatibility with websites expecting Safari-like behavior.

• OPR/133.0.0.0

The Opera-specific identifier, indicating the Opera browser version (Opera 133 pairs with Chromium 149) — also reduced to major.0.0.0 in current builds. On iOS the identifier is OPT/ instead, and Opera GX uses OPX/.

How to Modify Opera's User Agent on Desktop

• DevTools (Network conditions):
• Press Ctrl + Shift + I (Windows/Linux) or Command + Option + I (Mac) to open Developer Tools.
• Open the three-dot “Customize and control DevTools” menu → More tools → Network conditions.
• Under “User agent”, uncheck “Use browser default”, then pick a preset from the list or paste any custom string. The override stays active only while DevTools is open.
• Extensions:

You can use browser extensions like "User-Agent Switcher" from the Opera add-ons store to modify your user agent persistently, without needing to access Developer Tools.

How to Change the User Agent in Opera Mobile (Android & iOS)

Unlike desktop Opera, the mobile apps support neither extensions nor a custom user agent field — a common frustration in Opera’s own forums. The only built-in control is the Desktop site toggle, which switches between the mobile and desktop string:

• Opera for Android:

While viewing a page, tap the three-dot menu in the top-right corner and enable Desktop site. Opera then identifies itself as Opera on desktop Linux (the platform token becomes “X11; Linux x86_64” and the Mobile token is dropped) for that tab. Settings also include a global option to always request the desktop version of sites.

• Opera for iOS:

Tap the More (three-line) menu at the bottom right and enable Desktop site for the current tab — it works like Safari’s Request Desktop Website, because every iOS browser runs on Apple’s WebKit engine. Opera Mini offers no user agent setting at all.

• Developer workaround (full custom UA):

Because Opera for Android is Chromium-based, you can enable USB debugging on the phone, connect it to a computer, and inspect it from desktop Chrome via chrome://inspect (Chrome’s device discovery is more reliable here than Opera desktop’s). Once DevTools is attached, override the user agent from the same “Network conditions” panel described above — the override lasts while DevTools stays connected.

How to Check Opera's User Agent

• Via Browser:

Open Opera and navigate to opera://about to see your exact browser version and build details (this works on desktop and Android). To view the full user agent string itself, use the “What is my User Agent?” box further down this page — it works on any device, including Opera Mobile, which has no DevTools console.

• Using JavaScript:

Open Developer Tools (Ctrl + Shift + I or Command + Option + I), go to the Console tab, and type: navigator.userAgent; Press Enter to display the full user agent string.

What is my User Agent?

Frequently Asked Questions About Opera User Agents

What is the user agent for mobile devices?

A mobile user agent is the identification string a phone or tablet browser sends with every request. It usually carries a "Mobile" token plus platform details so websites can serve the mobile layout. Opera on Android currently sends "Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Mobile Safari/537.36 OPR/100.0.0.0", while Opera on iPhone sends a Safari-style WebKit string ending in OPT/<version>.

Does Opera have a mobile version?

Yes — several. Opera for Android is a full Chromium-based browser; Opera for iOS (the former Opera Touch, renamed in 2021) is a WebKit-based app; Opera GX Mobile brings the gaming browser to Android and iOS; and Opera Mini is a lightweight data-saving browser. Each identifies itself differently: OPR/ on Android, OPT/ on iOS, OPX/ for GX Mobile, and Opera Mini sends a WebView-style string with a full OPR build number.

How to change user agent in Opera?

On desktop, open DevTools (Ctrl + Shift + I), choose More tools > Network conditions, untick "Use browser default" under User agent, and pick a preset or paste any string — or install a User-Agent Switcher extension for a persistent change. On Opera Mobile there is no custom user agent option: the built-in control is the Desktop site toggle (three-dot menu on Android, More menu on iOS), which switches between the mobile and desktop string.

Can my user agent be used to track me?

On its own, no — thousands of people share the same string — but combined with other signals such as screen size, fonts, and time zone it feeds browser fingerprinting. That is why Chromium-based Opera now sends a reduced user agent: the platform token is frozen ("Android 10; K" on mobile, "Windows NT 10.0; Win64; x64" on desktop) and version details are zeroed out, with precise data moved to opt-in User-Agent Client Hints. Opera also bundles a tracker blocker you can enable in settings.