Browser Inspector
Comprehensive system, browser, and device information detection
Frequently Asked Questions
What information does the Browser Inspector collect about me?
The Browser Inspector reads device and browser capabilities directly available to any web page through standard browser APIs — such as screen resolution, user agent string, JavaScript engine, and hardware concurrency. No private data, location, or personal identifiers are accessed.
Is the collected browser data sent to your servers?
No. All the browser and device data displayed is read client-side and rendered directly in your browser. None of it is transmitted to our servers, analytics platforms, or third-party services.
Why would a developer need to know the browser user agent?
The user agent string helps developers diagnose rendering issues, test conditional browser support, build allowlists for API access, and confirm which browser features are available. It is commonly used in customer support, QA testing, and security auditing.
How Data is Collected
All information is collected via browser JavaScript APIs — no software is installed and nothing is sent to a server. APIs used include: navigator (browser, OS, language, platform), screen (resolution, color depth), window (viewport, device pixel ratio), and feature-detection checks for supported APIs.
Browser Detection
Browser name and version are determined by parsing the navigator.userAgent string combined with vendor-specific object checks (e.g., window.chrome, window.safari). User-agent strings can be spoofed — this tool shows what the browser reports, which may not always reflect the actual browser in use.
Feature Detection
Web API support is tested by checking for the existence of API objects and methods: serviceWorker in navigator, WebSocket, RTCPeerConnection, AudioContext, WebGLRenderingContext, Bluetooth, etc. Positive detection means the API is available; it doesn't guarantee it will work without the appropriate permissions.
Privacy Considerations
The combination of browser, OS, screen resolution, timezone, language, and installed plugins can create a unique "browser fingerprint" that websites may use to track you across sessions — even without cookies. Tools like Firefox's Enhanced Tracking Protection and the Tor Browser reduce fingerprinting surface by standardizing reported values.