b2KIT

Browser Info Detector

Detect browser name, version, OS, user agent, installed plugins, and supported Web APIs in your current browser.

Tested tool guide Tested browser tools Checked August 16, 2026

What Browser Info Detector does and how it behaves

Browser Info Detector examines the browser session in which its page is open. It reports the apparent browser and version, operating system, user-agent string, browser-exposed plugins, and the Web APIs available in that context. There is no text input because the current browser is the subject of the inspection. The main surprise is that browser and OS labels are inferred from self-reported data. Privacy protections, compatibility tokens, or user-agent overrides can make those labels incomplete or misleading.

How the result is produced

1

Identity report

The detector reads browser-exposed identification data and presents both the raw user-agent string and interpreted browser, version, and operating-system labels. These fields describe what the current session reports, not a verified software installation. A browser may reduce version details, imitate another browser for compatibility, or expose different information after a user-agent override.

2

Capability inventory

The plugin section reflects only plugin information the browser permits web pages to inspect. The Web API section records whether selected browser interfaces are exposed in the current page context. A positive result indicates detectable availability, but it does not prove that permission will be granted, suitable hardware exists, or every operation in that API will succeed.

Good uses

  • Capture the exact user-agent and reported browser details when documenting a browser-specific bug.
  • Compare Web API availability between two browsers or between normal and privacy-focused configurations.
  • Check whether a browser exposes any plugin entries before investigating plugin-dependent compatibility behavior.

Limits and checks

  • Do not treat the detected browser, version, or operating system as authenticated facts. User-agent data can be reduced, overridden, or intentionally misleading.
  • An empty plugin list does not prove that no browser-integrated viewers or extensions are installed. Modern browsers reveal very little plugin information to pages.
  • API detection is context-sensitive. Secure-context requirements, permissions, policy restrictions, hardware, and partial implementations can still prevent an exposed API from working.

Common questions

Can this detector identify the exact device or browser installation?

No. It can summarize information exposed by the current browser session, including its user agent and detectable capabilities. That information may suggest a browser family, version, and operating system, but it is not a reliable device identifier. Different devices can report similar values, and one device can report different values after privacy settings or overrides change.

Why does the plugin section show nothing or only a PDF viewer?

Browsers no longer expose a general inventory of installed extensions or legacy plugins to ordinary web pages. The reported list is limited to entries available through the browser's plugin-facing web interface, which may be empty or contain standardized PDF viewer entries. An empty result therefore means no plugin entries were exposed, not necessarily that nothing is installed.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools