Browser Detector
Detect your browser details instantly, including name, engine, and user agent. Also see window size and other quick info for debugging.
You Are Using...
Browser Name:
Browser Version:
Operating System:
layoutEngine:
User Agent:
MORE INFORMATION
Browser Resolution: Detecting...
Screen Resolution: Detecting...
Color Depth: Detecting...
Language: Detecting...
Timezone: Detecting...
Cookies Enabled:
WebSocket Supported: Detecting...
WebGL Supported: Detecting...
WebGL Vendor: Detecting...
WebGL Renderer: Detecting...
What this does
So you want to see what your browser is reporting about itself: its name and version, the operating system, the engine it uses, and a pile of other details handy for debugging. This lays it all out. Open the page and it fills in everything it can detect.
How to use it
There is nothing to set up. The page reads the details from your browser as soon as it loads and displays them, the core browser facts on one side and a longer list of technical details on the other.
How it works
The information comes from two places, both already inside your browser. The browser name, version, and operating system are worked out from the user agent string, a line of text your browser sends that describes itself, read here with a small detection library. The engine is identified by checking that same string for the tell tale name of each layout engine.
Everything in the more detailed list, the window and screen size, colour depth, language, timezone, whether cookies and features like WebSocket and WebGL are available, and the graphics details, is read straight from the browser's own built in interfaces. None of it is sent anywhere, it is all gathered and shown locally.
A note on user agents
One thing is worth knowing about the browser name and version in particular. The user agent string is self reported, the browser simply states what it is, so it can be changed or imitated, and some browsers now deliberately keep it vague to protect privacy. That makes user agent based detection less dependable than it once was, which is why, in real code, checking whether a specific feature exists is generally preferred over checking which browser is running.
It is also a reminder of how much a browser reveals. The same details shown here, taken together, are part of what lets websites recognise and fingerprint visitors, so this page doubles as a look at your own visible footprint.
Questions people ask
Where does this information come from?
All of it is read from your own browser: the name and version from the user agent string, and the rest from the browser's built in interfaces. Nothing is fetched from a server.
Why might the browser name be wrong?
The user agent string is self reported and can be changed or imitated, and some browsers keep it deliberately vague, so detection based on it is not always exact.
Is any of this sent anywhere?
No. Everything is gathered and displayed locally in your browser. None of the details leave your machine.
Why should code use feature detection instead?
Because what matters is usually whether a feature is available, not which browser is running. Checking for the feature directly is more reliable than trusting the browser's self description.
References
- MDN Web Docs. Navigator: userAgent property. https://developer.mozilla.org/en-US/docs/Web/API/Navigator/userAgent
- MDN Web Docs. Browser detection using the user agent. https://developer.mozilla.org/en-US/docs/Web/HTTP/Browser_detection_using_the_user_agent
Sugam Baskota is a senior software engineer and Computer Science graduate from UT Arlington, with interests in user scripts, browser extensions, developer tooling, and productivity systems. He spends time building practical utilities and extensions in the kinds of workflows Eon is designed to simplify. At Eon Tools, he reviews useful, password, and developer tools.