User-Agent Parser
Identify browser, OS and device hints from a user-agent string.
How to use User-Agent Parser
Identify browser, OS and device hints from a user-agent string.
- Select Load example or paste your own test input.
- Choose Run and review the available options.
- Run the selected action; review any validation message.
- Inspect the output before copying, printing or downloading it.
A small example
Input:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36
Example output:
{
"ua": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36",
"browser": {
"name": "Chrome",
"version": "130.0.0.0",
"major": "130"
},
"engine": {
"name": "Blink",
"version": "130.0.0.0"
},
"os": {
"name": "Windows",
"version": "10"
},
"device": {},
"cpu": {
"architecture": "amd64"
}
}When the result looks wrong
A user-agent string can be spoofed or reduced. Reported browser/device hints are not verified identity or exact device detection.
Questions about User-Agent Parser
Is my input uploaded?
File and text processing runs in your browser. Opening the website still loads application assets from its host.
What if the result looks wrong?
A user-agent string can be spoofed or reduced. Reported browser/device hints are not verified identity or exact device detection.
Can I use sensitive production data?
Prefer non-sensitive test data. Never paste live access tokens, passwords or confidential documents into a site without assessing its code and environment.
Supported input and output
Text input; check the selected action and example for the expected syntax.
See the result panel and available copy or download controls for the selected action.
