My Browser Info

The answer is at the top of the tool card above — for example, "Chrome 126" or "Firefox 127", together with the rendering engine that powers it (Blink, Gecko, or WebKit). The detection combines the browser-reported user agent with the modern User-Agent Client Hints interface, so it works in Chrome, Edge, Firefox, Safari, Opera, and Chromium-based browsers alike. Scroll down for the full picture: operating system, languages, timezone, and which Web APIs your browser supports.

This page shows the version your browser reports, which you can compare with the latest release on the vendor’s official site. A quick way to update: Chrome and Edge update automatically but you can force a check at chrome://settings/help (or edge://settings/help); Firefox checks on restart via Settings › General › Firefox Updates; Safari updates through macOS System Settings › Software Update. Browsers that are several major versions behind miss security patches — updating is one of the easiest security upgrades you can make.

The user agent (UA) is a short text your browser sends with every request, describing the browser, its version, and the operating system — for example: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36. Websites used it to adapt content to each browser, but because it was widely abused for fingerprinting and contained misleading historical tokens, browsers now freeze or reduce parts of it. The full string is shown on this page so you can copy it for support tickets or testing.

Chromium-based browsers practice User-Agent Reduction: since Chrome 101, the minor version is frozen at 0 (you will see 126.0.0.0 instead of 126.0.6478.115) and operating system details are simplified — Windows 10 and 11 both report Windows NT 10.0. Firefox reduces OS version too. The goal is to limit passive fingerprinting. If you need the exact version, Chromium browsers expose it through getHighEntropyValues(), which this page uses automatically when available — that is why the version shown here is more precise than a raw UA parse.

That is GREASE — deliberately inserted randomized entries. Chromium adds meaningless brand tokens like "Not A Brand;v=8" or "Not_A Brand" into the brands list, with names and positions that change between releases. The purpose is to force any parser that reads the list to handle unexpected values correctly, preventing buggy parsers from becoming entrenched standards. It is not malware, not an extension, and not an error — every Chrome, Edge, and Opera user sees a variation of it.

Browsers deliberately round or cap details that could identify you. Device memory (navigator.deviceMemory) is reported as a rough bucket — 0.25, 0.5, 1, 2, 4, or 8 GB — and never exceeds 8, even on a 32 GB machine. CPU core counts reflect logical processors as the browser sees them, which can differ from physical cores. Operating system versions come from reduced user agents or Client Hints and may be coarse. These approximations are privacy features, not bugs.

The capability matrix tests — in your live browser, right now — whether the interfaces behind modern web features exist: WebUSB and WebHID (talking to USB devices), Web Bluetooth, WebGPU (modern graphics), Web Serial, Web MIDI, WebRTC (real-time audio/video), WebAuthn (passkeys and security keys), Service Workers (offline apps), WebAssembly, WebGL 2, and the async Clipboard API. A green check means the API is present; it does not guarantee every sub-feature. These are the same checks that decide whether hardware-testing tools can run on this site.

Yes. The page itself only needs a browser to render — the information shown is whatever your browser reports. The difference is precision: Firefox and Safari do not implement the User-Agent Client Hints interface, so the card falls back to parsing the classic user agent string, which is accurate for browser name and major version but carries reduced OS detail. Chromium-based browsers (Chrome, Edge, Opera, Brave) additionally unlock high-entropy hints such as full version, architecture, and bitness.

Completely. Everything you see is read from your browser’s own interfaces — navigator, screen, Intl, and feature detection — and rendered locally. No data is transmitted to a server, no fingerprint is computed, and nothing is stored after you close the tab. That stands in contrast to many "what is my browser" sites that log user agents or run analytics on the results. You can verify the behavior yourself: load the page, disconnect from the internet, and it still works.

Edge, Opera, Brave, Vivaldi, and many others are built on Chromium — Google’s open-source browser core — so their user agents legitimately contain Chrome tokens, and their Client Hints brands list includes both "Chromium" and the actual product name. This page prioritizes the product-specific token (Edg/ for Edge, OPR/ for Opera) so the name shown is your real browser, with the engine listed separately as Blink. Brave goes further and randomizes some hints by default for privacy.