User Agent Checker
Your full browser & device fingerprint
Three panels: your own string, the environment around it, and a parser. The first shows the user agent your browser is sending right now and breaks it into browser with major version, rendering engine, operating system and device class, with a copy button for the raw text. The second reads the live Navigator and Screen objects — viewport size and pixel density, interface language and the accepted-language list, platform, logical CPU cores, approximate device memory, touch points, cookie availability, connection state, resolved timezone, Do Not Track and whether the built-in PDF viewer is active. The third accepts any pasted string and decodes that instead, which is how you find out what a log line or a bug report is describing.
See your browser's user agent string parsed into browser, engine, OS and device, plus screen, language, timezone and hardware details. The classic tool for debugging web apps.
Private User Agent Checker In Your Browser
User Agent Checker is processed locally with client-side JavaScript. Your files never touch a server, and there is no queue to wait in.
How to use User Agent Checker
Read the Your user agent panel for the raw string, then the Browser, Engine, Operating system and Device type tiles beneath it.
Scan the Browser & environment details grid for Screen, Language, Languages, Platform, CPU cores, Device memory, Touch points, Cookies, Online, Timezone, Do Not Track and PDF viewer.
Paste a different string into the Parse any user agent box to decode a device that is not the one you are sitting at.
Press the copy button in the first panel's header to put the raw user agent string on the clipboard.
- Every figure is read from the live Navigator and Screen objects, so the values describe this browser rather than a hard-coded lookup table.
- The parser is an ordered rule set that tests the most specific token first, which is why Edge and Opera are not reported as Chrome.
- The custom box decodes a pasted string and reports browser, full version, operating system, device and engine for that string rather than for you.
- No measurement request is made: the panel is assembled from properties the page already holds, with no fingerprinting script and no beacon.
- A developer reads the engine and device class to reproduce a rendering bug without asking the reporter to describe their setup.
- A QA engineer pastes the user agent from a bug report to establish which browser and operating system produced the failure.
- Someone auditing browser disclosure checks which Navigator properties a plain web page can read without asking for permission.