user agent new safari

Useragents.me

Last updated: 23 september, 2024.

A self-updating list of the latest and most common useragents seen on the web across all device types, operating systems, and browsers. Data is always fresh, updating weekly.

This user agent list is perfect for web scrapers looking to blend in, developers, website administrators, and researchers.

The most common useragents list is compiled from the user logs data of a number of popular sites across niches and geography, cleansed (bots removed), and enriched with information about the device and browser.

Most Common Desktop Useragents

Most common mobile useragents, latest windows desktop useragents.

• Latest Mac Desktop Useragents

Latest Linux Desktop Useragents

Latest iphone useragents, latest ipod useragents, latest ipad useragents, latest android mobile useragents, latest tablet useragents.

• Smartproxy: Fast, Reliable Proxies
• Free Proxy Checker

An updated list of the most common useragents on the web, specifically the most common desktop useragents. You can see the relative share of each useragent included in the data table below. Hint: scroll sideways if you're viewing this page on a mobile device.

Get useragent list as JSON or TSV

Get the most common desktop useragents list conveniently in JSON format

Get the most common desktop useragents list conveniently in TSV (tab separated values) format

An updated list of the most common useragents on the web, specifically the most common mobile useragents. You can see the relative share of each useragent included in the data table below. Hint: scroll sideways if you're viewing this page on a mobile device.

Get the most common mobile useragents list conveniently in JSON format

Get the most common mobile useragents list conveniently in TSV (tab separated values) format

A complete list of the absolute latest Windows (desktop) useragents.

Latest Mac OS X Desktop Useragents

A complete list of the absolute latest Mac OS X (desktop) useragents.

A complete list of the absolute latest Linux (desktop) useragents.

A complete list of the absolute latest iPhone (mobile) useragents.

A complete list of the absolute latest iPod (touch mp3 player) useragents.

A complete list of the absolute latest iPad (tablet) useragents.

A complete list of the absolute latest android (mobile) useragents.

A complete list of the absolute latest tablet useragents.

About useragents.me

Useragents.me was created for web scrapers to give them quick and easy access to a list of the latest and most commmon useragents. Many similar lists have appeared in the past before us, but which have been quickly forgotten about and left to die.

Useragents.me is run and developed by someone working directly in the business of web scraping and who uses the site himself daily. Furthermore it's designed to be self-sustaining, self-updating, and low mantinence — meaning it will be a resource you can trustfully rely on for years.

What can I do with the useragents listed here?

The useragents listed here are most commonly used by web crawlers and web scrapers who want to mask their requests.

How often is the list of most common user agents updated?

The list of most common useragents (both desktop and mobile) is updated every week (specifically, on Sunday nights).

What is my current useragent?

As far as we can see, it's:

What is the difference between the most common and latest useragents listed here?

• The most common useragents list is a list of useragents that were observed accessing a set of sites in a given period of time. If you need to scrape a large number of pages and want your scraping requests to 'blend in', you can likely safely use this list in rotation to be successful.
• The latest useragents list is a list of the absolute latest useragents for a specific browser and device type. If you don't have a large scraping task (and so don't need to rotate useragents), you can likely safely use just one of these.

When should I use a mobile or desktop useragent?

Some sites will give you different content depending on the device you're using, so you should select the user agent with the correct device type for the task.

Node.js API Wrapper

useragents-me-api (by Davide Violante)

Built something with our API and want it featured here? — DM me @_stayml .

Useragents.me has been featured in...

• latenightlinux
• stackoverflow
• infoextreme
• Softantenna
• 阮一峰的网络日志 (Ruan Yifeng's weblog)

© 2022 - 2024 Useragents.me

• Do Not Sell My Personal Info

•  ⋅ 
• Web Dev SEO

How to Change User Agents in Chrome, Edge, Safari & Firefox

Discover how to change user agents in web browsers for testing purposes. Learn how to ensure your campaigns are running properly and target the right audience.

Whether you are an SEO pro, marketer, or web developer, you might often need to change your browser’s user-agent to test different things.

For example, imagine you’re running a MAC-OS-specific campaign. To find out if your campaign is running properly and not targeting Linux users, changing the user-agent of your browser can help you test.

Changing user-agents is almost a daily task for web developers, as they need to test how websites behave in different browsers and devices.

What Is A User-Agent?

A user-agent is an HTTP request header string identifying browsers, applications, or operating systems that connect to the server.

Browsers have user-agents, and so do bots and crawlers such as search engines Googlebot , Google AdSense, etc.

Here, we will learn how to change your browser’s user-agent.

The process is called user-agent spoofing .

Spoofing occurs when a browser or client sends a different user-agent HTTP header from what it is and fakes it.

While the term may be alarming, this is not a dangerous activity and will not cause you any problems. (Feel free to spoof your user-agent as much as you want.)

How To Change Your User-Agent On Chrome & Edge

Since Microsoft Edge is now using Chromium , the settings for both Chrome and Edge are the same.

1. Right Click Anywhere On Webpage > Inspect

Alternatively, you can use CTR+Shift+I on Windows and Cmd + Opt +J on Mac.

2. Choose More Tools > Network Conditions

Screen new.

Click on the three vertical dots in the upper right corner.

3. Uncheck Select Automatically Checkbox

4. Choose One Among The Built-In User-Agents List

If the user-agent you want doesn’t exist, you can enter any string you want on the field below the list.

For example, you can enter the following (Googlebot’s user-agent) into the custom field:

This may be useful for SEO professionals to identify if there is a cloaking on the website where the webpage shows specific content to Googlebot and different content to website visitors.

Alternatively, you can use the Chrome extension User-Agent Switcher and Manager .

That said, I try not to use browser extensions when the browser can perform the action I want. This is to avoid overloading the browser with add-ons.

Also, extensions have a habit of breaking websites unexpectedly sometimes.

While you might think the website you visited has an issue, the root cause can be one of the add-ons you’re using.

How To Change User-Agent On Safari

1. go to preferences.

2. Enable Develop Menu Bar

Go to Advanced  and check Show Develop menu in menu bar .

3. Navigate To Develop > User-Agent

You can again select from a predefined list or enter a custom user-agent string by choosing “Other…”

How To Change User-Agent In Firefox

In Firefox, it is possible to change user-agents via the browser’s built-in settings.

However, it is not as user-friendly as on Chrome or Safari.

It is a real pain to use the browser’s built-in feature.

Instead, we will use a Firefox add-on called User-Agent Switcher .

After installing the add-on, you will see an icon in the upper right corner.

You can select one of the predefined user-agents or enter a custom user-agent by clicking on the pen icon below.

Another extension you can use is User-Agent Switcher and Manager .

User-Agents Are Easy To Spoof

The user-agents are easy to spoof, and anyone can use these easy tricks to alter them.

This feature is useful for testing web apps against various devices, especially when the HTML is different for mobile  or tablet devices.

It is a cost-efficient way to test websites as one doesn’t need to have many physical devices to be able to test.

However, certain issues may appear on the real device but not when testing by changing the user agent and using a browser emulator.

In that case, if you want to test on multiple real devices, I suggest using Browserstack , which offers testing opportunities on almost all devices.

What is a user agent?

User agent is a HTTP request header string identifying browser, application, operating system which connects to the server. Not only browsers have user agent but also bots, search engines crawlers such as Googlebot, Google Adsense etc. which are not browsers.

What is user-agent spoofing?

When browser or any client sends different user-agent HTTP header from what they are and fakes it that is called spoofing .

How does changing the user-agent help SEO professionals?

SEO professionals may find changing the user-agent to be a critical part of their audit process. It is beneficial for several reasons:

• Identifying cloaking issues : By mimicking different user-agents, such as Googlebot, SEO experts can uncover whether a website presents different content to search engines than users, which violates search engine guidelines.
• Compatibility: It ensures web applications are compatible across various browsers and devices.
• User Experience : Developers can optimize the user experience by understanding how content is rendered on different systems.
• Debugging: Changing the user-agent can help pinpoint browser-specific issues.
• Quality Assurance: It’s an essential step in quality assurance and helps maintain the integrity and performance of a website.

Can changing your browser’s user-agent pose a security risk?

No, changing your browser’s user-agent, commonly called user-agent spoofing, does not inherently pose a security risk. While the term “spoofing” might suggest malicious intent, this practice in the context of user-agents is harmless. It is a tool for developers and marketers to test how websites and applications interact with various devices and browsers.

More resources:

• An Introduction to Rendering For SEO
• Using Chrome DevTools To Diagnose Site Issues In An Audit
• 7 Essential SEO Browser Extensions & Plugins

Featured Image: /Shutterstock

All screenshots taken by author, May 2024

I am dedicated to ensuring the smooth and uninterrupted operation of Search Engine Journal. As the Director of Technology, I ...

Home » Tech Tips » Browsers » How to Change User Agent in Mac Safari Browser?

How to Change User Agent in Mac Safari Browser?

Mac comes with Safari as a default web browser app. Though Safari works well for visiting website, many prefer Chrome for development and integration purposes. If you are using Safari, did you anytime wonder how a website you see in Safari will look like in Chrome on Mac? You will probably install Chrome and check the site. However, what will you do if you want to test in Chrome Windows version or Microsoft Edge Windows version? Good thing is that it is not necessary to install Chrome and you can change the user agent in Safari as Chrome and test the sites easily.

User Agents

Each browser has its own user agent string so that the website owner can identify how the site is being accessed. The string will change based on the device, operating system and browser version you use. For example, below is the user agent for Chrome in Mac. You can use this free tool to check your browser’s user agent.

From this information, you can find the device is Macintosh and Chrome version 114 is used to access your website. For mere testing purposes, you do not need to install Chrome, Edge or Firefox in your Mac for checking the websites on those browsers. All you need is to simply switch the user agent string in Safari and test the site’s appearance.

Changing User Agent in Safari Mac

Since user agent is kind of developer stuff, Safari by default will disable this feature. You need to first enable “Develop” menu to reveal the feature in Safari.

• Open Safari app in Mac and go to “Safari > Settings…” menu.

• Go to “Advanced” tab and enable “Show features for web developers” option showing at the bottom.

• Close Safari Settings pop-up and now you will see a “Develop” menu added to the browser.
• Click on “Develop” menu and hover over “User Agent” to view a list of items.
• By default, Safari automatically chooses the user agent and you can switch to one of the available agents from the list.
• If you want to check the string, just hover over any item and Safari will show the full string as a tooltip for you to check.

Available and Custom User Agents

As of Safari 17.0, below are the available user agents showing in the menu items for the latest OS/browser versions. User agent string will be automatically updated in Safari when the OS/browser gets new version.

• Safari – Mac, iPhone, iPad Mini and iPad.
• Microsoft Edge – macOS and Windows
• Google Chrome – macOS and Windows
• Firefox – macOS and Windows

You can switch the user agent to any of these browsers and test the site. If you want to use custom string, then click on “Custom” menu showing as a last option in the menu. This will show a text box in the pop-up where you can enter your custom user agent string and click “OK” button.

Testing Websites

After choosing the user agent, open the site that you want to test. Now, Safari will load the site as if you are seeing on different browser or device.

You can switch the user agent any time and Safari will reload the page using the new user agent. This way you can test whether the site is loading properly on different browsers without installing them on your Mac.

If you are using Chrome, learn more on how to change user agent in Google Chrome .

About Nagasundaram Arumugham

Naga is the founder and chief content editor of WebNots. He has over 20 years of experience in technology field and published more than 2000 articles.

You also might be interested in

How to Use Tags in MacBook?

Have you ever find it challenging to locate the files[...]

How to Recover Files Converted to Unix Executable File in Mac?

Have you ever gone made with folders and files on[...]

How to Use Stage Manager in Mac?

Apple redesigned and introduced lot of features in macOS Ventura[...]

DOWNLOAD EBOOKS

• SEO Guide for Beginners
• WordPress SEO PDF Guide
• Weebly SEO PDF Guide
• Alt Code Emoji Shortcuts PDF
• Free ALT Code Shortcuts PDF
• View All eBooks

TRENDING TECH ARTICLES

• 600+ Windows Alt Codes for Symbols
• Fix Chrome Resolving Host Problem
• Fix Slow Page Loading Issue in Google Chrome
• View Webpage Source CSS and HTML in Google Chrome
• Fix Safari Slow Loading Pages in macOS
• Fix Windows WiFi Connection Issue
• ROYGBIV or VIBGYOR Rainbow Color Codes
• Fix I’m Not A Robot reCAPTCHA Issue in Google Search
• Structure of HTTP Request and Response

POPULAR WEB TUTORIALS

• Move WordPress Localhost Site to Live Server
• Move Live WordPress Site to Localhost
• Move WordPress Media Folder to Subdomain
• Fix WooCommerce Ajax Loading Issue
• Create a Free Weebly Blog
• Edit Weebly Source Code HTML and CSS
• Add Scroll To Top Button in Weebly
• Add Table in Weebly Site
• How to Add Advanced Data Table Widget in Weebly?
• Up to $500 Free Google Ads Coupon Codes

FREE SEO TOOLS

• Webpage Source Code Viewer
• HTTP Header Checker
• What is My IP Address?
• Google Cache Checker
• Domain Age Checker Tool
• View All Free Web and SEO Tools

© 2024 · WebNots · All Rights Reserved.

Type and press Enter to search

Sign up for our daily newsletter

• Privacy Policy
• Advertise with Us

How to Change the User Agent in Safari for Mac

In order to let websites serve browser-specific settings and pages, your browser sends a string called user agent to the websites that you visit on your computer. That way the target website gets to know what browser you are using and serves the pages accordingly. While most websites look the same in every browser, some have specific files that are only rendered when using a specific browser, Safari, for example. If you wish to see how a site looks in a specific browser, you can change the user agent in Safari on your Mac and pretend to be another browser.

When you change the user agent string, it technically changes the way websites interact with your browser. For example, if a site has a file that only renders when you’re using Chrome for Android, you can change the user agent to Chrome for Android in Safari and see that site as if you’re viewing it for real on your Android device.

Here’s how you can go about doing that.

Changing the User Agent in Safari for Mac

Fire up Safari on your Mac from the dock.

Click on “Safari” in the top left corner and select “Preferences…” You will be taken to the preferences panel for your browser.

Once in the “Preferences” panel, click on the “Advanced” tab located in the top bar. It should open the advanced settings for your browser.

In the “Advanced” tab, you should see an option that says “Show Develop menu in menu bar.” Tick mark it, and it will add a new menu in the menu bar for you to change the user agent.

Pull down the new menu by clicking on “Develop” in the menu bar. Then select “User Agent,” and you should see a list of the predefined user agents that you can use right away with your browser. Click on any and it will be selected.

If you can’t find the user agent you want to use, click on “Other” in the menu, and it will let you manually specify one.

You should see a prompt asking you to enter a user agent string that you wish to use in Safari on your Mac. This part is usually used by the geeks or developers who know what a user agent looks like and how to write one. If you are unsure, you can use the help of the User Agent String website to try out various agents in your browser.

When you are done entering the string, click on “OK,” and it will save it for you.

To check whether the new user agent works or not, just visit any site that lets you check what browser you are using, and it will tell you the name of the browser depending on what user agent you provided in the previous step. I have provided the Opera Mini user agent thus the browser check site says I’m using Opera Mini, although my actual browser is Safari.

The user agent has been changed in Safari on your Mac, and you are now telling websites that you don’t use Safari but use another browser because the user agent string says so.

If you are looking to see how a website looks like in another browser without actually downloading it, you can use the above method and have Safari pretend to be the browser you want.

Our latest tutorials delivered straight to your inbox

Mahesh Makvana is a freelance tech writer who's written thousands of posts about various tech topics on various sites. He specializes in writing about Windows, Mac, iOS, and Android tech posts. He's been into the field for last eight years and hasn't spent a single day without tinkering around his devices.

UserAgents.io

What does it do.

UserAgents.io provides a simple way to parse a user agent and get technical information about it. The database is updated daily and easy to navigate.

What is an user-agent?

The User-Agent request-header field contains information about the user agent originating the request.

This is for statistical purposes, the tracing of protocol violations, and automated recognition of user agents for the sake of tailoring responses to avoid particular user agent limitations.

User agents SHOULD include this field with requests. The field can contain multiple product tokens and comments identifying the agent and any subproducts which form a significant part of the user agent. By convention, the product tokens are listed in order of their significance for identifying the application.

Source: RFC 2616

New User Agents

Latest user agents.

New WebKit Features in Safari 13

Dec 20, 2019

by Jon Davis

This year’s releases of Safari 13 for macOS Catalina, iPadOS, iOS 13, and watchOS 6 include a tremendous number of WebKit improvements for the web across Apple’s platforms. Of particular note is the number of features that enhance website compatibility to bring a true desktop-class web browsing experience to Safari on iPadOS. This release is also packed with updates for improved privacy, performance, and a host of new tools for web developers.

Here’s a quick look at the new WebKit enhancements available with these releases.

Desktop-class Browsing on iPad

WebKit provides the heart of this new experience with deep, fundamental changes that deliver a great desktop website experience on a touch device. With the exception of iPad mini, Safari on iPad will now send a user-agent string that is identical to Safari on macOS. Beyond just a user-agent change, WebKit added new support for web standards to provide the needed compatibility and quality. That included adding new support for Pointer Events, the Visual Viewport API, and programmatic paste. You can read more details about support for those standards in the sections below. In addition, WebKit added Media Source Extensions support in Safari on iPadOS to improve compatibility with the desktop-variants of streaming video websites.

Beyond foundational new web standards support in WebKit, there are many other refinements for the desktop browsing experience on iPad. Page scaling behaviors have been fine-tuned to prevent horizontal scrolling on wide webpages with responsive design viewport tags. When a webpage is scaled down to fit entirely within the viewport, WebKit will increase the font size of content to ensure text is comfortably legible. WebKit added support for automatic Fast Tap on links and buttons to help make navigating web content feel more responsive. Improved hardware keyboard support adds the ability to scroll with the arrow keys and perform focus navigation. Find on page now works like Safari on desktop, highlighting all of the matching terms on the page with a special highlight for the current selection. The behavior of editing callout menus for text selections was polished to avoid overlapping in page controls provided by many document editing web applications. Last but not least, Safari includes support for background downloads, as well as background file uploads.

This new experience on iPad means significant changes for web developers to consider for their web technology projects. Safari on iPad is a chameleon; it can respond to servers as either a desktop device or a mobile device under different circumstances. Most of the time, Safari on iPad presents a macOS user-agent when loading a webpage. If Safari is moved into a one-third size when multitasking the desktop site will be scaled to fit the one-third size without reloading and losing your place. But loading or reloading a webpage while Safari is in one-third size will provide an iOS user-agent since the mobile layout is better suited to the smaller viewport.

Now more than ever before, web developers need to take great care in providing a single responsive web design that uses feature detection instead of relying on separate desktop and mobile sites dependent on the user-agent. Developers should be sure to test their desktop website experience on an iPad to ensure it works well for users.

Pointer Events

WebKit added support for Pointer Events to provide DOM events for generic, hardware-agnostic pointer input such as those generated by a mouse, touch, or stylus. It adds a layer of abstraction that makes it easier for web developers to handle a variety of input devices. Similar to mouse events, pointer events include coordinates, a target element, button states, but they also supports additional properties related to other forms of input, such as pressure, tilt, and more.

See the Pointer Events specification for more information.

Visual Viewport API

WebKit added support for the Visual Viewport API, that allows webpages to detect the part of the page that is visible to the user, taking zooming and the onscreen keyboard into account. Developers can use this API to move content out of the way of the onscreen keyboard. This is useful for a floating overlay, a custom completion list popup, or a custom-drawn caret in a custom editing area.

See the Visual Viewport API specifications for more information.

Programmatic Paste

WebKit also brings new support for programmatic paste in Safari for iOS and iPadOS with document.execCommand('paste') . When a page triggers programmatic paste within scope of a user gesture, a callout bar with the option to paste is provided. When the call out is tapped it will grant access to the clipboard and proceed with the paste. For paste operations where the contents of the clipboard share the same origin as the page triggering the programmatic paste, WebKit allows the paste immediately with no callout bar.

Learn more in the Document.execCommand() reference on MDN.

Accelerated Scrolling on iOS and iPadOS

Accelerated scrolling the main frame has always been available with WebKit on iOS. In addition, developers could use a CSS property called -webkit-overflow-scrolling to opt-in to fast scrolling for overflow scroll. None of that is necessary with iPadOS and iOS 13. Subframes are no longer extended to the size of their contents and are now scrollable, and overflow: scroll; and iframe always get accelerated scrolling. Fast scrolling emulation libraries are no longer needed and -webkit-overflow-scrolling: touch; is a no-op on iPad. On iPhone, it still has the side-effect of creating a CSS stacking context on scrollable elements. Developers will want to test their content to see how hardware accelerated scrolling everywhere affects it and remove unnecessary workarounds.

Performance Improvements

This release brings performance improvements that reduced the initial rendering time for webpages on iOS, and reduced load time up to 50% for webpages on watchOS. Reduced memory use by JavaScript in Safari, web views, and non-web clients that use JSContext. WebKit also achieved better graphics rendering performance showing up to a 10% improvement in the MotionMark graphics performance benchmark score.

Intelligent Tracking Prevention

The latest update to Intelligent Tracking Prevention enhances prevention of cross-site tracking through the abuse of link-decoration. The updates in ITP 2.3 as part of this release of Safari add new countermeasures. In addition to the 24-hour cookie expiry from ITP 2.2, non-cookie website data like LocalStorage will be marked for deletion if the page is navigated to from a classified domain to a landing URL with a query string or fragment identifier. Deletion happens after seven days of Safari use without user interaction on the website. Beyond link decoration, Intelligent Tracking Prevention will also downgrade document.referrer to the referrer’s eTLD+1 if the referrer has link decoration when the user was navigated from a classified domain.

For details on Intelligent Tracking Prevention updates, see the “ Intelligent Tracking Prevention 2.3 ” blog post and our collection of other privacy related blog posts .

FIDO2-compliant USB Security Keys

Safari 13 on macOS has support for FIDO2-compliant USB security keys through the Web Authentication standard. Security keys can hold device bounded public key credentials that are associated with specific internet accounts. This allows users to add an additional layer of protection to their accounts by utilizing security keys as a second factor to authenticate. Not just that, but Web Authentication also prevents phishing. Since user agents are arbitrating the entire authentication process and the public key credentials can never leave their bounded security keys, it’s impossible for phishing sites to get users’ targeted credentials.

More Privacy and Security Improvements

Building on the strength of privacy and security in WebKit, users will have additional protections with sandbox hardening on iOS and macOS, and navigation protection from third-party iframes .

Developers will now need to call DeviceMotionEvent.requestPermission() or DeviceOrientationEvent.requestPermission() to prompt the user for permission before getting access to the events, on in Safari or Safari View Controller on iOS and iPadOS.

Apple Pay in WKWebView

In iOS 13, webpages loaded in WKWebView can now accept Apple Pay. In order to protect the security of Apple Pay transactions in WKWebView , Apple Pay cannot be used alongside of script injection APIs such as WKUserScript or evaluateJavaScript(_:completionHandler:) .

If these APIs are invoked before a webpage uses Apple Pay, Apple Pay will be disabled. If a webpage uses Apple Pay before evaluateJavaScript(_:completionHandler:) is invoked, the completion handler will be called with a non-nil NSError . These restrictions are reset every time the top frame is navigated.

Media Improvements

Media improvements in WebKit improve both compatibility and capability for developers. Support for the decodingInfo() method of the Media Capabilities API allows developers to check for supported codecs, efficiently supported codecs, and optional codec features including new alpha transparency. WebKit now supports transparency in video with an alpha channel that works for all supported video formats.

In Safari on macOS, WebKit added the ability for users to share their screen with others natively, using web technologies, without the need for any plug-ins. SFSafariViewController gained WebRTC support for the navigator.mediaDevices property of the Media and Streams API.

Dark Mode for iOS and iPadOS

Last year WebKit added dark mode for the web to Safari on macOS Mojave. This year, WebKit brings the same support to style web content that matches the system appearance in Safari on iOS and iPadOS.

Learn how it works and how to add support to your web content in the blog posts on “ Dark Mode Support in WebKit ” and “ Dark Mode in Web Inspector ”.

Improved Home Screen Web Apps on iOS and iPadOS

Support for websites saved to the home screen have been polished to work more like native apps. The changes focused on better multitasking support, improved login flow to work in-line without switching to Safari, support for Apple Pay, and improved reliability for remote Web Inspector.

Safari WebDriver for iOS

Support for Safari WebDriver on iOS 13. Control via WebDriver is exposed to developers via the /usr/bin/safaridriver executable, which hosts a driver that handles REST API requests sent by WebDriver test clients. In order to run WebDriver tests on an iOS device, it must be plugged into a macOS host that has a new enough version of safaridriver. Support for hosting iOS-based WebDriver sessions is available in safaridriver included with Safari 13 and later. Older versions of safaridriver do not support iOS WebDriver sessions.

If you’ve never used safaridriver on macOS before, you’ll first need to run safaridriver --enable and authenticate as an administrator. Then, you’ll need to enable Remote Automation on every device that you intend to use for WebDriver. To do this, toggle the setting in the Settings app under Safari → Advanced → Remote Automation.

With the introduction of native WebDriver support in Safari on iOS 13, it’s now possible to run the same automated tests of desktop-oriented web content on desktop and mobile devices equally. Safari’s support comes with new, exclusive safeguards to simultaneously protect user security and privacy and also help you write more stable and consistent tests. You can try out Safari’s WebDriver support today by installing a beta of macOS Catalina and iOS 13.

You can learn more about iOS support for Safari WebDriver by reading the “ WebDriver is Coming to Safari in iOS 13 ”.

Web Inspector Improvements

Web Inspector adds tools that bring new insights to web content during development. This release also includes many tooling refinements with more capabilities and a better debugging experience. Among the changes, Web Inspector has improved performance for debugging large, complex websites.

A new CPU Usage Timeline is available in the Timelines Tab that provides developers with insight into power efficiency through CPU usage. This helps developers analyze and improve the power efficiency of their web content. The Timelines Tab has also been updated to support importing and exporting of recorded timeline data using a JSON file format. The portability of timeline data makes it possible to share recordings with other developers, or use the data in custom tools.

Read more in the “ CPU Timeline in Web Inspector ” blog post. For more tips on developing power efficient web content, you can also read the “ How Web Content Can Affect Power Usage ” blog post.

This release introduces a new Audit Tab to run tests against web content with results that can be easily imported and exported. The Audit Tab includes a built-in accessibility audit for web content and allows developers to create their own audits for custom checks throughout the web content development process.

You can read more in the blog posts for “ Audits in Web Inspector ” and “ Creating Web Inspector Audits ” .

When an iOS or iPadOS device with Web Inspector enabled in Safari’s Advanced Settings is connected to a macOS device running Safari, Web Inspector will offer a new Device Settings menu. The Device Settings menu allows overriding developer-related Safari settings such as the User-Agent string when Web Inspector is connected to the device.

Read more about this in the “ Changing Page Settings on iOS Using Web Inspector ” blog post.

The Elements Tab includes a new Changes sidebar to keep track of CSS changes made in the Styles sidebar, making it easier to capture all of the changes made and re-incorporate them into production code. In the Network Tab, certificates and TLS settings are now available to review in the Security pane of the resources view.

These improvements are available to users running watchOS 6, iOS 13, iPadOS, macOS Catalina, macOS Mojave 10.14.6 and macOS High Sierra 10.13.6. These features were also available to web developers with Safari Technology Preview releases. Changes in this release of Safari were included in the following Safari Technology Preview releases: 77 , 78 , 79 , 80 , 81 , 82 , 83 , 84 , 85 , 86 , 87 , 88 , 89 . Download the latest Safari Technology Preview release to stay on the forefront of future web features. You can also use the WebKit Feature Status page to watch for changes to your favorite web platform features.

We love hearing from you. Send a tweet to @webkit or @jonathandavis to share your thoughts on this release, and any features you were hoping for that didn’t make it. If you run into any issues, we welcome your bug reports for Safari, or WebKit bugs for web content issues.

How-To Geek

How to change your browser's user agent without installing any extensions.

Your changes have been saved

Email is sent

Email has already been sent

Please verify your email address.

You’ve reached your account maximum for followed topics.

Quick Links

Google chrome, mozilla firefox, microsoft edge and internet explorer, apple safari.

If you ever wanted to make your web traffic seem like it was coming from a different browser--say, to trick a site that claims it's incompatible with yours--you can. All popular browsers offer built-in user agent switchers, so you can change your user agent without installing any extensions.

Related: What Is a Browser's User Agent?

Websites identify browsers by their " user agents ". Change a browser's user agent and it will report it's a different browser to websites. This allows you to request web pages intended for different browsers--or even different devices, like smartphones and tablets.

Chrome's user agent switcher is part of its Developer Tools. Open them by clicking the menu button and selecting More Tools > Developer Tools. You can also use press Ctrl+Shift+I on your keyboard.

Click the menu button to the right of the "Console" tab at at the bottom of the Developer Tools pane and select "Network Conditions"

If you don't see the console at the bottom, click the menu button at the top right corner of the Developer Tools pane--that's the button just to the left of the "x"--and select "Show Console".

On the Network conditions tab, uncheck "Select automatically" next to User agent. You can then select a user agent from the list or copy and paste a custom user agent into the box.

This setting is temporary. It only works while you have the Developer Tools pane open, and it only applies to the current tab.

In Mozilla Firefox, this option is buried on Firefox’s about:config page.

To access the about:config page, type

into Firefox’s address bar and press Enter. You’ll see a warning--be careful when you change settings here, you could mess up Firefox’s settings.

into the filter box. We’re looking for the

preference, but it probably won’t exist on your system.

To create the preference, right-click on the about:config page, point to New, and select String.

Name the preference

Enter your desired user agent as the value of the preference. You’ll have to look up your desired user agent on the web and enter it exactly. For example, the following user agent is used by Googlebot, Google’s web crawler:

Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

You can find extensive lists of user agents on various websites, such as  this one .

This setting applies to every open tab and persists until you change it, even if you close and reopen Firefox.

To revert Firefox to the default user agent, right-click the "general.useragent.override" preference and select Reset.

Microsoft Edge and Internet Explorer have user agent switchers in their developer tools, and they're nearly identical. To open them, click the settings menu and select "F12 Developer Tools" or just press F12 on your keyboard.

The developer tools will open in a separate pane at the bottom of the window. Click the "Emulation" tab and choose a user agent from the "User agent string" box. You can also select the "Custom" option in the User agent string list and type a custom user agent into the box. You can find extensive lists of user agents on various websites, such as  this one .

This setting is temporary. It only applies to the current tab, and only while the F12 Developer Tools pane is open.

This option is available in Safari's normally hidden Develop menu. To enable it, click Safari > Preferences. Select the "Advanced" tab and enable the "Show Develop menu in menu bar" option at the bottom of the window.

Click Develop > User Agent and select the user agent you want to use in the list. If the user agent you want to use isn't shown here, select "Other" and you can provide a custom user agent. You can find extensive lists of user agents on various websites, such as  this one .

This option only applies to the current tab. Other open tabs and tabs you open in the future will use the "Default" user agent.

• Control Panel

• Skip to main content
• Skip to search
• Skip to select language
• Sign up for free
• Remember language
• Português (do Brasil)

The User-Agent request header is a characteristic string that lets servers and network peers identify the application, operating system, vendor, and/or version of the requesting user agent .

Warning: Please read Browser detection using the user agent for why serving different Web pages or services to different browsers is usually a bad idea.

Common format for web browsers:

A product identifier — its name or development codename.

Version number of the product.

Zero or more comments containing more details. For example, sub-product information.

Firefox UA string

For more on Firefox- and Gecko-based user agent strings, see the Firefox user agent string reference . The UA string of Firefox is broken down into 4 components:

• Mozilla/5.0 is the general token that says that the browser is Mozilla-compatible. For historical reasons, almost every browser today sends it.
• platform describes the native platform that the browser is running on (Windows, Mac, Linux, Android, etc.) and if it is a mobile phone. Firefox OS phones say Mobile — the web is the platform. Note that platform can consist of multiple ; -separated tokens. See below for further details and examples.
• rv: geckoversion indicates the release version of Gecko (such as " 17.0 "). In recent browsers, geckoversion is the same as firefoxversion .
• Gecko/geckotrail indicates that the browser is based on Gecko. (On the desktop, geckotrail is always the fixed string 20100101 .)
• Firefox/firefoxversion indicates that the browser is Firefox and provides the version (such as " 17.0 ").

Chrome UA string

The Chrome (or Chromium/Blink-based engines) user agent string is similar to Firefox's. For compatibility, it adds strings like KHTML, like Gecko and Safari .

Opera UA string

The Opera browser is also based on the Blink engine, which is why it almost looks the same as the Chrome UA string, but adds "OPR/<version>" .

Older, Presto-based Opera releases used:

Microsoft Edge UA string

The Edge browser is also based on the Blink engine. It adds "Edg/<version>" .

Safari UA string

In this example, the user agent string is mobile Safari's version. It contains the word "Mobile" .

Crawler and bot UA strings

Library and net tool ua strings, specifications, browser compatibility.

BCD tables only load in the browser with JavaScript enabled. Enable JavaScript to view data.

• User-Agent detection, history and checklist
• Firefox user agent string reference
• Browser detection using the user agent
• Client hints

• Home New Posts Forum List Trending New Threads New Media Spy
• WikiPost Latest summaries Watched WikiPosts
• Support FAQ and Rules Contact Us

Still showing as 10.15.

• Thread starter wellander1
• Start date Jun 19, 2021
• Sort by reaction score
• Older macOS Versions
• macOS Monterey (12)

Contributor

• Jun 19, 2021

In Monterey beta 1 the User agent string in in Safari on my M1 Mac shows this Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.0 Safari/605.1.15 Will this ever be fixed?  

No, that's an intentional decision, it's not a bug.  

macrumors G5

216593 – [macos] limit reported macos release to 10.15 series.

• Latest Mac versions:
• Latest user agents:

Navigation Menu

Search code, repositories, users, issues, pull requests..., provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications You must be signed in to change notification settings

A JavaScript library for generating random user agents with data that's updated daily.

intoli/user-agents

Folders and files, repository files navigation, user agents.

Installation | Examples | API | How it Works | Contributing

User-Agents is a JavaScript package for generating random User Agents based on how frequently they're used in the wild. A new version of the package is automatically released every day, so the data is always up to date. The generated data includes hard to find browser-fingerprint properties, and powerful filtering capabilities allow you to restrict the generated user agents to fit your exact needs.

Web scraping often involves creating realistic traffic patterns, and doing so generally requires a good source of data. The User-Agents package provides a comprehensive dataset of real-world user agents and other browser properties which are commonly used for browser fingerprinting and blocking automated web browsers. Unlike other random user agent generation libraries, the User-Agents package is updated automatically on a daily basis. This means that you can use it without worrying about whether the data will be stale in a matter of months.

Generating a realistic random user agent is as simple as running new UserAgent() , but you can also easily generate user agents which correspond to a specific platform, device category, or even operating system version. The fastest way to get started is to hop down to the Examples section where you can see it in action!

Installation

The User Agents package is available on npm with the package name user-agents . You can install it using your favorite JavaScript package manager in the usual way.

The User-Agents library offers a very flexible interface for generating user agents. These examples illustrate some common use cases, and show how the filtering API can be used in practice.

Generating a Random User Agent

The most basic usage involves simply instantiating a UserAgent instance. It will be automatically populated with a random user agent and browser fingerprint.

In this example, we've generated a random user agent and then logged out stringified versions both the userAgent.data object and userAgent itself to the console. An example output might look something like this.

The userAgent.toString() call converts the user agent into a string which corresponds to the actual user agent. The data property includes a randomly generated browser fingerprint that can be used for more detailed emulation.

Restricting Device Categories

By passing an object as a filter, each corresponding user agent property will be restricted based on its values.

This code will generate a user agent with a deviceCategory of mobile . If you replace mobile with either desktop or tablet , then the user agent will correspond to one of those device types instead.

Generating Multiple User Agents With The Same Filters

There is some computational overhead involved with applying a set of filters, so it's far more efficient to reuse the filter initialization when you need to generate many user agents with the same configuration. You can call any initialized UserAgent instance like a function, and it will generate a new random instance with the same filters (you can also call userAgent.random() if you're not a fan of the shorthand).

