Edge User Agent Strings Edge Click on any string to get more details Edge 18.19582. Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Edge/18.19582.
-->To override the user agent string from Microsoft Edge DevTools:
Select Control
+Shift
+P
(Windows, Linux) or Command
+Shift
+P
(macOS) to open the Command Menu.
Type network conditions
, choose Show Network conditions, and select Enter
to open the Network conditions tool.
In the User agent section, turn off the Select automatically checkbox.
Choose a user agent string from the list, or enter your own custom string.
Use the following options to discuss the new features and changes in the post, or anything else related to DevTools.
Alt
+Shift
+I
(Windows, Linux) or Option
+Shift
+I
(macOS) in DevTools.Note
Portions of this page are modifications based on work created and shared by Google and used according to terms described in the Creative Commons Attribution 4.0 International License.
The original page is found here and is authored by Kayce Basques (Technical Writer, Chrome DevTools & Lighthouse).
This work is licensed under a Creative Commons Attribution 4.0 International License.
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.
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.
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:
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.
Safari for iOS |
---|
Mozilla/5.0 (iPhone; CPU iPhone OS 10_3_1 like Mac OS X) AppleWebKit/603.1.30 (KHTML, like Gecko) Version/10.0 Mobile/14E304 Safari/602.1 |
Android Browser |
---|
Mozilla/5.0 (Linux; U; Android 4.4.2; en-us; SCH-I535 Build/KOT49H) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30 |
Chrome Mobile |
---|
Mozilla/5.0 (Linux; Android 7.0; SM-G930V Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.125 Mobile Safari/537.36 |
Opera Mobile (Blink rendering engine) |
---|
Mozilla/5.0 (Linux; Android 7.0; SM-A310F Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.91 Mobile Safari/537.36 OPR/42.7.2246.114996 |
Opera Mobile (Presto rendering engine) |
---|
Opera/9.80 (Android 4.1.2; Linux; Opera Mobi/ADR-1305251841) Presto/2.11.355 Version/12.10 |
Opera Mini |
---|
Opera/9.80 (J2ME/MIDP; Opera Mini/5.1.21214/28.2725; U; ru) Presto/2.8.119 Version/11.10 |
Opera Mini (iOS WebKit) |
---|
Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_2 like Mac OS X) AppleWebKit/537.51.2 (KHTML, like Gecko) OPiOS/10.2.0.93022 Mobile/11D257 Safari/9537.53 |
Firefox for Android |
---|
Mozilla/5.0 (Android 7.0; Mobile; rv:54.0) Gecko/54.0 Firefox/54.0 |
Firefox for iOS |
---|
Mozilla/5.0 (iPhone; CPU iPhone OS 10_3_2 like Mac OS X) AppleWebKit/603.2.4 (KHTML, like Gecko) FxiOS/7.5b3349 Mobile/14F89 Safari/603.2.4 |
UC Browser |
---|
Mozilla/5.0 (Linux; U; Android 7.0; en-US; SM-G935F Build/NRD90M) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 UCBrowser/11.3.8.976 U3/0.8.0 Mobile Safari/534.30' |
Dolphin |
---|
Mozilla/5.0 (Linux; Android 6.0.1; SM-G920V Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.98 Mobile Safari/537.36 |
Puffin for Android |
---|
Mozilla/5.0 (Linux; Android 5.1.1; SM-N750K Build/LMY47X; ko-kr) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Mobile Safari/537.36 Puffin/6.0.8.15804AP |
Puffin for iOS |
---|
Mozilla/5.0 (Linux; Android 5.1.1; SM-N750K Build/LMY47X; ko-kr) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Mobile Safari/537.36 Puffin/6.0.8.15804AP |
Samsung Browser |
---|
Mozilla/5.0 (Linux; Android 7.0; SAMSUNG SM-G955U Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/5.4 Chrome/51.0.2704.106 Mobile Safari/537.36 |
Yandex Browser |
---|
Mozilla/5.0 (Linux; Android 6.0; Lenovo K50a40 Build/MRA58K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.137 YaBrowser/17.4.1.352.00 Mobile Safari/537.36 |
MIUI Browser |
---|
Mozilla/5.0 (Linux; U; Android 7.0; en-us; MI 5 Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/53.0.2785.146 Mobile Safari/537.36 XiaoMi/MiuiBrowser/9.0.3 |
IE Mobile |
---|
Mozilla/5.0 (compatible; MSIE 10.0; Windows Phone 8.0; Trident/6.0; IEMobile/10.0; ARM; Touch; Microsoft; Lumia 950) |
Edge Mobile |
---|
Mozilla/5.0 (Windows Phone 10.0; Android 6.0.1; Microsoft; Lumia 950) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Mobile Safari/537.36 Edge/15.14977 |
BlackBerry Browser |
---|
Mozilla/5.0 (BB10; Kbd) AppleWebKit/537.35+ (KHTML, like Gecko) Version/10.3.3.2205 Mobile Safari/537.35+ |
Get access to a free, fully-working local version trial of DeviceAtlas.
Our high performance flagship product - the most complete data set.
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.
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:
Get started with a locally-installed trial to test DeviceAtlas at no cost.