Description
About Browser Information
Introduction
Browser Information focuses on the software side of your session: engine and platform clues, user-agent context, and a compact feature matrix. Use it when the question is “which browser and what can it do,” not “what size is my screen.”
What this tool does
It summarizes identity and capability signals the browser exposes to pages, with clear empty states when privacy reduction hides detail. Hardware-heavy fields such as concurrency, memory, and viewport depth live on Device Information instead, with short pointers here when useful.
When to use it
Use it for support macros, WebView checks, and feature planning. Prefer User Agent when a CDN or legacy sniffer is the dispute, Browser Features for a wider API matrix, and Device Information for geometry and hardware hints.
How it works
Reads navigator and related surfaces in-page. Client Hints and reduced user agents intentionally omit older detail. Feature rows are detection checks, not guarantees that permissioned APIs will succeed after a prompt.
Step-by-step instructions
- Open Browser Information over HTTPS in the profile under test.
- Note engine, platform, and any reduced or incomplete identity fields.
- Scan the feature summary for APIs relevant to your bug.
- Cross-check Device Information or User Agent when the ticket needs those angles.
Common problems
Incomplete fields are often privacy policy, not a broken page. In-app WebViews differ from desktop Chrome. Extensions that spoof the user agent change what you see here.
Privacy explanation
Identity and feature signals stay in your tab for diagnostics. DeviceHub does not sell fingerprint marketplace data from this page.