This code example initializes a single user agent with a filter that limits the platform to Win32 , and then uses that instance to generate 1000 more user agents with the same filter.

Regular Expression Matching

You can pass a regular expression as a filter and the generated user agent will be guaranteed to match that regular expression.

This example will generate a user agent that contains a Safari substring.

Custom Filter Functions

It's also possible to implement completely custom logic by using a filter as a function. The raw userAgent.data object will be passed into your function, and it will be included as a possible candidate only if your function returns true . In this example, we'll use the useragent package to parse the user agent string and then restrict the generated user agents to iOS devices with an operating system version of 11 or greater.

The filtering that you apply here is completely up to you, so there's really no limit to how specific it can be.

Combining Filters With Arrays

You can also use arrays to specify collections of filters that will all be applied. This example combines a regular expression filter with an object filter to generate a user agent with a connection type of wifi , a platform of MacIntel , and a user agent that includes a Safari substring.

This example also shows that you can specify both multiple and nested properties on object filters.

class: UserAgent([filters])

• filters < Array , Function , Object , RegExp , or String > - A set of filters to apply to the generated user agents. The filter specification is extremely flexible, and reading through the Examples section is the best way to familiarize yourself with what sort of filtering is possible.

UserAgent is an object that contains the details of a randomly generated user agent and corresponding browser fingerprint. Each time the class is instantiated, it will randomly populate the instance with a new user agent based on the specified filters. The instantiated class can be cast to a user agent string by explicitly calling toString() , accessing the userAgent property, or implicitly converting the type to a primitive or string in the standard JavaScript ways ( e.g. `${userAgent}` ). Other properties can be accessed as outlined below.

