Browser detector
Instantly see which browser and version you're running, plus its engine, operating system, languages and a live feature-support grid. Everything is read in your browser and shown only to you — nothing is uploaded.
User agent
—
Display & preferences
Storage estimate
Feature support
100% local — nothing leaves your device
How to use it
- 1 Open this page in the browser you want to check — detection runs automatically.
- 2 Read your browser name, version, engine and OS at the top of the report.
- 3 Scroll the feature grid to see which APIs (WebGL, WebGPU, getUserMedia, Service Worker, WebAssembly, Bluetooth) your browser supports.
- 4 Copy the user-agent string or share the report if you need to send it to support.
Troubleshooting
Browser detector showing the wrong browser or version in Chrome
Detection reads navigator.userAgent and userAgentData, which extensions, enterprise policies or “Request desktop site” can rewrite. Disable any user-agent spoofing extension, turn off desktop-site mode, then reload. The version shown is the engine build, which may differ slightly from the menu's marketing number.
Browser detector not working on Windows 11 or shows blank fields
Some fields rely on the modern userAgentData API, which only fills in over a secure https connection and in Chromium browsers. On Firefox or older browsers a few entries fall back to the legacy user-agent string. Reload over https and disable strict privacy or anti-fingerprinting extensions, then retry.
Feature grid says WebGPU or Bluetooth is not supported
A red entry means your current browser, version or platform lacks that API, not that the page is broken. WebGPU and Web Bluetooth are unavailable in many browsers, on iOS, and over plain http. Update your browser, switch to a supported one, or load the page over https to enable them.
The user agent looks fake or anonymised in Firefox or Brave
Privacy-focused browsers and anti-fingerprinting settings deliberately freeze or generalise the user-agent string and block userAgentData to resist tracking. That's expected behaviour. To see real values, lower the resist-fingerprinting setting for this page or open it in a standard browser profile.
Frequently asked questions
What browser am I using right now?
This page detects it for you the moment it loads, reading navigator.userAgent and navigator.userAgentData. The browser name, version, rendering engine and operating system are shown at the top of the report.
Is any of my browser data uploaded or recorded?
No. Everything runs locally in your browser using JavaScript and the navigator API. Your user agent, version and feature results are computed on your device and shown only to you — nothing is sent to a server or stored.
What is a user agent string?
It's a line of text your browser sends with every request, identifying its name, version, engine and operating system. This tool displays your full user-agent string so you can copy it for bug reports or compatibility checks.
How accurate is the detected version number?
It reflects what your browser reports through userAgentData and the user-agent string. This usually matches the version in your browser's About page, though privacy settings, spoofing extensions or freeze policies can make it generic or slightly different.
Does the browser checker work on mobile?
Yes. It works in mobile Chrome, Safari, Edge, Firefox and other modern browsers on Android and iOS. The report adapts to show your phone's browser, version, OS and the features available on that platform.
Why are some features marked unsupported?
Each row is feature-detected live. A feature shows as unsupported when your specific browser, version or device lacks that API, or when it requires an https connection. Updating or switching browsers often turns those entries green.