What Is My Browser

"What browser am I using?" is a question that seems simple but has a surprisingly complex answer — and it is one of the most common pieces of information requested by technical support, IT helpdesks, and web developers when troubleshooting a problem. It is not just "Chrome" or "Firefox"; it is a specific version, on a specific operating system, at a specific screen resolution, with specific settings (cookies, language, timezone, do-not-track) that can all affect how a website behaves. This tool answers every dimension of that question at once, reading all the relevant properties from the browser\u0027s own navigator, screen, and window APIs — no network request, no server, no guesses.\n\nThe information collected falls into several categories. Identity: what browser and what version does the user agent string report? (Chrome 126 on Windows 10/11, Safari 17 on macOS 14, Firefox 129 on Linux). Display: what is the screen resolution, colour depth, and pixel ratio? (1920x1080, 24-bit colour, 2x Retina). What is the actual viewport size right now? (the browser window could be smaller than the screen). Environment: what language does the browser prefer? (en-GB, de-DE). What timezone is the system set to? (Europe/London, America/New_York). Are cookies enabled? (most sites break without them). Is the browser currently online? (navigator.onLine — a live check). Privacy: has the user set Do Not Track? (mostly ignored by sites now, but still a browser setting). And finally, the raw user agent string itself — the complete text the browser sent to load this very page, which is the piece of data support teams most commonly ask for.\n\nAll of this runs locally in the browser by reading properties from navigator, screen, and window objects — the standard JavaScript APIs that every browser exposes. Nothing is transmitted to a server, inferred from an IP address, or guessed from a database. The results are as accurate as the browser\u0027s own reporting, which for all major browsers is very accurate (browsers do not lie about their screen resolution or language preference).\n\nThe tool is designed to be the quickest possible answer to "what is my browser?" — the page loads and the information is displayed without any interaction needed. There is no input field, no button to click, no output to copy (though all text is selectable for copying). It is a display page, not a configuration tool.\n\nWhy this matters in practice: a user reports that a website "looks broken". The support agent asks for the browser and OS. The user opens this page, reads "Chrome 126 on Windows 11", and the agent can immediately check whether that browser/OS combination is in the tested matrix. Or: a developer receives a bug report that the layout is "off" on a specific screen. They ask the reporter to open this page, note the screen resolution (1366x768 — a common budget laptop resolution the design was not tested for) and viewport (683px wide because the browser was snapped to half-screen), and the mystery is solved. These are real, everyday scenarios where a one-click browser identification page saves back-and-forth emails.