Inspect your browser user agent
Read the user-agent string locally and understand reduced browser data, compatibility checks and why device detection is unreliable.
Try the calculation or tool
Read what the browser reports
The inspector below displays navigator.userAgent and basic browser-provided values. It runs locally and does not require an IP lookup service. Copy the text when reporting a compatibility problem, but review it before sharing because browser and platform details may be included. A browser user-agent string is not a unique device identity or an authentication credential.
Do not parse names too literally
Modern browsers often include compatibility tokens belonging to other engines. Finding the word Safari in a string does not necessarily mean the browser is Safari. Some browsers reduce or freeze parts of the string to limit fingerprinting, and users or automation can override it. A mobile-looking string does not prove the screen size, touch capability or operating system version.
Test the feature that matters
If the issue concerns file downloads, clipboard access or screen recording, test whether the relevant API exists and works in the current context. Permissions, HTTPS, iframe restrictions and user interaction can matter more than the browser name. Reproduce the smallest failing action and record the exact error. Avoid displaying an “unsupported browser” warning solely because the product name is unfamiliar.
Make a useful bug report
Include the page URL, approximate time, steps, expected result and observed result. State whether extensions or private browsing affect the behaviour. Share a sanitized sample input instead of credentials or private documents. When comparing two browsers, use the same input and viewport. The local values shown here are diagnostic hints; they do not reveal your public IP, precise location or every installed browser component.