User Agent Parser
Detect and display current browser name, version, OS, device type from the User-Agent string.
User Agent Parser
Automatically detects your current browser information and allows testing of custom User-Agent strings. Perfect for QA testing and browser compatibility debugging.
Test Custom User-Agent String
Quick Test Examples
Parsing History (Last 10)
💡 Tips
- • Use this tool to test how your website detects different browsers and devices
- • QA testers can verify browser compatibility across different User-Agent strings
- Your inputs are not collected or stored
- • Click on history items to quickly reload and test previous User-Agent strings
Related tools
User Agent Parser – Browser Detection Made Simple
The User Agent Parser is an essential developer tool that instantly analyzes User-Agent strings to extract detailed information about browsers, operating systems, devices, and rendering engines. Perfect for QA testing, browser compatibility debugging, and web analytics validation.
What is a User-Agent String?
A User-Agent string is a text identifier that web browsers send to websites, containing information about the browser type, version, operating system, and device. This tool parses that string into human-readable components for easy analysis.
Key Features
- Automatic Detection: Instantly shows your current browser information on page load
- Manual Testing: Test any User-Agent string for compatibility debugging
- Comprehensive Parsing: Extracts browser, OS, device type, and rendering engine
- Export Options: Copy results as JSON or plain text for documentation
- History Tracking: Keeps track of recently parsed User-Agent strings
- Example Library: Quick-test common browser/device combinations
Perfect for Developers and QA Teams
This tool is invaluable for web developers, QA testers, and support teams who need to:
- Debug browser-specific compatibility issues
- Test responsive design across different devices
- Validate analytics and tracking implementations
- Document browser support for bug reports
- Understand user environment for support tickets
Privacy & Security
We do not collect or store what you enter.
💡 Pro Tip
Use this tool during cross-browser testing to quickly identify which browser and version your users are experiencing issues with. The parsed information can be invaluable for bug reports and compatibility documentation.
How to Use the User Agent Parser
- 1See your own browser: The tool reads your browser's User-Agent string when the page opens and shows the browser, version, operating system, device type and engine.
- 2Test another User-Agent: Paste any User-Agent string, for example from a server log or bug report, into the manual testing box to parse it.
- 3Try the examples: Click an example such as Safari on iPhone or Samsung Internet on Android to see how common browsers identify themselves.
- 4Copy the result: Copy the parsed result as JSON or the raw string for documentation or a bug report.
- 5Reuse your history: Your last 10 parsed strings are kept in this browser; click one to parse it again, or export the list as JSON.
Frequently Asked Questions
What is a User-Agent string?
A line of text every browser sends in the User-Agent HTTP header to say which browser, version, operating system and device it runs on. For example, Chrome on Windows sends "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36".
Why does almost every User-Agent start with Mozilla/5.0?
For historical compatibility. In the 1990s, sites sent better pages to Netscape (Mozilla), so other browsers copied its token, and later browsers copied each other's. That is why Chrome also mentions Safari, AppleWebKit and Gecko.
Why does Windows 11 show as Windows 10/11?
Windows 11 browsers still send "Windows NT 10.0", exactly like Windows 10, so the User-Agent string alone cannot tell them apart. Sites that need the difference ask for the platform version through User-Agent Client Hints (Sec-CH-UA-Platform-Version) in Chromium browsers.
Why is my Mac version shown as 10.15?
Safari, Chrome and Firefox freeze the macOS version at 10.15 (Catalina) in the User-Agent string for privacy and compatibility, so any recent macOS release appears as 10.15.
Why is Chrome on my iPhone reported with the WebKit engine?
Apple requires every browser on iPhone and iPad to use WebKit, Safari's engine, so Chrome (CriOS), Firefox (FxiOS) and Edge on iOS all render with WebKit even though their names differ.
Can a User-Agent string be faked?
Yes. Any browser, script or bot can send any User-Agent, and browser developer tools include a switcher for testing. Use it for statistics and compatibility hints, not for security decisions.
Is the User-Agent string being replaced?
Partly. Chromium browsers now reduce the detail in the string and offer User-Agent Client Hints, which let a site request the exact platform version, device model or full browser version only when it needs them. Firefox and Safari still send a traditional, partly frozen string.
Related Tools
HTTP Status Code Lookup
Searchable encyclopedia of all HTTP status codes with descriptions, use cases, and examples.
JSON Formatter & Beautifier
Beautify or minify JSON, highlight syntax errors, and explore nested structure with tree view.
Base64 Encoder/Decoder
Convert text to/from Base64 strings.
Base32 Encoder / Decoder
Encode and decode text using Base32 — used in 2FA secrets and legacy systems.
CSV to JSON Converter
Parse CSV text or files into structured JSON. Preview table, download JSON, copy to clipboard.
YAML to JSON Converter
Paste YAML data and instantly convert it to valid JSON with syntax highlighting and error checking.
UUID / CUID Generator
Generate UUIDs (v1, v4), CUIDs, and NanoIDs for testing. Copy single or bulk output.
JSON Validator
Check JSON for syntax errors.
URL Encoder/Decoder
Convert special characters in URLs to %xx format.
JWT Debugger
Decode and inspect JSON Web Tokens instantly.
JSON to CSV
Flatten JSON objects into spreadsheet file.
XML to JSON
Translate XML data into modern JSON format.