Check details your browser reports about itself — browser type, OS, screen size, timezone, and language. Not IP geolocation.
No, this tool only shows information your browser voluntarily reports via JavaScript, such as browser type, OS, screen size, timezone, and language. It does not perform IP-based geolocation.
Your browser reports its configured timezone (like Asia/Kolkata) directly, but does not report your city or precise location unless you separately grant location permission.
No, everything is read and displayed entirely within your browser — nothing is transmitted to a server.
It's useful for debugging website issues tied to a specific browser or screen size, confirming your browser's detected timezone and language settings, or simply understanding what a website can see about your browser without any special permissions.
It shows the version your browser currently reports in its user agent string, which reflects whichever version is currently installed and running.
Screen resolution is your full physical display's pixel dimensions, while viewport size is just the visible content area of your current browser window — these differ whenever the browser isn't maximized or when browser chrome (toolbars, bookmarks bar) takes up part of the screen.
This tool displays a range of information that web browsers make available to JavaScript running on any page — details like your browser name and version, operating system, screen resolution, timezone, and language preference. It's important to understand what this actually is: browser-self-reported metadata, not IP-based geolocation or any form of precise identification.
This tool does not look up your IP address, does not determine your city or physical location, and does not access any server-side geolocation database. Real IP geolocation requires server-side infrastructure that looks up an IP address against a database of network ranges — something this purely browser-based tool doesn't do. Any location-sounding information shown here (like your timezone) comes directly from your device's own settings, not from analyzing your network connection.
Understanding what a website can learn about your browser just from standard JavaScript APIs — without any special tracking or permissions — helps demystify a common source of confusion about "fingerprinting" and privacy. This same information (browser, OS, screen size, timezone, language) is available to essentially any website you visit, forming part of what's sometimes called a browser fingerprint when combined across multiple signals.
No single piece of information shown on this page uniquely identifies you — plenty of people share the same browser, OS, and screen resolution. Fingerprinting becomes a privacy concern specifically when many individually common data points are combined together, since the combination of browser version, OS, screen resolution, timezone, language, installed fonts, and other signals becomes increasingly unique the more signals are combined, even without using cookies or any login. This tool shows you a subset of the signals involved in that process, giving a concrete sense of what's technically visible to any website without requiring any special permission from you.
The user agent is a text string your browser sends with every web request, originally intended to let servers identify the browser and adjust content accordingly. Over the years, this string has become somewhat messy for historical compatibility reasons — many browsers include references to other browser engines in their user agent for legacy compatibility purposes, which is why parsing it correctly to identify the actual browser in use requires more careful logic than a simple text match might suggest. This tool handles that parsing for you, extracting the actual browser name and version from what can otherwise be a confusingly layered string.
All information shown here is read directly from your browser's JavaScript APIs and displayed locally — nothing is transmitted to any server by this tool, logged, or stored anywhere.
It's worth being clear about the distinction, since the two are easy to confuse. An IP lookup or geolocation tool works server-side: it receives your network connection, looks up your public IP address against a database mapping IP ranges to approximate geographic regions, and returns a location estimate — this can reveal your approximate city or region without your browser directly participating. This tool works entirely differently: it only reads and displays settings your own browser is willingly reporting through standard JavaScript, with no network-level lookup involved at all, and specifically does not determine or reveal anything about your IP address or physical location.
When a user reports a bug that a development team can't reproduce on their own machines, knowing the reporting user's exact browser version, operating system, and screen resolution is often the missing piece that explains the discrepancy — a layout bug that only appears at a specific narrow viewport width, or a feature that behaves differently on an older browser version, are both extremely common root causes that are otherwise hard to diagnose without this information. Asking a user experiencing an issue to visit a page like this one and share the results is a quick, low-friction way to gather exactly the technical details needed to reproduce and fix a browser-specific bug without a lengthy back-and-forth conversation.