A user agent string tells a website what device, operating system, and browser someone is using, and Android 12 devices generate a distinct set of these strings across Chrome, Samsung Internet, Firefox, and other browsers. Here’s a practical breakdown of what those strings look like and how to read them.
What a User Agent String Actually Contains
Every user agent string is built from a few consistent components, even though the format looks messy at first glance. Most strings start with “Mozilla/5.0,” which can largely be ignored since it’s a legacy compatibility token with no real relevance to the device. After that comes the platform details, followed by rendering engine and browser version information.
Chrome on Android 12
Chrome is the most common browser on Android, and its user agent strings follow a predictable pattern. A typical example looks like this:
Mozilla/5.0 (Linux; Android 12; Pixel 6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.62 Mobile Safari/537.36
Breaking that down, the string identifies the Linux kernel underlying Android, the Android version (12), and the specific device model (Pixel 6), followed by the WebKit rendering engine version and the Chrome browser version.
It’s worth knowing that Chrome’s user agent behavior has changed significantly since Android 12’s release. Newer Chrome versions apply what’s called User-Agent Reduction, which freezes most of the platform details regardless of the real device or OS version. A current reduced string looks like this instead:
Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/150.0.0.0 Mobile Safari/537.36
Almost every modern Chrome string says “Android 10; K” even on devices running much newer Android versions, because Chrome’s User-Agent Reduction — fully rolled out by May 2023 — freezes the platform to “Android 10” and replaces the real device model with the letter “K.” If you specifically need an Android-12-labeled string for testing, you’ll likely need an older Chrome version or a manually crafted string rather than a live capture from a current device.
Samsung Internet on Android 12
Samsung’s own browser produces a distinctly formatted string that includes both its own version number and a compatibility reference to Chrome:
Mozilla/5.0 (Linux; Android 12; SAMSUNG SM-N976N) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/16.2 Chrome/92.0.4515.166 Mobile Safari/537.36
Samsung’s official format includes the SamsungBrowser version token as mandatory, followed by a Chrome compatibility version, and an optional field indicating the intended device UX — “Mobile” for small screens, “TV” for smart TVs, or empty for PC-style content. Note that from Samsung Internet version 24.0 onward, the browser switched to a unified platform token for its own UA reduction, using “K” for mobile devices as well.
Firefox on Android 12
Firefox strings are structurally simpler than Chrome’s. Firefox user agent strings tend to follow a shorter, four-component format compared to Chrome’s more elaborate structure. A general Android Firefox format looks like:
Mozilla/5.0 (Android 12; Mobile; rv:94.0) Gecko/94.0 Firefox/94.0
The platform section of a Firefox UA string includes a “Mobile;” token when running on a phone-sized device, or a “Tablet;” token instead when running on a tablet. If you’re trying to detect device form factor through user agent sniffing, it’s more reliable to look for “Mobi” in the string rather than assuming any fixed correlation between “Android” and phone versus tablet form factors.
Best Practices When Using These Strings
- Match the string to your actual test target. Use appropriate user agents for the platform you’re testing — mobile, desktop, or crawler — rather than defaulting to one generic string for everything.
- Don’t rely on outdated strings for compatibility testing. Since Chrome and Samsung Internet now freeze most platform details, an authentic “Android 12” string may only be obtainable from an older browser build or a manually constructed test string, not a live capture from a current device.
- Verify your own device’s current string directly. You can check this by opening Chrome, typing chrome://version/ into the address bar, and looking at the “User Agent” field.
- Consider User-Agent Client Hints for anything requiring precise device data. With evolving privacy standards, Google is gradually reducing the information exposed through user agent strings, and initiatives like User-Agent Client Hints are meant to provide more detail while preserving user privacy.
Mozilla/5.0 (Linux; Android 12; Pixel 5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.5481.77 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 12; SM-G998B) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.98 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 12; SM-F926B) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.87 Safari/537.36
Mozilla/5.0 (Linux; Android 12; SM-A125F) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 12; M2103K19C) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 12; Pixel 3 Build/SP1A.210812.016.C1; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/101.0.4951.61 Mobile Safari/537.36 GoogleApp/13.17.13.23.arm64
Mozilla/5.0 (Linux; Android 12; RMX3195 Build/SP1A.210812.016; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/149.0.7827.91 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 12; POCO F2 Pro Build/SKQ1.211006.001; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/149.0.7827.91 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 12; Mi 11 Ultra; Build/SD1A.231211.16) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.7204.245 Mobile Safari/537.36
Mozilla/5.0 (Linux; Android 12; XQ-AU51) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Mobile Safari/537.36
Join The Discussion
Are you using Android 12 user agent strings for testing, scraping, or device detection work? Share what you’ve found works reliably given how much Chrome and Samsung Internet have changed their UA reduction behavior, and if you’ve run into mismatches between a device’s real Android version and what its user agent reports, that’s worth comparing notes on too.
