Start a project

Tool 69 of 100 · HTTP

User-Agent Parser

Paste a User-Agent string, or thousands from a log, and see the browser, engine, operating system, device type and any bots or AI crawlers.

Use the tool All developer tools Live · free
User-Agent Parser at a glanceIllustration: 1, User-Agent strings; 2, processed in your browser; 3, Browser, OS, device.User-Agent Parser1User-Agent strings3Browser, OS, device2In yourbrowser
1 User-Agent strings 2 processed on your device 3 Browser, OS, device

User-Agent Parser

User agents

First line in detail

Value

    Client Hints (your browser only)

    HintValue

    Summary

    Browsers

      Operating systems

        Bots and tools

          Parsed as CSV

          01

          What it does

          Reads browser, engine, OS, device type and bots from User-Agent strings, and summarises a pasted log column.

          • Chrome, Safari, Firefox, Edge, Samsung and in-app browsers
          • Blink, WebKit and Gecko engines
          • Windows, macOS, iOS, Android, Linux and ChromeOS
          • Search, AI and monitoring bots

          02

          Private by design

          Everything happens in your browser. Nothing you type, paste or upload is sent anywhere, and it keeps working offline once the page has loaded.

          03

          What you get

          A parsed table and a CSV, with a Copy and a Download button on every result.

          • User-Agent
          • Bots
          • Logs
          • Analytics

          Why it matters

          User-Agent strings are a mess of history: every browser claims to be Mozilla, Chrome claims to be Safari, and Chrome now freezes parts of the string, so a Windows 11 PC still says 'Windows NT 10.0'.

          This parser reads the parts that are still meaningful, explains the frozen ones, and flags search engines, AI crawlers and other bots. Paste a column from your access logs to see the browser, OS and bot mix at a glance.

          How it works

          1. InputOne or more User-Agent strings
          2. In your browserMatched against browser, engine and bot rules
          3. OutputA table with a summary, and CSV

          Where it fits in a designer's workflow

          1. Plan
          2. Design
          3. Build
          4. Test
          5. Launch
          Reading access logs and analytics exports.

          By the numbers

          The sample User-Agent strings, parsedMicrosoft Edge on Windows: 125 characters; Mobile Safari on iOS: 135 characters; Chrome on Android: 111 characters; Samsung Internet on Android: 138 characters; Firefox on macOS: 84 characters; : 72 characters; : 102 characters; : 10 charactersMicrosoft Edge on Windows125 charactersMobile Safari on iOS135 charactersChrome on Android111 charactersSamsung Internet on Android138 charactersFirefox on macOS84 characters72 characters102 characters10 characters
          Parsed by this tool's own rules. Nearly every string starts with Mozilla/5.0 for historical reasons, and Chrome now freezes the OS and version details, so the browser name is reliable but the exact version often isn't. Source: MDN: User-Agent.
          Show the numbers as a table
          BrowserEngineOSDeviceBot
          Microsoft EdgeBlinkWindowsdesktopno
          Mobile SafariWebKit (all iOS browsers use WebKit)iOSmobileno
          ChromeBlinkAndroidmobileno
          Samsung InternetBlinkAndroidmobileno
          FirefoxGeckomacOSdesktopno
          botyes
          WebKitbotyes
          botyes

          How to use it

          1. Paste a User-Agent string, or press 'Add my browser'.
          2. Read the browser, engine, OS and device.
          3. For logs, paste one User-Agent per line.
          4. Download the parsed table as CSV.

          FAQ

          Why does it say Windows 10 on Windows 11?

          Browsers froze that part of the string. Only User-Agent Client Hints (Sec-CH-UA-Platform-Version) can tell them apart.

          Can it detect every bot?

          It knows the common search engines, AI crawlers, social previewers, uptime monitors and HTTP libraries. Bots that pretend to be browsers can't be spotted from the string alone.

          Should I use User-Agents for feature detection?

          No. Test for the feature in JavaScript or CSS. Use the User-Agent for analytics and bot handling.

          Is anything sent?

          No. Everything is parsed in your browser.

          Work with me

          Want a site that gets these right?

          I build fast, accessible websites and web apps that pass these checks from day one. Tell me about your project and I'll reply personally with honest next steps.

          Start a project What I do

          All developer tools · Back to leej.uk