WHAT IT DOES
Turn an opaque User-Agent into a cautious reading.
Paste a User-Agent string to identify likely browser, operating system, device class, architecture, and automation markers. The parser uses transparent local signatures and labels uncertain or unrecognised fields instead of pretending a heuristic is a guarantee.
Why use it?
Use it to interpret client-identification text from a log while keeping heuristic matches separate from facts about the device.
How to use this tool
- Paste one User-Agent string and parse it.
- Compare the browser, operating system, device, and automation fields with the raw tokens. For example, a curl marker identifies what the string claims, not proof of the client process.
- Use missing or uncertain fields as a limit of the evidence, not a reason to invent a device identity. No client is contacted or fingerprinted by this tool.
Details and limitations
- Common Chromium, Firefox, Safari, Edge, Opera, curl, Googlebot, Windows, macOS, Linux, Android, and iOS tokens are read locally.
- The result separates browser, device, automation, and raw-token sections so a copied field can be checked against the original string.
- A User-Agent is self-declared client text: the result describes matching tokens and is not proof of the actual browser, device, or person behind a request.
- Control characters, empty input, and implausibly large pasted strings are rejected before parsing.