🔍 User-Agent Parser
Parse User-Agent strings into browser, OS, engine, and device hints in your browser.
Last updated: November 8, 2026 · By the BoltQuickTools team
Work out what sent a request from its User-Agent header
Server logs and bug reports often include a long User-Agent string and little else. This page turns one string into a quick reading of browser, operating system, engine and device type, which is useful when triaging a single report or log line.
Parsing a string
Paste into User-Agent String. The result fills in shortly after you stop typing, and Parse runs it immediately. To try it without your own data, pick an entry from Load Sample User-Agent. The eight result cells are repeated as text in Parsed JSON, which Copy JSON copies. Clear resets everything.
The page does not read your own browser's details. If you want those, copy your User-Agent from your browser's developer tools.
Example: Chrome on Windows
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36
returns:
{
"browser": "Chrome",
"browserVersion": "124.0.0.0",
"os": "Windows",
"osVersion": "10/11",
"engine": "Blink",
"deviceType": "Desktop",
"botSignature": "No bot signature",
"platform": "64-bit"
}
The string says Safari, Gecko and AppleWebKit too, because browsers carry those tokens for compatibility. The parser checks Edge and Opera first, then Chrome, then the others, so the most specific match wins.
Where the labels are wrong or vague
The rules are a short list of patterns rather than a device database, and User-Agent strings can be set to anything by the sender. Treat the result as a hint.
| Input | What you get | Why it matters |
|---|---|---|
Chrome on iPhone (CriOS/), Firefox on iPhone (FxiOS/) | Browser: Unknown | Those tokens are not in the rules. The engine still shows WebKit. |
| Samsung Internet | Browser: Chrome, with the Chrome version | Its own token is not checked. |
| Modern iPad Safari | macOS, Desktop | iPads send a Mac-style string by default, and the text cannot distinguish them. |
| Android tablet | Device Type: Mobile | Every Android string is treated as mobile unless it contains tablet. |
A phone model containing "bot", such as CUBOT_X50 | Device Type: Bot, Likely bot | The bot check matches the letters anywhere in the string. |
curl/8.5.0 | Device Type: Desktop, No bot signature | Anything unmatched falls through to Desktop, and command-line clients are not recognised as automated. |
Internet Explorer on WOW64 | Platform: 64-bit | WOW64 actually means a 32-bit browser on 64-bit Windows. |
Platform is also a loose label. It reads "64-bit" only when the string contains Win64, x64 or WOW64, so a 64-bit Linux string with x86_64 shows "Desktop platform".
Reduced versions, Windows 11 and fake bots
Why does Chrome show a version ending in .0.0.0?
Chrome now sends a reduced User-Agent that hides the minor version numbers, so those zeros are in the string itself and not added by this page.
Why does Windows 11 show as "10/11"?
Both versions send Windows NT 10.0, so the string cannot separate them.
Can this verify that a visitor really is Googlebot?
No. Any client can send that string. The sample reports Device Type Bot, with browser, OS and engine all Unknown, but real verification needs a reverse DNS check on the requesting IP address, which the DNS lookup can help with.
How do I send a request with a specific User-Agent?
Set the header in a curl command, then use curl to code to convert it for your language. If you are writing your own matching rules, try them in the regex tester.