Skip to content

Free User Agent Parser

Parse user agent strings to identify browser, operating system, device type and version. Also detects your current browser. Free, with no sign-up required — everything happens right in your browser, so nothing you enter is sent to a server.

💻 User Agent Parser

How the User Agent Parser Works

Paste a user agent string, or press Use My Browser's UA to insert the one your browser is sending, and press Parse. The tool matches the string against patterns for common browsers, rendering engines, operating systems and device types, and shows the browser name and version, the engine, the operating system and the kind of device, such as desktop, mobile or tablet.

User agent strings are messy for historical reasons. Almost all of them begin with Mozilla/5.0 and mention several other browsers so old websites would treat them as compatible, which is why Chrome's string contains Safari and Edge's contains Chrome. The parser checks the most specific names first for that reason. It is built from pattern rules, so very new or unusual clients may be misidentified, and browsers are now reducing the detail in the string. Anyone can set a user agent to any text, so use it for analytics and layout decisions, never for security.

Practical Use Cases

  • Find out which browser and operating system a visitor or log entry used.
  • Debug a layout issue that appears only on a particular device or browser.
  • Check what your own browser reports to websites.
  • Make sense of user agent strings in server logs and analytics exports.

Frequently Asked Questions

It is a line of text that browsers and apps send with each request to identify themselves, including their name, version, operating system and rendering engine.
For historical compatibility. Browsers copied each other's names so that websites designed for one would serve content to the others. The real browser is usually named last or most specifically.
Yes. Anyone can change them, and bots often copy common browser strings. Do not rely on them for security decisions.
Not always. The tool uses pattern matching, so new browsers, in-app browsers and custom clients can be misidentified. Browsers are also shortening the information they reveal.
No. The parsing is done in your browser, and nothing you paste is sent to a server.