Updated for 2023 - The standard way to pass information to the server about the visiting device is to include it in the User-Agent (UA) string. This information typically passes the name and version of the browser among many other details. In order to get an understanding of which mobile browsers use your site, you need to know their User-Agent strings.
Here’s a handy list of UAs that you may want to use.
What is the User-Agent and what information does it pass?
Described in the HTTP standard, the User-Agent string contains a number of tokens that refer to various aspects of the request, including the browser’s name and version, rendering engine, device’s model number, operating system and its version, etc.
From a web developer’s perspective, User-Agent strings can be useful when it comes to testing how online content is rendered on various hardware and software combinations. What works well on Chrome Mobile and the latest Android may not work the same on an older device and browser.
Most common mobile browsers
The landscape of mobile browsers is quite complex, with several major players (pre-installed in most cases) and a number of locally popular contenders. While all phones come with pre-installed browsers, both Google Play and Apple App Store offer a number of alternative browsers, some focusing on speed and lightness, others on saving bandwidth and blocking ads, and an ever-increasing amount claiming to increase privacy and reduce a users' mobile digital footprint. (We discussed some of the more popular privacy-respecting browsers.)
According to our report on the most popular mobile browsers, Safari Mobile, Chrome Mobile, and Samsung Browser are the three most used mobile browsers across the globe. The report also lists a number of other locally popular apps for web browsing, such as UC Browser, Yandex Browser, IE Mobile, Opera Mobile, Opera Mini, Firefox, and MIUI Browser. Feel free to browse the stats for your local market using our Data Explorer tool.
The Complete Guide To User Agents.
Download our free e-book on User Agents to learn:
- What is a User Agent?
- How do you parse them?
- What can you do with them?
List of mobile browsers User-Agent strings
The following table contains User-Agent strings for all the most used mobile browsers today. Note that UAs used by mobile browsers vary depending on the browser version, device model, OS, and many other factors.
iOS and iPadOS
| Safari |
|---|
| Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.5 Mobile/15E148 Safari/604.1 |
| Safari (iPadOS) |
| Mozilla/5.0 (iPad; CPU OS 16_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.5 Mobile/15E148 Safari/604.1 |
| Chrome |
| Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/114.0.5735.99 Mobile/15E148 Safari/604.1 |
| Chrome (iPadOS) |
| Mozilla/5.0 (iPad; CPU OS 16_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/114.0.5735.124 Mobile/15E148 Safari/604.1 |
| Firefox |
| Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) FxiOS/114.1 Mobile/15E148 Safari/605.1.15 |
| Yandex.Browser |
| Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.0 YaBrowser/23.5.6.403.10 SA/3 Mobile/15E148 Safari/604.1 |
Android
| Chrome |
|---|
| Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Mobile Safari/537.36 |
| Samsung Browser |
| Mozilla/5.0 (Linux; Android 13; SAMSUNG SM-S918B) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/21.0 Chrome/110.0.5481.154 Mobile Safari/537.36 |
| Opera Mobile |
| Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36 OPR/99.0.0.0 |
| Opera Mobile (Presto rendering engine) |
| Opera/9.80 (Android; Opera Mini/7.5.33942/191.308; U; en) Presto/2.12.423 Version/12.16 |
| MIUI Browser |
| Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/100.0.4896.127 Safari/534.24 XiaoMi/MiuiBrowser/13.30.1-gn |
| Huawei Browser |
| Mozilla/5.0 (Linux; Android 10; JNY-LX1; HMSCore 6.11.0.302) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.88 HuaweiBrowser/13.0.5.303 Mobile Safari/537.36 |
| Phoenix |
| Mozilla/5.0 (Linux; U; Android 11; en-us; itel P661W Build/RP1A.201005.001) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.85 Mobile Safari/537.36 PHX/12.9 |
| Edge |
| Mozilla/5.0 (Linux; Android 13; SM-S918B) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Mobile Safari/537.36 EdgA/113.0.1774.63 |
| Yandex.Browser |
| Mozilla/5.0 (Linux; arm_64; Android 12; CPH2205) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 YaBrowser/23.3.3.86.00 SA/3 Mobile Safari/537.36 |
| UC Browser (UCWeb rendering engine) |
| Mozilla/5.0 (Linux; U; Android 4.4.2; en-US; HM NOTE 1W Build/KOT49H) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 UCBrowser/11.0.5.850 U3/0.8.0 Mobile Safari/534.30 |
| VivoBrowser |
| Mozilla/5.0 (Linux; Android 8.1.0; vivo 1820 Build/O11019; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/87.0.4280.141 Mobile Safari/537.36 VivoBrowser/10.4.2.0 |
| HeyTap Browser |
| Mozilla/5.0 (Linux; U; Android 13; vi-vn; CPH2159 Build/TP1A.220905.001) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.88 Mobile Safari/537.36 HeyTapBrowser/45.9.5.1.1 |
| Firefox (Gecko rendering engine) |
| Mozilla/5.0 (Android 13; Mobile; rv:109.0) Gecko/114.0 Firefox/114.0 |
| Amazon Silk |
| Mozilla/5.0 (Linux; Android 5.1.1; KFSUWI) AppleWebKit/537.36 (KHTML, like Gecko) Silk/108.4.6 like Chrome/108.0.5359.220 Safari/537.36 |
Get access to a free, fully-working local version trial of DeviceAtlas.
Our high performance flagship product - the most complete data set.
How to parse User-Agent strings
As you can easily notice from the list above, each User-Agent string contains a number of keywords that may obfuscate the device behind the request. For example, most UAs listed here include "Mozilla" and "Mobile Safari."
The result is that UA parsing solutions must be sophisticated enough to understand which elements of a UA are meaningful. A simple regex solution searching for keywords will struggle in terms of accuracy and detection speed. To make things worse, the number of UA combinations grows every time a new device, browser, browser's version, or OS version are released.
To tackle these issues you may want to consider using a specialized device detection provider, such as DeviceAtlas. It offers a patented algorithm that detects and identifies all devices requesting online content through parsing UA strings based on a constantly updated, massive list of connected devices.
Learn more about User-Agents
If you're looking for more information on User-Agents, be sure to read these posts on the DeviceAtlas blog:
Get started with a local device detection trial
DeviceAtlas is a high-speed device detection solution used by some of the largest companies in the online space to:
- Optimize UX and conversion rate on mobile
- Boost web performance
- Target ads and analyze web traffic
- Enable App analytics and advertising insights
Get started with a locally-installed trial to test DeviceAtlas at no cost.
