Loading page
About this tool
Client-side dashboard for device, browser, privacy, GPU, storage, and web API capability analysis.
The Device & Browser Dashboard reports everything a web page can learn about your browser without asking permission: the browser and engine parsed from the user-agent string, the operating system, viewport and screen geometry, the privacy signals you send, and which of 20 web APIs are actually available. Detection matches the most specific user-agent token first — Edge before Chrome, Chrome before Safari — because every Chromium browser carries the earlier names in its UA. Everything runs locally; nothing is transmitted or stored.
Open Device & Browser Dashboard on AltFTool — it loads instantly in your browser.
Load the dashboard: it reads your user-agent, viewport, screen size and time zone locally, with nothing uploaded.
Read the Privacy signals card for your score out of 100, then the Web API support table covering all 23 probes.
Press Copy report for a plain-text snapshot, or Re-scan after changing a browser setting to compare the two.
Edge, Opera, Samsung Internet and Vivaldi are identified rather than collapsed into Chrome.
Every API row is a live probe of the actual object, so it reflects this browser, not a compatibility table.
All values are read in the browser and discarded on navigation — no network request is made.
For historical compatibility. Chrome's UA contains "AppleWebKit", "KHTML, like Gecko" and "Safari" so that servers written for older engines would serve it the modern site. Edge adds "Edg/" on top of the full Chrome string. That is why detection must match the most specific token first, and why feature detection beats UA sniffing in production.
GPC is a header and a JavaScript flag saying you opt out of the sale or sharing of your personal data. Unlike Do Not Track it has legal force in some jurisdictions — California's Attorney General and Colorado's privacy rules both treat it as a valid opt-out request. This dashboard reports whether your browser exposes the flag, but the security score here is built only from secure-context, cross-origin isolation, cookie and Do Not Track signals — it does not currently weight GPC.
You can reduce it, not eliminate it. Firefox's resist-fingerprinting mode and Safari's protections round or omit screen size, deviceMemory and hardwareConcurrency; Chromium exposes all three. Whether cookies are enabled at all is worth 10 of the 100 points in the security score here — this dashboard does not distinguish first-party from third-party cookie blocking.
No. The screen is the physical display in CSS pixels; the viewport is the part of the page you can see, which is smaller by the browser chrome and any open panels. Responsive breakpoints react to the viewport, which is why the breakpoint shown here follows the viewport width — 640, 768, 1024, 1280 and 1536 pixels in Tailwind's default scale.