QQ Browser user agent
QQ Browser is a Chromium-based web browser developed by Tencent and widely used in China. Like other Chromium-derived browsers, its user-agent string carries the standard Chrome and Safari compatibility tokens together with a QQBrowser product token that distinguishes it. Recognising that token helps you attribute traffic to QQ Browser rather than to generic Chrome.
What this means
QQ Browser is a desktop and mobile browser from Tencent. On modern versions it is built on Chromium, so its engine and most behaviour match Chrome. The distinguishing element in the user agent is a QQBrowser product token alongside the inherited Chrome and Safari tokens.
Because it inherits the Safari compatibility token that every Chromium browser carries, naive detection can mislabel QQ Browser as Safari or as plain Chrome. Match the QQBrowser token first to attribute it correctly.
How it appears
The user agent follows the common Chromium layout: a Mozilla/5.0 prefix, a platform block, an AppleWebKit token, a Chrome version token, a Safari compatibility token, and the QQBrowser product token. On mobile a Mobile token and an Android or iOS platform block also appear.
Match on the stable QQBrowser product token rather than a pinned version number, since the version moves with releases. Treat the full string as a claim that can be copied, not proof of the client.
- Product token: QQBrowser (with a version suffix that changes)
- Carries inherited Chrome and Safari compatibility tokens
- Most common in China-facing desktop and mobile traffic
How it appears in analytics and logs
A user agent that carries the Chromium and Safari compatibility tokens plus a QQBrowser product token indicates Tencent's QQ Browser. It is a real human browser, not a bot, and is most common in China-facing traffic.
Diagnostic use case
Attribute Chinese-market browser traffic to QQ Browser instead of generic Chrome, and avoid mis-bucketing it as Safari because of the Safari compatibility token.
What WebmasterID can help detect
WebmasterID classifies the QQBrowser token as a distinct browser family rather than folding it into generic Chrome, so regional browser mix is visible without raw log parsing.
Common mistakes
- Bucketing QQ Browser as Safari because of the inherited Safari compatibility token.
- Folding QQ Browser into generic Chrome and losing regional browser-mix detail.
- Pinning a specific QQBrowser version instead of matching the stable product token.
Privacy and accuracy notes
The QQBrowser token only tells you the browser family. It carries no visitor identity. WebmasterID reads it as coarse browser context and never ties it to an individual.
Frequently asked questions
- Is QQ Browser based on Chrome?
- Modern QQ Browser is built on Chromium, so it shares Chrome's engine and carries the standard Chrome and Safari compatibility tokens, plus its own QQBrowser product token.
Related pages
- UC Browser user agent
UC Browser is a mobile-first browser developed by UCWeb (an Alibaba company), widely used in India, Indonesia, and other South and Southeast Asian markets. Its user agent commonly carries a UCBrowser product token. Some configurations route traffic through a compression proxy, which can affect how requests appear.
- 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.
- User agent sniffing pitfalls
User-agent sniffing means changing site behaviour based on substrings in the User-Agent header. It is fragile: it misfires on new or unexpected browsers, breaks as user agents are reduced, and is easily defeated by spoofing. Feature detection and Client Hints are more robust approaches for most cases.
- Privacy-first analytics
See browser-family mix as coarse context, with no fingerprinting.
Sources and verification notes
- MDN — User-Agent header structureChromium UA layout; QQBrowser product token observed in the wild, exact version not pinned.
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.