What's the Latest Version of Chrome User Agents?

User Agent Chrome – What You Need to Know

Keeping track of your Chrome user agent string ensures you’re getting the right experience, whether you’re testing web compatibility, protecting your privacy, or troubleshooting site issues. If you’re wondering what your current UA string is, how to view it, or even spoof it, you’re in the right place.

What’s Chrome’s Current User Agent String?

As of April 25, 2025, for the stable release of Chrome 134.0.6998.31 on Windows 10, the typical UA string is:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36

This string identifies your browser version, rendering engine, and operating system in every HTTP request.

Latest Chrome User Agent Strings by Operating System

Chrome sends a slightly different user agent string on each operating system. Modern Chrome uses the reduced user agent format: the browser reports only its major version and freezes the minor, build, and patch numbers to 0.0.0 (for example Chrome/134.0.0.0). It also freezes most operating system details, so a string identifies the platform family rather than the exact OS build. This reduction is deliberate — it limits the passive fingerprinting and cross-site tracking that a highly detailed UA string used to enable.

Here are representative Chrome user agent strings for each major platform. The major version shown here (134) increments with every Chrome release, roughly every four weeks — the live tables at the top of this page always reflect the current strings pulled from Google's release data.

A few things worth knowing about how these strings behave:

• Windows 10 and Windows 11 look identical. Both report Windows NT 10.0, so a parser — or a lookup service such as WhatIsMyBrowser — cannot tell the two releases apart from the UA string alone.
• macOS is frozen at 10_15_7. Every recent macOS release (Sonoma, Sequoia, and newer) reports the same Intel Mac OS X 10_15_7 token regardless of the version actually installed.
• Android reports a generic device. The reduced format replaces the real model name and Android version with Android 10; K on most builds.
• iOS uses CriOS, not Chrome. Because every iOS browser runs on Apple's WebKit engine, Chrome for iOS identifies itself with the CriOS token and a Safari/WebKit signature.

How to Check Your Chrome User Agent

Not sure what UA string your browser is sending? Here’s how to find out:

• chrome://version
  • Open Chrome and navigate to chrome://version.
  • Look for the User Agent line to view the full string.
• Developer Tools Console
  • Open Developer Tools (Ctrl + Shift + I on Windows/Linux or ⌘ + Option + I on Mac).
  • In the Console tab, type navigator.userAgent and press Enter.

Both methods reveal exactly what Chrome reports to websites.

How to Change or Spoof Your Chrome User Agent

Want to see how a site behaves on a different device or browser version? Override Chrome’s UA in a few clicks:

• Open Developer Tools.
• Select the three‑dot menu in the tools panel, then choose More tools → Network conditions.
• Under User agent, uncheck Select automatically.
• Choose a preset UA or enter your own custom string.
• Refresh the page to apply the new UA.

This lets you simulate virtually any browser or device without additional software.

Best Chrome Extensions for Switching User Agents

Chrome's built-in DevTools override (above) is ideal for a quick, one-off test, but it only lasts while DevTools stays open and applies to a single tab. If you switch user agents often — or want a spoofed UA to persist across sessions and apply to every request — a dedicated Chrome extension is the better fit. Two options from the Chrome Web Store are widely used:

• User-Agent Switcher and Manager: A popular open-source extension that lets you pick from a large library of preset browser and OS user agents or enter a custom string. It can apply the spoofed UA to specific domains, keep it active across restarts, and reset to the default with one click.
• User-Agent Switcher for Chrome: A lightweight switcher with quick presets for common browsers and devices — handy for rapidly cycling through mobile, tablet, and desktop identities while checking responsive behavior.

Extension vs. DevTools: which should you use?

• Use DevTools when you need a temporary override for a single tab during a debugging session and don't want to install anything.
• Use an extension when you need the user agent to persist across page loads and sessions, apply to every tab or to specific domains, or want to switch between saved profiles quickly.
• Use automation (see below) when the switching needs to be scripted, repeatable, or run across many pages — for example web scraping or automated cross-browser tests.

How to Programmatically Rotate Chrome User Agents in Selenium, Puppeteer, and Playwright

For automated testing and web scraping, you'll usually set — and often rotate — the Chrome user agent in code. Cycling through a pool of realistic UA strings helps distribute automated requests and lets you check how a site responds to different browsers and devices. Here's how to set the Chrome user agent in the three most common automation frameworks.

Selenium (Python)

Pass the string with the --user-agent switch on ChromeOptions. To rotate, loop over a list and start a fresh driver for each string:

from selenium import webdriver

user_agents = [
    "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36",
    "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36",
    "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36",
]

for ua in user_agents:
    options = webdriver.ChromeOptions()
    options.add_argument(f"--user-agent={ua}")
    driver = webdriver.Chrome(options=options)
    driver.get("https://www.example.com")
    print(driver.execute_script("return navigator.userAgent"))
    driver.quit()

Puppeteer (Node.js)

Puppeteer exposes page.setUserAgent(), so you can change the UA on each new page:

const puppeteer = require('puppeteer');

const userAgents = [
  'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36',
  'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36',
];

(async () => {
  const browser = await puppeteer.launch();
  for (const ua of userAgents) {
    const page = await browser.newPage();
    await page.setUserAgent(ua);
    await page.goto('https://www.example.com');
    await page.close();
  }
  await browser.close();
})();

Playwright (Node.js)

Playwright sets the user agent per browser context, which keeps each rotated identity fully isolated (cookies, storage, and cache):

const { chromium } = require('playwright');

const userAgents = [
  'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36',
  'Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Mobile Safari/537.36',
];

(async () => {
  const browser = await chromium.launch();
  for (const ua of userAgents) {
    const context = await browser.newContext({ userAgent: ua });
    const page = await context.newPage();
    await page.goto('https://www.example.com');
    await context.close();
  }
  await browser.close();
})();

Rotating the user agent only changes the header Chrome reports; other automation fingerprints (such as the navigator.webdriver flag) remain, so pair UA rotation with the other stealth techniques your test or scraping framework recommends.

Why Customize Your Chrome User Agent?

• Compatibility Testing: Verify layouts and features across different browsers and devices.
• Privacy: Reduce fingerprinting by spoofing a more generic UA.
• Development: Emulate mobile or legacy environments directly from your desktop.
• Debugging: Pinpoint issues tied to specific UA strings.

Looking Ahead: User-Agent Client Hints

The web is moving toward a more privacy‑focused approach known as User‑Agent Client Hints. Rather than sending one long string on every request, Chrome shares only the details a site explicitly asks for, through request headers such as Sec-CH-UA, Sec-CH-UA-Platform, and Sec-CH-UA-Mobile. Low-entropy hints such as the browser brand, platform, and a mobile flag are sent by default, while high-entropy details like the full version and CPU architecture are only delivered when the server requests them. On the client side, the same information is available in JavaScript through the navigator.userAgentData API — for example, navigator.userAgentData.getHighEntropyValues() returns the detailed values a site would otherwise parse out of the UA string. As Chrome continues its regular release cycle every 4–6 weeks, your UA string and how you work with it may evolve. Bookmark this page to stay informed about any changes.

What is my User Agent?