Android OS user agent tokens
Browsers on Android include a Linux; Android platform token with an OS version, and historically a device model identifier. With user-agent reduction, Chrome on Android now sends a generic device token instead of the real model, so model-based detection no longer works and Client Hints are needed for device detail.
What this means
Android browsers report a Linux; Android platform token with the Android OS version, and historically also a device model string (for example a manufacturer and model code). Apps using the system WebView and Chrome both follow this general shape.
The Android version is useful coarse context. The device model, where still present, identified the hardware — but that is changing under user-agent reduction.
User-agent reduction on Android
Chrome's user-agent reduction replaces the specific Android device model in the user agent with a generic token (a fixed placeholder) and freezes some other detail. This means model-based detection and analytics no longer work from the legacy string.
If you need device characteristics, request high-entropy Client Hints (such as Sec-CH-UA-Model) explicitly, and accept that the browser may withhold them. Do not build features that assume the real model is still in the user agent.
- Token: Linux; Android plus OS version
- Device model is being replaced by a generic placeholder
- Use Sec-CH-UA-Model (high-entropy hint) for model, if granted
Practical handling
Group Android visits by OS version family where helpful, and stop relying on model strings for layout or analytics. Combine the Android token with the Accept-Language header for localisation rather than guessing.
Android traffic is overwhelmingly human and mobile, but Android also underlies some automation; use behaviour to separate the two rather than the platform token alone.
How it appears in analytics and logs
A Linux; Android token indicates an Android browser. The OS version is usually present, but the device model is increasingly replaced by a generic placeholder, so you can no longer reliably read the phone model from the user agent.
Diagnostic use case
Interpret Android platform tokens for mobile analytics and understand why device-model detection from the user agent has largely stopped working under UA reduction.
What WebmasterID can help detect
WebmasterID reads the Android platform token as coarse mobile-OS context and does not depend on device-model strings that UA reduction has removed, keeping mobile breakdowns accurate and privacy-safe.
Common mistakes
- Relying on the device model in the Android user agent after UA reduction.
- Treating the generic device token as a real phone model.
- Assuming every Android string is a human, ignoring Android-based automation.
Privacy and accuracy notes
Android tokens are coarse OS context. The move to a generic device token reduces fingerprinting surface. WebmasterID records the broad platform family only and does not reconstruct device models.
Related pages
- Android WebView user agent
Android WebView is the embedded browser component native apps use to show web content in-app. Its user agent is Chrome-like but includes a wv token, signalling the request came from inside an app rather than a standalone Chrome. This page explains the pattern and why WebView traffic is a distinct context.
- User-agent reduction explained
User-agent reduction is Chrome's effort to freeze and trim the legacy user-agent string, removing fine-grained OS and full-version detail. The information is not gone; it moves to opt-in User-Agent Client Hints. This page explains what reduction changed and how detection should migrate to Client Hints.
- 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.
- WebmasterID docs
Coarse mobile-OS context recorded without device fingerprinting.
Sources and verification notes
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.