Updated · Built and checked by the PlinzoTools team, formulas tested against published sources
Parse a User-Agent string to identify the browser and operating system.
Unknown
Every browser sends a User-Agent string identifying itself (and often the operating system) with every web request. This tool parses a User-Agent string -- your own by default, or any other you paste in -- to identify the browser name, version, and operating system.
Your own browser's User-Agent loads automatically; edit or replace it with any other User-Agent string to parse. The identified browser and OS appear instantly.
The string is checked against known signature patterns for major browsers (Chrome, Safari, Firefox, Edge, Opera, Samsung Internet, and the Facebook and Instagram in-app browsers) and operating systems (Windows, macOS, iOS, Android, ChromeOS, Linux), in a deliberate priority order -- many browsers include other browsers' names in their User-Agent for compatibility, and every iPhone and iPad string says "like Mac OS X", so the more specific signature is always tested first. The operating system is shown with its version where the string carries one, such as iOS 18.1 or Android 14.
For validating other structured web-related strings, see the URL Validator.
The tool checks browser signatures in a fixed order: the Facebook in-app browser (FBAN, FBAV or FB_IAB), the Instagram in-app browser, Edge (Edg/, EdgA/ or EdgiOS/), Opera (OPR/), Samsung Internet (SamsungBrowser/), Chrome on iOS (CriOS/), Firefox on iOS (FxiOS/), Firefox, the Android WebView, Chrome, and finally Safari, which is recognised by a Version/ token together with Safari/. The version number is taken from the matching token. For the operating system, iPhone, iPad and iPod are checked first, because their strings also contain "like Mac OS X"; then Android, Windows (with NT 10.0 shown as Windows 10/11, 6.3 as 8.1, 6.1 as 7 and so on), ChromeOS, macOS and Linux. Anything not matched shows as Unknown. Because the order matters, browsers built on Chrome's engine are labelled by their own token when they have one, and otherwise fall through to Chrome.
When reporting a bug, paste the exact User-Agent from the user's report and read off the browser and OS. In server logs, use the tool to decode a suspicious or unfamiliar string. For QA, paste different strings to see how a similar detection routine would classify them. Keep in mind that this is only a summary of the header. The header itself can be changed by the sender or by a browser extension, and some devices, such as tablets requesting a desktop site, send a desktop-style string on purpose.
If you are deciding how your website should behave, test for the feature you need, not the browser name. Feature checks keep working when a new browser or version appears, while browser sniffing tends to break silently.
For legacy compatibility reasons -- many browsers historically included other major browsers' names in their User-Agent string so that older websites checking for "Safari" or "Gecko" wouldn't incorrectly block them; this tool checks for Chrome's own signature first to correctly identify it despite that.
Since iPadOS 13, Safari on an iPad requests desktop websites by default and sends a Mac-style User-Agent with no mention of iPad at all, so no parser can tell it apart from a Mac. iPhones, and iPads in mobile mode, include "iPhone" or "iPad" in the string and are correctly reported as iOS.
It covers the major desktop and mobile browsers/OSes in common use; less common or older browsers may not be specifically recognized and would show as "Unknown."
Yes easily -- browsers let users (or automated tools) freely override their reported User-Agent, so this identification should never be relied on for security purposes, only for compatibility/debugging context.
On load the tool fills the box with your own browser's User-Agent, so you immediately see how your current browser is identified. Edit or replace it to test other strings.
Yes. Links opened inside the Facebook or Instagram apps use a built-in browser whose User-Agent carries app tokens, and the tool names it Facebook In-App or Instagram In-App, with the app's version.
Not in this tool, which reports only the browser and operating system. Many crawlers imitate Chrome, so check the raw string for a bot name such as Googlebot or bingbot.
Browsers may report a reduced or rounded version in the header for privacy, so the minor numbers can be zeros or differ from the exact build.
Reference: MDN Web Docs