Maxthon browser user agent
Maxthon is a web browser that on modern versions is built on Chromium. Its user-agent string follows the Chromium layout and adds a Maxthon product token that identifies it. Recognising that token attributes traffic to Maxthon rather than to generic Chrome.
What this means
Maxthon is a desktop and mobile browser with a long history; current releases are based on Chromium. Because of that, it inherits Chrome's engine and the standard compatibility tokens, with a Maxthon product token to distinguish it.
As with all Chromium derivatives, the inherited Safari token can trip up naive detection. Match the Maxthon token first to attribute it correctly.
How it appears
Expect the Chromium structure: a Mozilla/5.0 prefix, a platform block, an AppleWebKit token, a Chrome version token, a Safari compatibility token, and a Maxthon product token. Some historical Maxthon builds used different engines, so older strings may differ.
Match on the stable Maxthon product token rather than a fixed version. The whole string is a claim and can be copied, so it is not proof of the client.
- Product token: Maxthon (version suffix changes)
- Modern builds carry inherited Chrome and Safari tokens
- Older builds may have used a different engine layout
How it appears in analytics and logs
A Chromium-style user agent carrying a Maxthon product token indicates the Maxthon browser. It is a real human browser, not a bot, and should be counted as a human visit.
Diagnostic use case
Attribute Maxthon traffic distinctly from generic Chrome, and avoid mislabelling it as Safari because of the inherited Safari compatibility token.
What WebmasterID can help detect
WebmasterID can recognise the Maxthon product token as its own browser family rather than folding it into Chrome, keeping browser-mix reporting accurate.
Common mistakes
- Folding Maxthon into generic Chrome and losing browser-mix detail.
- Mislabelling Maxthon as Safari due to the inherited Safari token.
- Assuming all Maxthon versions share one engine — older builds differed.
Privacy and accuracy notes
The Maxthon token only reveals the browser family. It holds no visitor identity. WebmasterID treats it as coarse browser context only.
Related pages
- 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.
- 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
Browser-family mix as coarse context, with no profiling.
Sources and verification notes
- MDN — User-Agent header structureChromium UA layout; Maxthon product token observed in the wild, 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.