Everything the browser knows about the machine it is running on, printed in one report: browser and engine, CPU core count, device memory (browsers cap the reported value at 8 GB), GPU via WebGL, screen geometry and pixel ratio, network class, storage quota, and preference signals like dark mode.
The codec-support section answers the question people actually come with: can this browser decode HEVC, AV1, VP9, FLAC, Opus — each marked with an honest ✓ / (maybe) / ✗ straight from canPlayType.
Frequently asked questions
Is this a privacy risk?
No data leaves the page — the report is the page reading its own standard APIs and printing them for you to copy. Close the tab and nothing persists anywhere.
Why does memory say ~8 GB when I have 16?
The deviceMemory API is deliberately coarse and clamped to 8 GB maximum — it is an anti-fingerprinting measure, not a bug in the tool.
中文说明
浏览器所知的本机信息，一份报告全打出：浏览器与引擎、CPU 核心数、设备内存（浏览器上报值上限 8 GB）、WebGL 读出的 GPU、屏幕几何与像素比、网络等级、存储配额，以及深色模式等偏好信号。
解码支持区回答大家真正带着来的问题：这台浏览器能不能解 HEVC、AV1、VP9、FLAC、Opus——每项都由 canPlayType 给出诚实的 ✓ / (maybe) / ✗。
常见问题
这有隐私风险吗？
没有任何数据离开页面——报告就是页面读取自己的标准接口再打印给你复制。关掉标签页，什么都不会留下。
为什么内存显示 ~8 GB，我明明有 16 GB？
deviceMemory 接口刻意粗粒度并封顶 8 GB——这是反指纹追踪的措施，不是工具的 bug。