Category: Developer tools

user agent parser

System ideaMissing a tool?

Break a UA string into browser, engine, OS and device

Paste a User-Agent header and locally parse browser version, rendering engine, operating system and device type.

BrowserChrome 128.0.0.0Rendering engineBlink 128.0.0.0Operating systemWindows 10/11Device typeDesktop

Everything on this page is processed in your browser. Nothing is uploaded.

What this tool does

This user agent parser accepts any pasted User-Agent header, or your current browser's string, and shows browser name and version, rendering engine, operating system and device type. Parsing happens in the browser and is not uploaded to LocalTools. Treat results as debugging hints, not security identity.

How to use it

  1. Paste a User-Agent string or use your current browser's.
  2. Review browser, version, engine, operating system and device type.
  3. Try the example string to see desktop browser detection.

Privacy

This tool runs entirely in your browser. Your input is never uploaded, stored or shared — closing the tab removes it.

Frequently asked questions

What information is usually inside a User-Agent string?
It commonly includes browser and version, operating system, rendering engine and device-related tokens.
How do I parse browser, OS and device type from a UA?
Paste the string and the tool uses pattern matching to extract browser, OS, device type and engine fields.
Why should User-Agent parsing not be used as a security check?
User-Agent strings can be changed or spoofed, so they are useful clues but not proof for access control.
Does this User Agent parser upload the UA string I paste?
No. The UA string and result are processed locally in your browser and are not uploaded to LocalTools.
What device detection or security decisions does this UA parser not support?
It does not perform reliable bot verification, IP reverse DNS, full Client Hints collection, access control or fraud decisions.