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.
What this means
UC Browser is a popular mobile browser, especially on lower-cost Android devices in price-sensitive markets. Its user agent generally includes a UCBrowser product token alongside a mobile platform token, and historically it has used a WebKit-based engine and, more recently, Chromium-based builds.
It is a real human browser. High UCBrowser share usually signals a mobile audience in South Asia (notably India) or Southeast Asia.
Proxy and compression modes
UC Browser has offered cloud-acceleration and data-compression modes that route page fetches through UCWeb servers to reduce bandwidth. In those modes, the originating IP and some headers may reflect UCWeb infrastructure rather than the end-user device.
This is expected behaviour for the browser, not spoofing. Do not classify such requests as datacenter bot traffic purely because they originate from a proxy; the UCBrowser token still indicates a human session.
- Distinguishing token: UCBrowser plus version
- Primarily mobile (Android) usage
- May use a compression/cloud proxy that changes the source network
Detection tips
Match on the stable UCBrowser token rather than the version. Combine it with the Accept-Language header to understand audience language rather than guessing from the browser alone.
Because some builds report Chrome-pattern strings, treat a missing UCBrowser token cautiously; UC Browser usage may be slightly under-reported in markets where it ships custom builds.
How it appears in analytics and logs
A mobile user agent containing a UCBrowser token is a human using UC Browser, typically on Android. In compression or cloud modes, requests may arrive from UCWeb infrastructure rather than the device network, which is normal for this browser.
Diagnostic use case
Recognise UC Browser users when analysing mobile traffic from Asian markets, and understand proxy/compression behaviour that can alter request characteristics.
What WebmasterID can help detect
WebmasterID classifies UC Browser as a human mobile browser. Where a compression proxy is in use, it still records the visit as human traffic and notes the browser family without fingerprinting the device.
Common mistakes
- Flagging UC Browser proxy requests as datacenter bots.
- Assuming the source IP equals the user's device location in compression mode.
- Matching on a UCBrowser version instead of the stable token.
Privacy and accuracy notes
UC Browser is identified only from the user-agent token. WebmasterID does not infer exact location and treats market context as coarse, never as a personal identifier.
Related pages
- 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.
- Accept-Language vs user agent
Accept-Language and User-Agent are different HTTP headers that answer different questions. Accept-Language expresses the visitor's preferred languages and locales; User-Agent identifies the client software and platform. Mixing them up leads to wrong localisation and brittle detection. Both are client-supplied claims and can be absent or altered.
- Bot vs human
Separate human mobile browsers from automation, even behind proxies.
Sources and verification notes
- UCWeb — UC BrowserMobile browser; UCBrowser token and optional compression proxy.
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.