首页 通用效率工具内容详情

Browser Info Check: UA, Screen, Timezone, GPU on One Page - View and leave, zero reporting, works offline

2026-11-17 3 访客
Browser Info Check: UA, Screen, Timezone, GPU on One Page

站点名称:Browser Info Check: UA, Screen, Timezone, GPU on One Page

所属分类:通用效率工具

官方网址:https://www.9314.cn/tools/browser-info/en/

SEO查询: 爱站网 站长工具

进入网站

站点介绍

Browser Info Check: UA, Screen, Timezone, GPU on One Page

Debugging a layout that broke on exactly one teammate's machine, I asked over chat three times: how wide is your window, what scaling? The answer turned out to be an external display at 150%. That day this page was born - every check scattered across console commands, collected where opening it is enough.

The short version

  • About 25 checks at once: UA parsing (browser, version, engine, OS), physical screen versus CSS viewport, DPR, color depth, language list, timezone with UTC offset, cookies, touch, CPU cores, WebGL GPU renderer.
  • UA parsing stays offline: built-in priority-ordered rules (Edg before Chrome, Chrome before Safari) distinguish the five majors; when a Chromium shell reads as Chrome, the full UA string below settles it.
  • Physical and CSS viewports shown separately: breakpoints follow the CSS viewport - at DPR=2 a physical 3840 screen hits breakpoints at 1920. The two numbers people mix up most when debugging misalignment.
  • NetworkInformation where offered: Chromium shows connection type, downlink estimate and RTT; Safari and Firefox lack the interface, and unsupported is the expected reading there.
  • Zero reporting: no requests, nothing in localStorage, gone when the tab closes; Copy report to keep a copy.

The privacy boundary, in plain words

Everything this page can read, every site you visit can read too - UA, screen and timezone are headers and interfaces your browser volunteers to everyone. The difference here: it is read for your eyes only and sent nowhere. The source contains no fetch/XHR/beacon; detection data never touches storage. The shared site analytics log the page view only, never your device details.

When "unavailable" is the answer

Anti-fingerprinting modes return generic GPU names and block precise timezones. A WebGL renderer reading "generic value (anti-fingerprinting)" is not breakage - the browser is protecting you, and that state is itself useful information.

FAQ

Is anything uploaded or saved from the detection?

No. Everything is read inside this device's browser and shown directly on the page - there is no reporting endpoint, nothing is written to localStorage, and closing the tab wipes it all. To keep a copy, use the copy-report button and take it with you.

Why does my browser show up as Chrome?

Most Chromium-based browsers (Edge, Opera, Brave, Vivaldi and many regional builds) carry a Chrome/version token in the UA. This page matches known browser tokens in priority order (Edg before Chrome, Chrome before Safari), so Chromium-family browsers display as Chrome; check the full UA string below to confirm the actual brand.

Why do screen resolution and CSS viewport differ?

screen.width is physical pixels while CSS layout uses logical pixels (CSS px); the two differ by the device pixel ratio DPR. A MacBook driving a 4K display at 200% scaling: physical 3840x2160, viewport about 1920x1080, DPR=2. Responsive breakpoints follow the CSS viewport, not physical resolution.

What does the WebGL renderer tell me?

The WEBGL_debug_renderer_info extension exposes the GPU model (Apple M3, NVIDIA RTX 3060 and so on) - often the first evidence when triaging canvas performance or WebGL compatibility. Some browsers return generic values or block the extension under anti-fingerprinting; showing unavailable is normal.

中文版:https://www.9314.cn/tools/browser-info/

 暂无评论,快来抢沙发吧~

发布评论