User-Agent Inspector
Inspect the current or pasted user-agent string locally.
Read the guideRun the tool
The calculation runs in your browser. This tool does not send your input to JVR Software.
More information
Back to the toolWhat it is and when to use it
A user-agent string is a client’s self-reported description. User Agent Info makes an example or the current browser’s string easier to inspect. It is useful when comparing what a browser reports during testing or checking why an old integration classified a device unexpectedly.
How it works
Browser user-agent strings contain identifiers, version-like tokens and historical compatibility text. Multiple modern browsers can share many of those tokens because they use related browser engines or preserve compatibility with older sites. Some browsers intentionally reduce details to limit tracking.
How to use it
- Use the current value or paste an example copied from a controlled test.
- Inspect the display for recurring family and platform markers.
- Check the actual capabilities you need in that browser when making a website behavior decision.
Worked example
A Chromium-based browser can include both Chrome and Safari in its user-agent text. A standard Edge marker may appear alongside similar compatibility tokens. Seeing Safari text therefore is insufficient to establish which browser produced the request.
Reading the result
Treat any inferred browser family or device as provisional. A desktop-mode setting, automated client or privacy option can change the text. When you need to know whether a browser supports a feature, use browser feature detection and test actual behavior on representative devices.
Common mistakes and limits
User agents can be altered by the client and are unsuitable for authentication or authorization. Use layout responsiveness and progressive enhancement instead of tying normal navigation to a particular user-agent label. Remove unrelated unique identifiers before sharing diagnostic logs.
