What does a browser information page show?
A browser information page reads the values your browser offers to any page you visit and displays them: the user agent string, the platform, the reported operating system, the screen and viewport size, the device pixel ratio, the graphics renderer, the connection type, and preferences such as colour scheme and reduced motion. None of it is secret and none of it is inferred — each row is a value the browser handed over on request.
The list matters because it is the raw material of a device fingerprint. A user agent on its own is coarse, but the combination of user agent, screen size, pixel ratio, time zone, graphics renderer and installed-font metrics narrows a visitor down far more than any cookie, and it does so without writing anything to the device. That trade-off is worth understanding: it is why browsers have spent the last decade reducing what they volunteer.
For practical work the values are exactly what a bug report needs. Whether a layout broke because the viewport is narrow or because the device pixel ratio is high, whether a dark stylesheet applied because the preference is genuinely dark, whether a machine report came from a phone or a desktop, whether the connection is slow enough that a large video should not autoplay — each of those is answered here, in the moment, without sending anything anywhere.
How to check your browser and device details
- Open the page. The values are read from the browser the moment it loads, so there is nothing to paste and nothing to press.
- Start with the three tiles: the browser family and major version, the reported operating system, and whether the device is a desktop, a tablet or a phone.
- Read the full table for the details — user agent, languages, time zone, screen and viewport size, pixel ratio, CPU thread count, memory, touch points and the graphics renderer.
- Type into the filter to narrow the table when you need one value for a bug report or a support form.
- Press Copy everything to put the whole list on the clipboard as plain lines, ready to paste into an email or an issue.
- Reload after changing a browser setting, such as switching to dark mode or rotating a phone, to confirm the value changed.
What Is My Browser? limits and rules
| Item | Limit |
|---|---|
| Sources | navigator, screen, window and matchMedia, read in the browser |
| Sending | None — the values are read into the page and never leave it, and there is no server-side lookup |
| User agent | Whatever the browser reports, which is increasingly abbreviated and frozen |
| Client hints | Shown only if the browser volunteers them, which Safari and Firefox largely do not |
| Graphics renderer | May be blanked by the browser as an anti-fingerprinting measure |
| Device memory | Rounded to a power of two, and not reported by every browser |
| IP address and location | Not shown — they need a network request, which this page never makes |
| Operating system | Inferred from the user agent, so it can be wrong or generic on purpose |
When to use it
- Copying an exact user agent and screen size into a bug report so the reproduction is unambiguous.
- Confirming that a dark-mode stylesheet or a reduced-motion rule is actually being applied.
- Checking the device pixel ratio when images look soft or a layout halves in size on a phone.
- Reading the effective connection type before deciding whether to load a video or an image gallery.
- Seeing how much information your own browser volunteers, and comparing it across browsers and settings.
Is it private?
This page makes no network request and stores nothing. Every value is read from APIs your browser exposes locally, displayed in the table, and discarded when you close the tab. That said, the same values are visible to any script on any site you visit — which is the reason some browsers now restrict them.
Frequently asked questions
Because browsers have been deliberately reducing it. Chrome froze the platform and device fields years ago, reporting a generic string and moving the real detail to Client Hints, which are sent only when a server explicitly asks. Firefox followed in the same direction, and Safari reports less again. It is a trade: less detail means fewer bugs caused by sites sniffing the wrong browser, and it also means a tracking script gets less to work with. The displayed string is what your browser actually sends.
The unmasked renderer string comes from a WebGL debug extension, and browsers increasingly restrict it. Firefox and Safari return a generic value instead of the real card name, and some configurations return nothing at all. The extension exists precisely because the real string is a strong fingerprinting signal: the exact combination of card model and driver version is close to unique. If the row reads as blocked or generic, that is the browser protecting you, not a fault in this page.
No, and it cannot. Both would need a network request — an IP address is only visible to the server you connect to, and a geolocation estimate is built from a database lookup of that address. This page deliberately makes no request, so it shows what your browser knows about itself rather than what a server knows about you. If you want the other half, a service that responds with the address it saw will tell you.
Because it is inferred from the user agent, and modern user agents keep it vague on purpose. On Windows, the string still says NT 10.0 for both Windows 10 and 11, since the version was frozen at the release where browsers stopped updating it. On Apple hardware with a desktop-class chip, an iPad may report as a Mac. The platform value beside it is usually more accurate, but it too can be generic, because precision here is what fingerprinting exploits.
Quite a lot, most of it through measurements rather than declarations. The set of installed fonts can be probed by rendering text and measuring it; the canvas and audio APIs can be drawn from and their output hashed, since the exact rendering differs subtly per machine; battery status, media devices and available codecs can all be enumerated. None of that is in this table because it needs active probing rather than reading a value, which is why some browsers now ask permission or return noise for those APIs.
For a bug report, yes — it is what a developer needs, and catalogues like a support form expect the user agent. The caution is about combining it. A user agent plus screen size plus time zone plus renderer is much more identifying than any of those alone, and pasting the full list into a public place is effectively publishing a fingerprint of your device. Share the rows that answer the question rather than the whole table when the destination is public.
Related tools
Written and maintained by Md. Nur Hossain Repon.