User-Agent Parser
Classify browser, operating system, platform and engine clues in an HTTP User-Agent string with Bowser. Paste a string or explicitly load the value from your current browser. The result is an inference from a string, not a hardware specification or a browser feature test.
Key features
- Separate browser, OS, platform and engine JSON groups
- Load the current browser’s User-Agent on request
- Omit unknown properties instead of inventing values
- Up to 4,096 input characters and a copyable JSON result
How to use
- Paste only the User-Agent value, or press Load current browser.
- Press Run to parse the string.
- Review browser, os, platform and engine with the inferred flag.
- Copy the result if needed and compare another sample.
Use cases
- Identify browser families in access log samples
- Compare mobile and desktop User-Agent examples
- Turn a browser support report’s supplied string into structured JSON
Frequently asked questions
Can the result differ from the real device?
Yes. Browsers may change or reduce information for compatibility and privacy, and the string can be spoofed. The inferred flag means that the result comes from interpreting a string.
Why are some values missing?
Properties the parser cannot identify are omitted. If no group is recognized, an error is shown. A missing property does not prove the device or feature is absent.
Does the tool read my browser automatically?
Opening the page does not fill the input. The Load current browser button copies navigator.userAgent into the input, and Run performs the analysis.
Does it collect Client Hints?
This tool parses only the supplied User-Agent string. It does not request high-entropy Client Hints, IP location, screen dimensions or device permissions.
Can this determine supported browser features?
The result cannot confirm WebGL, media formats, touch support or other capabilities. Applications should separately use feature detection and verify actual behavior.
Can I paste an entire request log?
Paste only the User-Agent value, within 4,096 characters. Full headers, cookies and authentication values are unnecessary. Browsers often include multiple compatibility tokens, so individual words should not be read as independent facts.
Privacy
Parsing runs in your current browser. The tool does not send the string or output to a server or write them to browser storage. Your current browser string is read only when you press its button.
Comments & questions