Opera GX user agent
Opera GX is a variant of the Opera browser aimed at gamers, built on the same Chromium foundation as standard Opera. Like Opera, it identifies with an OPR token alongside a Chrome token, which means GX and regular Opera look similar in the user agent and are easy to conflate without close inspection.
What this means
Opera GX is Opera's gaming-oriented browser, sharing the Chromium engine and much of Opera's behaviour while adding features like resource limiters. Because it is part of the Opera family, it uses the same OPR product token convention that standard Opera uses.
That shared convention is the catch: an OPR token tells you the visitor is on an Opera-family browser, but it does not by itself cleanly separate GX from regular Opera in every case. Treat the OPR token as an Opera-family signal first.
How it identifies itself
Look for an OPR token together with a Chrome token and the AppleWebKit chain, the same shape as standard Opera. Any GX-specific differentiation depends on the exact tokens present, and we do not assert a guaranteed GX-only marker here because that detail is not something we can pin reliably across versions.
As with all browsers, the string is client-supplied and editable. Match the OPR token to attribute Opera-family traffic, and avoid splitting GX from Opera on assumptions you cannot verify.
- Chromium-based, gaming-focused Opera variant
- Uses the OPR token like standard Opera
- Cleanly separating GX from Opera is not always reliable
How it appears in analytics and logs
A user agent with an OPR token and a Chrome token indicates an Opera-family browser; Opera GX shares that pattern with standard Opera, so the OPR token alone does not always separate the gaming variant.
Diagnostic use case
Recognise Opera GX traffic, understand why it resembles standard Opera in the user agent, and avoid double-counting or mislabelling the two Opera variants.
What WebmasterID can help detect
WebmasterID attributes OPR-token traffic to the Opera family server-side, keeping it distinct from mainline Chrome so your browser mix reflects Opera and its variants accurately.
Common mistakes
- Assuming the OPR token alone always distinguishes GX from standard Opera.
- Counting Opera-family traffic as plain Chrome.
- Inventing a GX-only marker rather than treating OPR as an Opera-family signal.
Privacy and accuracy notes
The OPR token names a browser brand, not a person. WebmasterID treats Opera GX as a browser-family signal and never as an individual identifier.
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.
- Chrome user agent and its quirks
Chrome's user-agent string is full of historical artefacts: it claims AppleWebKit and Safari for compatibility even though Chrome uses the Blink engine. Google has also reduced the detail Chrome exposes in the UA, moving fine-grained information into User-Agent Client Hints. This page explains the pattern and the quirks.
- Browser user agents: how to read them
A browser user-agent string packs several tokens into one line: a legacy Mozilla prefix, a rendering-engine signature, the platform, and the browser itself. This page explains each part so you can read a UA without over-reading it, because the contents are client-controlled and can be copied by any client.
- Privacy-first analytics
Attribute Opera-family browsers without identifying individuals.
Sources and verification notes
- Opera — Opera GXOfficial page; Opera GX is a Chromium-based Opera variant. Exact GX-only UA markers not asserted.
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.