userAgent.random()

• returns: < UserAgent >

This method generates a new UserAgent instance using the same filters that were used to construct userAgent . The following examples both generate two user agents based on the same filters.

The reason to prefer the second pattern is that it reuses the filter processing and preparation of the data for random selection. Subsequent random generations can easily be over 100x faster than the initial construction.

userAgent()

As a bit of syntactic sugar, you can call a UserAgent instance like userAgent() as a shorthand for userAgent.random() . This allows you to think of the instance as a generator, and lends itself to writing code like this.

userAgent.toString()

• returns: < String >

Casts the UserAgent instance to a string which corresponds to the user agent header. Equivalent to accessing the userAgent.userAgent property.

userAgent.data

• appName < String > - The value of navigator.appName .
• connection < Object > - The value of navigator.connection .
• cpuClass < String > - The value of navigator.cpuClass .
• deviceCategory < String > - One of desktop , mobile , or tablet depending on the type of device.
• oscpu < String > - The value of navigator.oscpu .
• platform < String > - The value of navigator.platform .
• pluginsLength < Number > - The value of navigator.plugins.length .
• screenHeight < Number > - The value of screen.height .
• screenWidth < Number > - The value of screen.width .
• vendor < String > - The value of navigator.vendor .
• userAgent < String > - The value of navigator.userAgent .
• viewportHeight < Number > - The value of window.innerHeight .
• viewportWidth < Number > - The value of window.innerWidth .

