🖥️ What Is My Browser? ☆

Overview

What Is My Browser shows exactly which browser you are using: name, version, rendering engine and operating system, plus display details like screen resolution, viewport size, pixel ratio and color depth. It also lists your language, timezone, cookie and Do Not Track settings, touch support and online status. Everything is detected locally from standard browser APIs. Nothing is uploaded, and no external service is contacted. Use it to check whether your browser is up to date, to copy your user agent for support requests, or to see what information websites can read from your browser.

How browser detection works

Browsers expose a set of standard APIs that describe themselves: navigator.userAgent and userAgentData for name and version, navigator.languages for language preferences, screen and window properties for display details, and media queries for features like dark mode or reduced motion. The report groups these signals so you can see what any website can read on your first visit, before cookies, before consent. User-agent strings can be spoofed by extensions or privacy tools, so a mismatch between the reported browser and real behavior is itself useful information when debugging a support case.

Specifications and compatibility

Property	What is my browser behavior
Detects	Browser name/version, rendering engine, OS, screen, viewport, pixel ratio, color depth
Also reports	Language, timezone, cookies, Do Not Track, touch support, online status
Method	Standard browser APIs only; no fingerprinting beyond what sites already read
Processing	100% client-side; nothing uploaded, no external service contacted
Export	Copy the full report for support tickets
Cost	Free, no account, no ads

Privacy: a diagnostic, not a tracker

The point of this page is to show you what is visible about you. It does not add tracking of its own. No data leaves the tab and the report still renders offline after the page has loaded once.

When to check your browser details

• Confirm the version before reporting a bug.
• Copy the user agent when a support form asks for it.
• Check whether hardware acceleration or dark mode is detected correctly.
• Verify that a privacy tool is actually spoofing the user agent.
• See why a site may be showing the mobile layout.

Related: browse the privacy and security tools for fingerprint, WebRTC and IP checks.

What browser detection actually reveals

Every page you visit can read a surprising amount about your setup, and knowing what is visible explains both how sites adapt and how they track. The user agent string is the classic signal, but it is unreliable: browsers freeze or mimic each other's identifiers for compatibility, so it says more about history than about the software you run. Feature detection is the honest alternative, checking whether an API exists rather than guessing from a name. Beyond that, a page can see the platform, screen resolution, device pixel ratio, colour depth, time zone, preferred languages, touch support and whether cookies are enabled. Graphics APIs add detail: WebGL exposes the renderer and vendor strings, which often identify the GPU model and can distinguish devices behind the same network. Fonts and canvas rendering add more entropy, which is how fingerprinting works without cookies. Privacy tools respond by randomising or blocking these values, so a report may show deliberately generic data. Practical uses of a browser report include diagnosing why a site misbehaves, an outdated engine, a blocked third-party cookie, a zoomed display or a missing codec. Treat the report as a diagnostic, not as an identity document, and remember that the page reads these values locally: nothing is sent to a server, and no profile is stored.