tigtools

User Agent Parser

See what a User-Agent string says about the browser, operating system and device. Your current browser's string is filled in to start.

Runs in your browser No sign-up

User-Agent strings are easy to change or fake, and modern browsers freeze parts of them (for example Windows 11 still reports Windows NT 10.0, and Android often reports the model as “K”). Use the result as a hint, not as proof. User-Agent Client Hints give more reliable details where the browser supports them.

How to use it

  1. Your browser's User-Agent is filled in automatically. To check another one, paste it from a server log, an analytics report or a support ticket.
  2. Read the browser and version, rendering engine, operating system, device type and, for Android, the model code.
  3. Use “Try a bot” or paste a crawler string to see how bots are recognised.
  4. In a Chromium-based browser, compare with the Client Hints shown below the result.

How it works

The parser applies an ordered list of hand-written rules. Bots and HTTP tools are checked first (Googlebot, Bingbot, YandexBot, Applebot, GPTBot, ClaudeBot, social media link previewers, SEO crawlers, curl, Wget, Python requests, Postman and others), then any string containing words such as bot, crawler or spider. Browsers are checked from the most specific to the most generic, because almost every browser copies tokens from others: Edge, Opera, Samsung Internet, Yandex, Vivaldi and UC Browser all contain “Chrome/”, and Chrome contains “Safari/”, so Chrome and Safari are only reported when nothing more specific matches.

The engine is Blink for Chromium-based browsers, Gecko for Firefox, WebKit for Safari, Trident for Internet Explorer and EdgeHTML for the old Edge. On iPhone and iPad every browser uses WebKit, because Apple required it, so Chrome on iOS shows WebKit. Windows versions come from the NT number; Windows 10 and 11 both send NT 10.0 and cannot be told apart from the string. For Android the model code (for example SM-S918B) is shown when present, with the maker for common prefixes.

User-Agent strings are not reliable evidence. Any client can send any string, privacy tools change it, and browsers now reduce it on purpose: Chrome on Android sends “Android 10; K” instead of the real version and model, and iPads send a Mac string. User-Agent Client Hints (Sec-CH-UA headers and navigator.userAgentData) are the more reliable, structured replacement in Chromium browsers; for your own browser they are shown below the result when available.

Examples

Checking a suspicious log entry

A server log shows thousands of requests claiming to be Googlebot. The parser confirms the string is a Googlebot string, and the note reminds you to verify the IP with reverse DNS, because the string alone can be faked.

Reproducing a customer's bug

A support ticket includes “Mozilla/5.0 (Linux; Android 14; SM-S918B) … SamsungBrowser/25.0 Chrome/121…”. The parser shows Samsung Internet 25 on Android 14, a Samsung SM-S918B phone, so you test in that browser rather than in Chrome.

Seeing your own browser

Open the page to see your own browser, engine and OS, and, in Chrome or Edge, the Client Hints with the real platform version, for example Windows 15.0.0 for Windows 11.

Frequently asked questions

Why does it say “Windows 10 or 11”?

Both send “Windows NT 10.0” in the User-Agent, so the string cannot tell them apart. In Chromium browsers, the Client Hints platform version tells them apart: 13.0.0 and above means Windows 11.

Why is Brave shown as Chrome?

Brave sends the same User-Agent as Chrome on purpose, to blend in with Chrome users. Several privacy-focused browsers do the same, so they cannot be told apart from the string.

Is it possible to detect the exact phone model?

Only sometimes. Many Android browsers include a model code, but Chrome now sends “K” in its place. iPhones never include the model. Client Hints can provide the Android model when a site asks for it.

Is my User-Agent sent to your server by this tool?

The tool reads it from your browser and parses it on the page. It is not sent anywhere by the tool. Note that every website you visit, including this one, receives your User-Agent in normal HTTP requests.

Privacy

Parsing happens only in your browser. The strings you paste and the Client Hints shown are not sent anywhere by this tool, stored or included in analytics.