The userAgent.data contains the randomly generated fingerprint for the UserAgent instance. Note that each property of data is also accessible directly on userAgent . For example, userAgent.appName is equivalent to userAgent.data.appName .

The project follows the Semantic Versioning guidelines . The automated deployments will always correspond to patch versions, and minor versions should not introduce breaking changes. It's likely that the structure of user agent data will change in the future, and this will correspond to a new major version.

Please keep in mind that older major versions will cease to be updated after a new major version is released. You can continue to use older versions of the software, but you'll need to upgrade to get access to the latest data.

Acknowledgements

The user agent frequency data used in this library is generously provided by Intoli , the premier residential and smart proxy provider for web scraping. The details of how the data is updated can be found in the blog post User-Agents — A random user agent generation library that's always up to date .

If you have a high-traffic website and would like to contribute data to the project, then send us an email at [email protected] . Additional data sources will help make the library more useful, and we'll be happy to add a link to your site in the acknowledgements.

Contributing

Contributions are welcome, but please follow these contributor guidelines outlined in CONTRIBUTING.md .

User-Agents is licensed under a BSD 2-Clause License and is copyright Intoli, LLC .

Contributors 3

• TypeScript 75.6%
• JavaScript 22.1%
• Emacs Lisp 2.3%

The latest user agents for web browsers on Android

