User Agent Parser
Detect your browser, OS, engine, and device type from any user agent string.
About User Agent Parser
Every web browser automatically sends a user agent string with each HTTP request. This string identifies the browser software, the rendering engine powering it, the operating system and its version, and the device type. Web servers and analytics platforms read this string to adapt content, track statistics, and filter bots.
This free online user agent parser decodes any UA string into human-readable components — browser name and version, OS, rendering engine, device type, CPU architecture, and bot detection — instantly in your browser with no data sent to a server.
What This Tool Detects
- • Browser name and version (Chrome, Firefox, Safari, Edge, Opera, Brave, and more)
- • Operating system and version (Windows, macOS, Linux, Android, iOS, ChromeOS)
- • Rendering engine (Blink, WebKit, Gecko, Trident)
- • Device type (Desktop, Mobile, Tablet, Bot)
- • CPU architecture (x86-64, ARM64, ARM, x86)
- • Bot and crawler detection
How to Use User Agent Parser
- 1
View your browser automatically
Open the tool — your current browser's UA string is parsed instantly on the My Browser tab.
- 2
Parse a custom user agent
Switch to the Parse Custom UA tab, paste any UA string (from server logs, a mobile device, or a known bot), and click Parse.
- 3
Read the results
See browser name/version, OS, rendering engine, device type, CPU architecture, and a bot flag displayed in clearly labeled cards.
- 4
Copy the UA string
Use the copy button next to the raw UA string to copy it to your clipboard for use in documentation or bug reports.
User Agent Parser — FAQ
What is a user agent string?
A user agent (UA) string is a line of text that your browser sends to every web server you visit. It identifies your browser, its version, the operating system you are using, and sometimes additional details like the rendering engine. Servers use this information to serve compatible content.
Why would I need to parse a user agent string?
Developers parse user agent strings to detect the visitor's browser and OS for compatibility handling, analytics, or to serve device-specific content. Security analysts use UA parsing to identify bots, scrapers, and suspicious clients in server logs.
Can user agent strings be faked?
Yes. Any browser or HTTP client can send an arbitrary user agent string. This is common in web scraping, privacy browsing, and browser spoofing. You should never rely solely on the UA string for security decisions.
What is the difference between browser engine and browser?
The browser engine (like Blink or WebKit) is the underlying technology that renders HTML and runs JavaScript. The browser (like Chrome or Edge) is the application built on top of that engine. Many different browsers share the same engine — for example, Chrome, Brave, Edge, and Opera all use Blink.
What does "Blink" vs "WebKit" mean?
Blink is a fork of WebKit used by Chrome, Edge, Opera, and most Chromium-based browsers. WebKit is Apple's rendering engine used in Safari and all iOS browsers. Gecko is Mozilla's engine used in Firefox. Each engine has different CSS/JS feature support levels.
How do I change my user agent string?
In Chrome DevTools, open the Network Conditions panel (Menu → More tools → Network conditions) and uncheck "Use browser default" under User agent to type a custom UA. Firefox has a similar setting via about:config (general.useragent.override). Browser extensions can also do this persistently.
Is this tool accurate for all user agents?
This parser covers the most common browsers, OS platforms, and device types using regex pattern matching. Rare or enterprise browsers, very old clients, and highly customized UA strings may not be fully detected. For production use, consider a dedicated server-side UA parsing library.
Pro Tips
- • Paste any UA string from your server logs into the Custom tab to instantly identify unknown clients.
- • Bots and crawlers often send UA strings that match common patterns — check the "Bot" badge.
- • iOS apps (including Chrome and Firefox on iPhone) always use WebKit because Apple requires it.
- • Windows 10 and Windows 11 both report "Windows NT 10.0" in the UA string — they are indistinguishable from the UA alone.