What Is a Device Information Tool?
This tool reads several real hardware-related signals your browser exposes: how many logical CPU cores your processor has, an approximate memory bucket your browser reports, your reported platform string, and how many simultaneous touch points your screen supports. Each value comes directly from a standard browser API - nothing here is looked up, estimated from a device database, or guessed.
How to Use the Device Information Tool
- Load this page - every field populates automatically from your current device.
- Check "Logical CPU Cores" to see how many processing threads your browser can access.
- Check "Approx. Device Memory" for a rough memory bucket, where supported.
- Use "Max Touch Points" and "Device Type Guess" to confirm whether your device is being detected as touch-capable.
How It Works
CPU core count comes from navigator.hardwareConcurrency, which reports the number of
logical processor cores available to the browser - this can differ from your CPU's physical core count on
processors with hyperthreading or similar technology. Device memory comes from
navigator.deviceMemory, a Chromium-specific API that deliberately reports a rounded, approximate
figure (like 4, 8, or 16) rather than your exact installed RAM, as a privacy measure against precise device
fingerprinting. Touch capability comes from navigator.maxTouchPoints, and the device type guess
combines that with a CSS media query checking whether your primary pointing device is "coarse" (like a
finger) or "fine" (like a mouse).
Understanding Your Results
- CPU core count matches your processor's known thread count - your browser is correctly reporting available logical processors.
- Device memory shows a round number like 4 or 8 - expected behavior; this API intentionally reports an approximate bucket rather than your exact RAM amount, and caps out at 8GB in some browsers regardless of actual installed memory, again for privacy reasons.
- "Not reported" for Device Memory - this API is currently Chromium-specific; Firefox and Safari don't implement it.
- Device Type Guess doesn't match your actual device - some hybrid devices, like touchscreen laptops used with a mouse, can produce ambiguous signals that this heuristic doesn't always classify perfectly.
Browser Limitations
Several of these APIs are intentionally imprecise by design - both hardwareConcurrency and
deviceMemory can be capped or rounded by browsers specifically to reduce how precisely a
website can fingerprint your exact hardware configuration. This tool reports exactly what the browser
chooses to reveal, which is not always your device's true, exact specification.
Common Mistakes to Avoid
- Treating Device Memory as your exact installed RAM - it's a deliberately rounded, capped approximation, not a precise reading.
- Assuming CPU core count equals physical cores - hyperthreading and similar technologies mean logical core count often exceeds physical core count.
- Expecting these values in every browser - several are Chromium-specific and will show "Not reported" in Firefox or Safari.
Frequently Asked Questions
Why does Device Memory show a round number like 8, not my exact RAM amount?
This API is intentionally designed to report an approximate, rounded bucket rather than exact RAM, as a privacy measure to limit precise device fingerprinting.
Why doesn't Firefox show a Device Memory value?
The Device Memory API is currently a Chromium-specific feature and isn't implemented in Firefox or Safari.
Does logical CPU core count equal my processor's physical core count?
Not necessarily - many modern CPUs use hyperthreading or similar technology, which makes each physical core appear as two logical cores to software, including the browser.
Is any of this hardware data sent anywhere?
No. Everything is read and displayed entirely within your browser and is never transmitted or stored.
Why does my touchscreen laptop show as a non-touch device?
The device type guess relies on your primary pointer type reported through a CSS media query; a touchscreen laptop primarily used with a mouse or trackpad may report a "fine" pointer as primary even though it also has touch capability.
Conclusion
For a quick, genuine snapshot of what your browser can see about your device's processing power, memory, and input capability, this gives you the real available data - with an honest explanation of where and why it's intentionally approximate. For actual processing speed rather than core count, try the CPU Benchmark.