About browsers and devices
CPU, memory, and touch
Logical CPU, approximate memory, and touch support exposed by the browser.
Updated: October 9, 2026
CPU shows the logical processor count exposed by navigator.hardwareConcurrency. For privacy or scheduling, a browser may report fewer than the actual logical cores.
Memory
On supported browsers, Memory is the approximate capacity from navigator.deviceMemory. It is rounded and is neither exact installed memory nor currently free memory.
Touch
Touch checks whether navigator.maxTouchPoints is greater than zero. It suggests touch input support but does not mean a mouse or keyboard is unavailable.
How NetKarte shows them
Check CPU, Memory, and Touch in NetKarte's Device card. Read numerical values and availability separately; an unavailable value does not mean zero or absent hardware.
These are browser-exposed estimates. NetKarte does not access hardware directly, infer a device model, or run a performance benchmark.
Lower than the specification does not mean broken
An illustrative CPU 8 and Memory 8 GB do not mean eight physical cores and 8 GB free memory. They are exposed logical processors and, where supported, approximate memory. Unavailable memory is not absent memory.
Use OS system information for installed capacity and OS monitoring for current load. NetKarte runs no heavy performance benchmark. Touch availability does not mean the current input is a finger; a device may also use a mouse. Do not restrict site controls based only on this boolean.
References
- MDN Web Docs: Navigator.hardwareConcurrency (External site)Checked: 2026-10-09
- MDN Web Docs: Navigator.maxTouchPoints (External site)Checked: 2026-10-09
- W3C: Device Memory (External site)Checked: 2026-10-09