| Field | Value | Copy |
|---|---|---|
| {{ key }} | {{ value }} |
Web browsers are client applications that present pages and run scripts, and they also expose a concise snapshot of the device and connection that helps teams understand context. A clear browser and device details report can speed up troubleshooting when pages behave differently across systems.
Environment information explains what software and hardware you are using, how the page is being rendered, and what capabilities are available so reproducible steps are easier to confirm. A browser and device details report is often shared with support when diagnosing display glitches, audio issues, or slow loading.
Typical inputs are nothing more than opening the page and letting it read standard properties. The output is a readable summary and a structured JSON version that you can copy or download for later reference.
One typical case is confirming whether WebGL is available and whether the connection indicates a constrained link so 3D views may fall back gracefully. Another common case is checking language and time zone when timestamps or number formats look unfamiliar.
Results reflect your current setup, so values can change after resizing, switching networks, or altering privacy preferences. For repeatable comparisons, run checks in the same conditions, then share the report with a short note about what you tried.
The report observes two kinds of quantities: identification strings that describe the software stack and hardware descriptors that reveal rendering and connectivity conditions. Identification covers browser name and version, engine, operating system, and device class. Hardware‑adjacent values include viewport size, device pixel ratio (DPR), color depth, languages, time zone, rendering features, and connection estimates.
Computation begins by parsing the user agent to infer browser, engine, operating system, and device fields. It then reads standard properties to gather viewport dimensions, display density, color depth, language arrays, time zone, cookie and tracking preferences, hardware concurrency, device memory, touch points, graphics capabilities, and network hints. All values are collated into a JSON payload alongside a human‑readable table.
Results include capability flags for WebGL and WebGPU, plus connection hints such as effective type and downlink so heavy features can be toggled thoughtfully. Near boundary conditions are common, for example DPR shifting with zoom or connection type changing after a network handoff; compare repeated runs when behavior is unstable.
Comparability depends on the platform and privacy settings. User‑Agent Client Hints (UA‑CH) fields may be partial or absent, and some properties are rounded or suppressed. Treat values as a faithful view of the current session rather than a permanent device fingerprint.
| Parameter | Meaning | Unit/Datatype | Notes |
|---|---|---|---|
| Browser / Version | Application and version derived from user agent | string | Shown in the summary header |
| Engine / Version | Layout/runtime engine identification | string | Displayed as a badge |
| Operating System | OS name and version | string | Derived from user agent |
| Device Type / Vendor / Model | Device classification and identifiers if available | string | Desktop when unknown |
| Platform / Vendor strings | Reported platform and vendor properties | string | Direct from environment |
| Language / Languages | Primary locale and ordered preferences | string, list | Uses browser locale settings |
| Screen Resolution | Total screen pixel dimensions | px × px | Physical screen coordinate space |
| Viewport | Inner window width and height | px × px | Updates on resize |
| Device Pixel Ratio (DPR) | CSS‑pixel to device‑pixel ratio | ratio | Affected by zoom |
| Color Depth | Bits per pixel channel | bits | Null if unknown |
| User‑Agent Brands | Structured brand/version entries | list | From UA‑CH when present |
| UA‑CH Platform / Version | Platform label and version hint | string | High‑entropy values |
| UA‑CH Architecture / Model | CPU architecture and device model | string | May be blank |
| Time Zone / Local Time | IANA zone and localized clock | string | From Intl API and Date |
| Connectivity state | Network reachability flag | boolean | Reflects current status |
| Cookies Enabled | Cookie support capability | boolean | Simple on/off |
| Do Not Track | Tracking preference signal | string | “unspecified”, “0”, or “1” |
| Hardware Concurrency | Logical processor count | integer | Rounded on some platforms |
| Memory | Approximate device memory | GB | Low‑precision hint |
| Touch Support | Maximum simultaneous touch points | integer | Zero means no touch |
| WebGL / WebGPU | Graphics API availability | boolean | WebGPU often experimental |
| Effective Connection Type (ECT) | Broad connection quality class | string | e.g., “4g”, “3g” |
| Downlink | Estimated throughput | Mb/s | May be null |
| Data‑Saver Preference | Reduced‑data request signal | boolean | “On” or “Off” in UI |
| User‑Agent | Raw identification string | string | Full value displayed |
| Input | Accepted Families | Output | Encoding/Precision | Rounding |
|---|---|---|---|---|
| Browser environment | Standard web platform properties | Summary table | Text | None |
| Browser environment | Standard web platform properties | JSON payload | UTF‑8 text | None |
| — | — | CSV export | UTF‑8 text | None |
Numeric values are shown as provided by the platform without additional rounding. Throughput values use megabits per second. Local time follows your locale’s decimal and date separators. Counts such as hardware concurrency and touch points are integers.
No API calls or uploads are performed by the script; data is gathered within the page. Copy actions write plain text to the clipboard when permitted. Downloads are generated locally using object URLs and contain only what you see in the summary or JSON view.
Collection is instantaneous and scales with the small set of properties queried. With the same device, settings, and window size, repeated runs produce the same results. Viewport and connection hints update when the window or network changes.
The JSON preview uses HTML insertion for syntax highlighting; values originate from your environment. Avoid pasting untrusted text into fields that are later rendered as HTML elsewhere. The report can reveal device characteristics; share only with trusted parties.
Concepts align with the User‑Agent Client Hints specification, the Network Information API concept, the Device Memory specification, and the graphics capabilities defined by WebGL and WebGPU communities.
No data is transmitted or stored server‑side. The report may contain identifying information; handle according to your organization’s data handling policies.
The browser and device details report summarizes your current environment for quick diagnosis and sharing.
Example. Share the CSV with support and note “WebGL: Yes, DPR: 2, ECT: 4g”. This helps teams reproduce conditions.
No. Values are gathered and displayed within the page. Copy and download actions generate files locally for you to share if desired.
Parsing is accurate for mainstream setups, but privacy features and vendor changes can alter or hide details. Treat the report as descriptive, not authoritative.
Throughput uses megabits per second. The value is an estimate and may be null on platforms that do not expose it.
Once loaded, the page reads properties locally. The connectivity flag and connection hints reflect the current state and may change.
Open the Info tab and scroll to the table row labeled “User‑Agent”. Use the copy button to place it on your clipboard.
It means the tracking preference is not explicitly set or not exposed. Some platforms omit this field entirely.
The package does not declare licensing terms. Use and redistribution policies should follow your organization’s guidelines.