User-agent parser

Detect and parse Browser, Engine, OS, CPU, and Device type/model from an user-agent string.

Enable JavaScript to use the interactive tool. The guide below explains how it works.

User-Agent Parser: Decode and Understand Browser Identifiers

The User-Agent (UA) string is one of the most complex and historically burdened headers in the HTTP protocol. Originally intended to provide simple information about the client's browser and operating system, years of "browser wars" have turned it into a convoluted string filled with legacy compatibility tokens and contradictory information. The User-Agent Parser tool is designed to cut through this noise, providing a structured, easy-to-read breakdown of what any UA string actually means.

1. What the Tool Does

The User-Agent Parser takes a raw User-Agent string—either from your current browser or one you paste in—and instantly extracts the core technical details. It identifies the Browser (and its version), the Operating System, the Rendering Engine, and the Device Type (Mobile, Tablet, Desktop, or Bot). This transformation from a messy string to structured data allows developers to quickly understand the environment of a specific user or test their application's client-detection logic.

2. Why Developers Use It

3. Step-by-Step Instructions

  1. Navigate to the User-Agent Parser tool.
  2. By default, the tool shows the information for your current browser.
  3. To parse a different string, paste the raw User-Agent into the input field at the top.
  4. Review the generated cards which display:
    • Browser Details: Name and major/minor version.
    • OS Details: Operating system name and version.
    • Engine Details: The rendering engine (e.g., Blink, Gecko, WebKit).
    • Device Info: Manufacturer, model, and type.
  5. Use the "Copy" icon on any field to grab specific details for your reports or code.

4. Examples

5. FAQs

Q: Why do all User-Agent strings start with "Mozilla/5.0"? A: This is a legacy remnant. In the early web, servers would check for the "Mozilla" token to decide whether to serve advanced features. To ensure compatibility, every subsequent browser (including IE, Chrome, and Safari) started their strings with "Mozilla/5.0" to avoid being blocked.

Q: Can I trust the User-Agent string for security? A: No. The User-Agent string is entirely client-controlled and can be easily "spoofed" (faked). Never use it for sensitive security decisions; use it only for UI hints, analytics, and debugging.

6. Common Mistakes

7. Real-World Use Cases

8. Related Tools


Decode the identity of any web client with precision.

All tools

Guides and articles