Browser Info Test
A complete, live readout of your browser, engine, operating system, screen, and the web features it supports, with a one-click copy for support tickets.
Reading browser details…
Quick guide: how to use the Browser Info
Takes under a minute- 1Everything on this page is detected automatically, no clicks needed.
- 2Check your browser version and engine first.
- 3Scroll to the feature support table to see what APIs are available.
- 4Copy the readout when reporting a bug to a support team.
Overview
Every website you visit gets a small amount of information about the software and hardware you're using, whether you notice it or not. Your browser announces its name, version, and rendering engine, your operating system, your screen dimensions, and a long list of feature flags that tell the site what it's allowed to try. Most of the time this happens silently and you never think about it. But the moment something breaks, whether that's a video call that won't connect, a game that stutters, or a form that refuses to submit, this exact information becomes the first thing a support technician or a developer will ask you for.
This tool pulls all of that together in one place and displays it in plain language, without you needing to open developer tools or dig through browser settings. It reads the standard navigator and screen objects that every website already has access to, parses the User-Agent string into a readable browser name and version, checks the newer User-Agent Client Hints API where it's available, and runs a quick feature-detection pass against nine commonly needed web APIs.
None of this requires special permission. Browsers expose this information to any page by design, because websites need it to decide how to render themselves and which features to offer. What we've done here is simply collect it, label it clearly, and make it easy to copy.
How to read your results
Browser and engine
The browser name and version come from parsing the User-Agent string, cross-checked against the newer, more structured User-Agent Client Hints data where your browser provides it. The "engine" field tells you which rendering engine is doing the actual work under the hood: Blink powers Chrome, Edge, Opera, and most Android browsers; Gecko powers Firefox; and WebKit powers Safari and every browser on iOS, because Apple requires all iOS browsers to use WebKit regardless of their name.
This matters because two browsers with different names can behave almost identically if they share an engine. A rendering bug in Chrome will often show up in Edge and Opera too, since all three are Blink-based.
Operating system and platform
The OS field is a best-effort guess based on the User-Agent string. The "platform string" is a lower-level, older API (navigator.platform) that's being phased out in favor of User-Agent Client Hints, so on newer browsers you may see both a legacy platform value and a Client Hints platform value side by side. They should usually agree.
Screen, viewport, and pixel ratio
"Screen size" is your monitor or display's full resolution in device pixels. "Viewport size" is the visible area of the browser window itself, which is almost always smaller once you account for the browser's own toolbars and any docked panels. The device pixel ratio explains the relationship between the two: a ratio above 1 means the operating system is scaling content up for readability on a high-density screen.
Feature support grid
Each row in the grid answers a yes or no question: does this browser, right now, in this context, expose the JavaScript API needed for that feature? A "No" doesn't necessarily mean the feature is broken forever; it can mean the browser doesn't support it yet, it's disabled behind a flag, or (in the case of WebGL and WebGPU) the graphics drivers on this machine have been blocklisted for stability reasons.
Troubleshooting
If a feature you expected to see supported shows up as unsupported, work through these in order:
- Confirm you're on the latest version of your browser. Browser vendors ship new Web API support in regular release cycles, and an outdated build is the single most common cause of a missing feature.
- Check whether the feature requires a secure context. APIs like Service Worker, some Clipboard methods, and MIDI access are only available on pages served over HTTPS or on localhost.
- Look for browser flags. WebGPU in particular has spent long stretches available only behind an experimental flag on certain platforms.
- Rule out extensions. Privacy and ad-blocking extensions sometimes disable Notification, Clipboard, or WebRTC APIs site-wide.
- Try a different browser entirely to isolate whether the limitation is browser-specific or something about your device or network.
Why this information matters for troubleshooting
A huge share of "it doesn't work on my computer" support tickets get resolved the moment the support agent knows the caller's exact browser and OS combination, because so many bugs are specific to one rendering engine, one OS version, or one hardware pixel density. Reporting "Chrome 128 on macOS 14.5, DPR 2, WebGL2 supported" is worth more than paragraphs of description, because it lets a developer reproduce your exact environment.
It's also useful for your own diagnosis before you even contact anyone. If a site says it needs WebGPU and this page shows WebGPU as unsupported, you now know the fix is to update or switch browsers, not to keep retrying the same page. If a video call keeps failing and WebRTC shows as unsupported (rare, but possible in locked-down enterprise browser builds), that single row explains the whole problem.
Privacy notes
Everything shown here is read locally by JavaScript running in your browser and rendered directly on this page. Nothing is uploaded to a server as part of running this test. The copy-to-clipboard button only puts text on your own clipboard; it doesn't send anything anywhere until you decide to paste it into an email, chat, or support form yourself.
It's worth knowing, separately, that this same category of information (User-Agent, screen size, language, feature support) is one of the inputs used by "fingerprinting" scripts on some sites to try to identify visitors without cookies. Seeing how much detail is available here is a useful, honest look at what any site could technically collect about your setup, even though this particular page doesn't store or transmit it.
Frequently asked questions
Why do I need to know my browser version?
Support teams and bug trackers usually ask for your exact browser and OS version because a fix or workaround often only applies to specific versions. Guessing wastes time on both ends.
Is the User-Agent string always accurate?
Mostly, but some browsers deliberately reduce detail in the User-Agent string for privacy reasons, and some users or extensions spoof it. The userAgentData readout, where supported, is generally more reliable.
What does 'device pixel ratio' mean?
It's the ratio between physical screen pixels and CSS pixels. A ratio of 2 means the screen is a high-density (Retina-style) display where each CSS pixel is drawn with a 2x2 block of real pixels.
Why does deviceMemory show 'unknown'?
The Device Memory API is only implemented in Chromium-based browsers, and even there it reports a rounded approximation, not the exact RAM installed. Safari and Firefox don't expose it at all for privacy reasons.
Does hardwareConcurrency equal my CPU's core count?
It reports the number of logical processors the browser can use, which usually matches your CPU's thread count (including hyperthreading), not necessarily the physical core count.
Why is WebGPU showing as not supported?
WebGPU is newer than WebGL and is still rolling out. It's available in recent Chrome and Edge versions on most platforms, arrived later on macOS and Linux, and remains behind flags or unsupported in some Firefox and Safari releases.
What is a Service Worker and why should I care if it's supported?
Service Workers let websites work offline, cache assets, and send push notifications. If it's unsupported, an installable web app on that browser will lose offline capability and background sync.
Can I trust the touch support detection?
It's a solid signal but not perfect. Some laptops with touchscreens report touch support even when you never use it, and some browsers report a nonzero maxTouchPoints on non-touch hardware for compatibility reasons.
Why would a support agent ask me to copy this summary?
It bundles the ten or so details they'd otherwise ask for one at a time: browser, OS, screen size, feature flags, and the raw user agent. Pasting it once speeds up diagnosis significantly.
Does this page send my information anywhere?
No. Everything here is read directly by your browser's JavaScript and displayed on the page. Nothing is transmitted until you choose to paste the summary somewhere yourself.
My languages list looks different from my system language. Why?
The languages array reflects your browser's language preference settings, which you can change independently of your operating system's display language in most browsers.