User Agent Parser
Parse any user agent string into browser, engine, OS, device, CPU and bot details.
Paste a user agent string above to see the browser, engine, operating system and device.
- Browser
- Unknown
- Engine
- Unknown
- Operating system
- Unknown
- Device type
- Unknown
- Device model
- Unknown
- CPU architecture
- Unknown
- Bot / crawler
- No
Product tokens
How it works
Every browser sends a User-Agent HTTP header describing itself. This user
agent parser breaks that string apart with a set of regular expressions and tells you the
browser and version, the rendering engine (Blink, WebKit, Gecko or Trident), the operating
system and its version, whether the client is a phone, tablet, desktop or a bot, the device
model where the string exposes one, and the CPU architecture. Press "Use my user agent" to
analyse your own browser, or paste any UA string from a log file.
Two caveats worth knowing: Windows 11 still reports itself as Windows NT 10.0,
so it is indistinguishable from Windows 10 in a UA string, and modern browsers freeze or
reduce parts of the string, so a version number can be rounded or a device model replaced by
a placeholder such as "K". User agents are also trivially spoofable — treat them as a hint,
not proof. Parsing runs entirely in your browser: nothing you paste is uploaded, which
matters when the strings come from production access logs.
Frequently asked questions
What is a user agent string?
A user agent is the text a browser or app sends in the User-Agent HTTP header to describe itself: the product tokens for the browser and its version, the rendering engine, the operating system and often the device. Servers and analytics tools read it to decide what to send back. It is a plain string, so this parser simply matches known patterns inside it to work out browser, engine, OS, device type and CPU architecture.
How do I find my user agent?
Open this page and press "Use my user agent" — the box is filled with the exact string your browser is sending right now, and the breakdown appears underneath. You can then copy it as JSON or download it. Because the whole tool runs in your browser, your user agent is never sent to a server or logged anywhere.
Can a user agent string be faked or trusted for device detection?
It can be changed freely — browsers offer device emulation, extensions rewrite it, and scripts set it to anything. Treat it as a hint, not proof: use feature detection or Client Hints for anything important. Also note that Windows 11 still reports "Windows NT 10.0", and reduced user agents replace the Android device model with a placeholder such as "K", so some details are genuinely unavailable.