We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Parse User-Agent strings from HTTP request headers to extract detailed technical information, including browser, operating system, and device type.
Enter UserAgent to start parsing
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
A User-Agent is a text field that can accompany an HTTP request and identify software making the request. Paste one string to see a browser label and version when recognized, an operating-system label, a broad device label, and the original string. The page starts with the current browser’s reported value; you can replace it with a string from a log or support report.
This is a small rule-based reader, not a full device database. It checks for Firefox, Edge, Chrome, or Safari tokens; operating-system labels are limited to Windows, macOS, Linux, Android, iOS, or Unknown; device labels are Desktop, Mobile, or Tablet. It does not identify bots, device models, screen size, IP addresses, or location. RFC 9110 describes the header’s general purpose, while browser strings may include compatibility tokens that make simple parsing ambiguous.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Take the User-Agent value from a request log or support report. Paste the value itself, without neighboring log fields. The tool handles one string at a time.
The input is initially filled with the browser’s reported User-Agent. Use the provided action to reload that value, or paste another string over it. The summary updates as the input changes.
Check the browser, version, operating system, and device labels against the original tokens. An Unknown label means the string did not match this page’s limited checks; it does not prove the value is invalid.
Copy the browser/version or other displayed field as a brief clue, and retain the raw string when exact troubleshooting context matters.
For instance, a string containing Chrome/ may be labeled Chrome even if a related browser token is also present. The parser checks selected tokens in a fixed order rather than resolving every browser family.
Use cases
See how the tool fits into real work and everyday tasks.
Turn a long value in a user report into a compact browser and device summary before attempting a reproduction.
Read one request’s user-agent field more easily. This page does not process a batch or produce analytics.
Use the labels to guide a manual browser test, then verify the reported issue on the actual browser and device where possible.
Q&A
Find concise answers to common questions and confusing cases.
Some mobile User-Agent strings contain both mobile and desktop-style tokens. The parser checks Windows, Mac, and Linux before Android or iOS, so an earlier token can determine the displayed operating-system label.
Only a few browser tokens are recognized. The device starts as Desktop, changes to Mobile when the string contains Mobile, and changes to Tablet when it contains Tablet or iPad. Other strings may not fit those checks.
No. It is a reported text value, not proof of identity or authorization. It can be altered and should not be used alone for access control, fraud decisions, or unique-device identification.
Notes
Review scope, result limitations, and important precautions before use.
Browser detection from User-Agent text is an imperfect compatibility clue. For application behavior, test for the feature you need rather than treating a parsed label as definitive.
Related
Discover related tools, collections, and available API capabilities.