DeviceChecker

Browser & Device Information

Instant, private telemetry about your web browser, screen resolution, operating system, and device capabilities with zero setup and zero data uploaded.

Client Telemetry Loaded Instantly

Evaluated strictly in your local browser memory. Zero data uploaded.

Browser Identity

Detected Browser:
Best-effort interpretation
Operating System:
Client Hints (W3C):

Screen & Display

Physical Screen Resolution:
Available Screen Space:
Active Viewport (Live):
Device Pixel Ratio:
Color Depth:

System & Hardware

CPU Logical Cores:
Timezone:
Language:
Touch Input:
Online Status:

Web Diagnostic Capabilities

WebRTC

Camera & microphone media streaming

Test Camera
Web Audio API

Volume metering & tone synthesis

Test Speaker
WebGL

Hardware-accelerated 2D/3D graphics

Checking...
LocalStorage

Client-side persistent offline cache

Checking...
Service Workers

Background synchronization & PWA

Checking...
Raw User-Agent String (Ground Truth)Direct from navigator.userAgent

Note on browser signatures: Modern web browsers freeze and reduce the User-Agent string to prevent cross-site tracking. Chromium-based browsers (including Brave, Microsoft Edge, and Opera) often report as "Chrome" in their raw strings by design.

What This Shows You

01

Browser Identity

Inspect your browser name, release version, and operating system. We prefer modern W3C Client Hints and provide the raw User-Agent as ground truth.

02

Screen & Viewport

View physical monitor resolution, available workspace, active browser viewport, device pixel ratio (DPR), and display color bit depth.

03

System & Web Features

Confirm your CPU core count, device memory (if exposed), timezone, and verify support for WebRTC, Web Audio API, WebGL, and LocalStorage.

Understanding Your Results

Device telemetry in modern web browsers balances website compatibility with user privacy. Understanding how these values are read ensures accurate interpretation.

Best-Effort vs. Ground Truth

  • The raw User-Agent is the literal string your browser dispatches.
  • Friendly browser titles are best-effort interpretations.
  • Chromium browsers (Brave, Edge, Opera) intentionally share Chrome tokens for compatibility and anti-tracking.

Display Scaling & CSS Pixels

  • Browsers report layout dimensions in virtual CSS pixels, not physical LED dots.
  • Multiply reported resolution by the Device Pixel Ratio (e.g. 2x on Retina) to get true panel pixel counts.
  • Window zoom (Ctrl +/-) dynamically adjusts the active viewport size.

Browser & Device Telemetry Edge Cases

Explanations for unexpected values, display scaling math, Chromium browser signatures, and privacy API omissions.

Browser is detected as Google Chrome, but you are using another browser
This is expected behavior for Chromium-based browsers like Brave, Opera, Vivaldi, or Microsoft Edge. These browsers share the underlying Blink engine and deliberately retain Chrome signatures in their User-Agent for compatibility. Look at the raw User-Agent string below the cards for ground-truth inspection.
Reported screen resolution looks smaller than your actual monitor
Your operating system display scaling is active (e.g., 125% or 150% in Windows Display Settings, or scaled mode on macOS Retina). The browser reports CSS pixels. To calculate physical resolution, multiply the reported width and height by the displayed Device Pixel Ratio (DPR).
Viewport dimensions change when zooming or resizing the window
The active viewport (`window.innerWidth` and `innerHeight`) reflects the current visible web page area. Zooming the page (Ctrl + / Ctrl -) changes the virtual pixel ratio, dynamically recalculating the viewport dimensions in real time.
Timezone or language does not match your physical location
Web browsers report the timezone and locale set in your operating system regional preferences or masked by active VPN services and anti-fingerprinting privacy browser extensions, rather than querying your physical GPS location.
Device RAM or CPU cores row is missing or unlisted
`navigator.deviceMemory` is a Chromium-only property. Apple Safari and Mozilla Firefox deliberately do not implement device memory reporting to protect user privacy. When an API is unsupported by your browser, DeviceChecker cleanly omits the row rather than displaying a misleading placeholder.
WebRTC or Web Audio API marked as Unsupported
If WebRTC or Web Audio API are marked as unsupported, check whether you are using a hardened privacy browser (like Tor or LibreWolf), or if enterprise IT group policies or content-blocking extensions have disabled media streaming interfaces.

Frequently Asked Questions About Browser & Device Info

Honest answers about browser detection limits, IP address privacy, exposed device properties, and display scaling.

Is my IP address or physical location tracked or shown here?
No. DeviceChecker does not look up, collect, log, or display your public IP address or geographic location. All telemetry shown on this page is evaluated directly inside your local browser memory using native HTML5 and W3C JavaScript APIs. No data is transmitted across the internet.
Can any website see this device information without asking for permission?
Yes. Standard browser properties like screen resolution, active viewport, preferred language, timezone, and user-agent are routinely exposed by all web browsers to enable responsive layout formatting and regional localization. This is standard web architecture and explains why this tool displays your setup instantly without needing permission dialogs.
Why does the tool show Google Chrome if I am using Brave, Microsoft Edge, or Opera?
Brave, Microsoft Edge, Opera, and Vivaldi are built on the open-source Chromium platform. To prevent older websites from artificially blocking non-Chrome browsers, and as part of modern User-Agent reduction privacy standards, Chromium browsers intentionally include the "Chrome" token in their user-agent strings. We label friendly browser names as best-effort interpretations for this reason.
Why does my reported screen resolution differ from my monitor’s advertised 4K or 1080p specs?
Modern high-density displays (such as Apple Retina screens, 4K monitors, and high-end smartphones) use Display Scaling (e.g., 125%, 150%, or 200%). Web browsers report dimensions in virtual CSS pixels (`screen.width`). Multiplying the reported resolution by the Device Pixel Ratio (DPR) yields your physical display panel pixel count.
What is the difference between User-Agent Client Hints and the traditional User-Agent string?
The legacy `navigator.userAgent` string is a monolithic text line originally created in the 1990s that became bloated and prone to passive tracking. User-Agent Client Hints (`navigator.userAgentData`) is a modern W3C standard that allows browsers to provide structured, granular brand and platform details cleanly without leaking excessive device information.
Does DeviceChecker use canvas or WebGL fingerprinting on this page?
Never. DeviceChecker adheres strictly to a privacy-first engineering boundary. We do not use canvas rendering, WebGL vendor string inspection, audio buffer hashing, or font enumeration techniques. We strictly display standard, already-exposed browser and screen properties.

Browser API Support & Standardization

Confirmed cross-browser availability of native W3C Screen, Navigator, and Client Hints interfaces.

Browser hardware API feature support breakdown
Feature / DiagnosticChromeFirefoxSafariEdgeNotes
Screen & Viewport APIs (screen.width, window.innerWidth)FullFullFullFullUniversal W3C standard supported across all modern desktop and mobile browsers.
Navigator Language & Timezone (Intl DateTimeFormat)FullFullFullFullStandardized ECMAScript internationalization and navigator locale reporting.
User-Agent Client Hints (navigator.userAgentData)FullNoneNoneFullModern structured Client Hints supported in Chromium browsers; Safari and Firefox use traditional UA strings.
Hardware Concurrency (navigator.hardwareConcurrency)FullFullFullFullExposes logical CPU core count; may be clamped in private browsing modes for anti-fingerprinting.

Now that you know your browser setup, test your physical hardware peripherals quickly and privately.