User Agent Parser
Parse and analyze browser user agent strings
Loading
Loading
Loading
Loading
Raw User Agent
Loading...About the My User Agent
This page shows your user agent string and the browser, version, operating system and device type it reports. It is the fastest way to answer "which browser and version are you on?" in a bug report.
Your user agent is the identification string your browser sends with every request. It is how a server can tell a mobile Safari request from a desktop Chrome one, and it is the first thing anyone triaging a bug report asks for.
The strings themselves are a mess of historical accident. Almost every browser still claims to be Mozilla and includes tokens like AppleWebKit and KHTML that it has no real relationship with, because sites once sniffed for those names and browsers copied them to avoid being locked out.
Because of that, user agent sniffing is unreliable and browsers are actively reducing what they disclose. Feature detection is the right approach in code — check whether the capability exists rather than guessing from a name. To parse a string other than your own, use the user agent parser.
How to use the My User Agent
- Open the page. Your user agent string is read from your browser.
- Read the parsed details. See the browser, version, operating system and device type.
- Copy the raw string. Take it for a bug report or support ticket.
- Parse another string. Use the user agent parser for a string you have been given.
My User Agent features
- Your full user agent string
- Browser and version, operating system and device type
- Rendering engine
- Screen and window dimensions, and pixel ratio
- Copy any value for a bug report
Frequently asked questions
What is a user agent string?
A line your browser sends with every request describing itself — browser, version, engine and platform. It is the fastest answer to "which browser and version are you on?" in a bug report.
Why does Chrome's string mention Safari and Mozilla?
Historical compatibility. Browsers copied each other's identifiers for decades so that servers sniffing for one would not lock them out, and the accumulated result is the mess you see. It is why parsing these strings is unreliable.
Should I use the user agent to detect features?
No. Test for the feature itself instead — the string can be changed by the user, is deliberately frozen or reduced by modern browsers, and tells you nothing reliable about what is actually supported.
What is the pixel ratio telling me?
How many device pixels make up one CSS pixel. A ratio of 2 or 3 means a high-density display, which is why images need to be around twice their display size to look sharp.