Updated at: Sep 27, 2024

Android is a popular Operating System for Phones, Tablets and even some laptop computers.

Here you can find the latest user agents for some of the most popular web browsers which run on Android.

Explore our huge user agent listing , download our user agents database , (or you can search it ) if you're curious about other user agents.

Get latest user agents for Android via API

Our Web Browser/Operating System Version Numbers API endpoint will provide you with the latest user agents for all sorts of popular web browsers and operating systems.

Experiment with different user agents

You can use our User Agent Parser page to try out different user agent varieties, or to test if your user agent switcher is working properly.

Database of user agents

If you're interested in our database of many millions of user agents, please check out our API which provides access to our user agent database . You can perform very detailed and specific queries on it to find user agents that match your exact criteria - version numbers, hardware types, platforms and so on.

Update my web browser

Do i need to update my browser.

Find out if your browser is out of date Is my browser out of date?

Why should I update my browser?

There are very good reasons to, find out here! Why update your browser?

Is it free to update Chrome?

Find out about the cost of updating Chrome... Does Chrome cost anything?

Get help with our guides

How to enable javascript.

Change your JavaScript settings Guide to enabling Javascript

How to enable Cookies

Configure your cookie settings for privacy Guide to enabling cookies

Related articles

Web browsers without ai.

Some web browsers manufacturers have started adding AI features to their browsers, others have decided not to. Which web browsers don't have AI in them?

I can't log in to a website.

We've got a detailed guide to help you solve login problems How to fix website log in problems

Why do websites use cookies?

Why are cookies useful? Do you need them? What's the deal with cookies?

Clear Cache, Cookies and History

How to reset your browsing history How to reset your browser

Try a different web browser

Different web browsers have different features - try a different one to see if you prefer it. Experiment a bit!

Use a VPN to hide your IP address

We recommend NordVPN to hide your IP address or to unblock websites. Hide your IP Address