Free Online Hardware Scanner
Inspect your computer's hardware threads, graphics accelerator, and memory tiers. Zero installations required.
Diagnostic Engine Dashboard
Operating Environment
Client platform specifications.
Memory Allocation
Platform and browser memory limits.
Display Metrics
Logical canvas & estimated physical raster.
Graphics Processing Unit (GPU)
Unmasked WebGL hardware adapter query.
Sandboxed Storage Quota
Per-site origin storage allocation.
Real-Time Performance Logging
Dual-axis tracking: Frame Rate (left) vs Memory Heap Usage (right).
Diagnostic Permission Prompt
To audit your system specifications, the scanner will execute client-side Web APIs to measure CPU threads, memory tiers, and graphics acceleration.
Basic Scan: Analyzes logical threads, browser memory limits, and WebGL GPU details safely inside the browser sandbox.
Deep Scan (Allow): Prepares the interface for unmasked parameters and high-precision telemetry.
Complete Guide to Browser-Based Hardware Auditing & System Specifications
Whether you are evaluating a refurbished workstation, troubleshooting a stuttering browser application, verifying whether a device meets minimum video game requirements, or assessing rendering performance, knowing how to quickly audit your hardware is essential. Traditional desktop hardware profilers—such as CPU-Z, HWiNFO, or Speccy—provide exhaustive low-level telemetry, but they require binary installation, administrative root privileges, and platform-specific execution packages. Browser-based hardware diagnostics provide an immediate, zero-install alternative that executes instantly on Windows, macOS, Linux, ChromeOS, iOS, and Android.
Modern browser engines—including Google Chrome, Microsoft Edge, Mozilla Firefox, and Apple Safari—act as virtualized execution environments. Through carefully scoped, standardized Web APIs, browsers interface directly with your physical CPU, graphics card, memory controllers, and display panels. The PC-Tester Hardware Scanner acts as a real-time bridge to this telemetry, organizing raw sandboxed data points into a clean, human-readable system profile.
Core Architecture: How Web Browsers Probe Physical Hardware
Unlike native executable profilers that poll the Windows kernel, query WMI (Windows Management Instrumentation), or read direct ACPI tables, a web application queries standardized client-side interfaces. Below are the primary technical APIs our diagnostic engine utilizes to audit your system:
1. Logical Thread Concurrency (The Processor Pipeline)
Under the WHATWG HTML Living Standard, browsers expose the navigator.hardwareConcurrency property. This integer represents the total number of logical processor cores available to execute tasks and Web Workers concurrently. On modern multi-threaded architectures (such as Intel Hyper-Threading or AMD Simultaneous Multithreading), each physical core hosts two virtual threads. An 8-core / 16-thread processor (like an AMD Ryzen 7 or Intel Core i7) reports 16 threads. Web browsers deliberately abstract the exact model string (e.g., "i7-13700K") to mitigate browser fingerprinting, but thread concurrency offers an accurate measure of your CPU's multi-threaded multitasking throughput.
2. WebGL Hardware Acceleration & ANGLE Unmasked Renderers
To inspect your graphics processing unit (GPU), the scanner instantiates an off-screen HTML5 Canvas and attempts to acquire a webgl2 rendering context with high-performance power preference flags. Under standard specifications, querying the graphics context returns generalized descriptors like "WebGL 2.0 (OpenGL ES 3.0 Chromium)". However, the browser provides the privileged WEBGL_debug_renderer_info extension, which reveals the unmasked GPU vendor and unmasked renderer string.
On Windows workstations, Chromium browsers run ANGLE (Almost Native Graphics Layer Engine), which translates cross-platform WebGL calls into native Direct3D 11, Direct3D 12, or Vulkan API calls. Our engine's parsing pipeline strips hexadecimal hardware device identifiers, Direct3D pipeline noise, and driver strings (e.g., transforming ANGLE (NVIDIA, NVIDIA GeForce RTX 3060 Direct3D11 vs_5_0 ps_5_0, D3D11) into a clean NVIDIA GeForce RTX 3060). If a user has disabled GPU acceleration, our diagnostic flags software CPU fallbacks like Google SwiftShader or Mesa LLVMpipe, warning users that graphical rendering is unaccelerated.
3. Memory Tiers & JavaScript Heap Allocation
Memory auditing in the browser sandbox operates across two distinct layers: system-level RAM classification and execution-level JavaScript Heap tracking. Under the WICG Device Memory Specification, Chromium browsers expose navigator.deviceMemory. To prevent websites from creating high-entropy device fingerprints, this API rounds physical RAM to powers of two (0.25, 0.5, 1, 2, 4, 8) and deliberately caps maximum output at 8 GB. An output of "8 GB or more" indicates your machine has at least 8 GB (such as 16 GB, 32 GB, or 64 GB).
Concurrently, the Chromium-exclusive performance.memory API provides real-time visibility into the memory consumption of the browser engine itself. It reports usedJSHeapSize (active memory occupied by DOM nodes, scripts, and variables) alongside jsHeapSizeLimit (the total allocation ceiling granted to the browser tab). Tracking heap expansion against frame-rate drops allows developers and power users to pinpoint memory leaks and garbage collection stutters.
4. High-DPI Display Rasterization & Touch Topology
Display properties encompass both logical CSS dimensions and physical pixel grids. Modern operating systems frequently utilize High-DPI scaling (such as Windows display scaling at 125%, 150%, or macOS Retina scaling at 200%). The scanner reads window.screen.width and window.screen.height to present the logical desktop workspace. It then calculates an estimated physical panel resolution by factoring in window.devicePixelRatio. Furthermore, querying navigator.maxTouchPoints audits whether your screen hardware contains capacitive digitizers or if the system relies solely on mouse pointer inputs.
Online Browser Scanner vs. Native Operating System Tools
While an online scanner provides immediate, zero-friction audits across any device, native operating systems include built-in diagnostic programs designed for low-level BIOS, motherboard, and component inspection. Use the comparison table below to determine when to use the web scanner versus native tools:
| Diagnostic Parameter | Browser Scanner (pctester.online) | Native Operating System Utility |
|---|---|---|
| Installation Requirement | Zero installation. Instant execution in any browser. | Pre-installed OS binaries or third-party executable profilers. |
| CPU Core & Model Data | Logical threads (e.g. 16 Threads via Concurrency). | Exact silicon marketing model, clock speed, cache sizes (via dxdiag / lscpu). |
| RAM Memory Information | Device tier (up to 8GB+) & live JS heap size. | Exact physical RAM (16GB, 32GB), clock frequency (MHz), DDR generation, and slot counts. |
| Graphics Adapter (GPU) | Unmasked WebGL graphics card & ANGLE translation backend. | Discrete GPU model, dedicated VRAM capacity, driver branch, and bus interface. |
| Thermal & Voltage Sensors | Restricted by browser privacy sandboxes. | Full sensor telemetry: CPU package temperature, fan RPM, and power draw. |
| Storage Drive Volumes | Sandboxed per-origin browser storage quota & IndexedDB. | Physical drive models, NVMe PCIe speeds, partition sizes, and SMART health attributes. |
How to Retrieve Exact CPU & Motherboard Specs Natively
Because web browsers deliberately hide physical motherboard serial numbers and CPU model numbers to prevent tracking, use these fast, built-in operating system commands when you require exact model names for hardware upgrades:
Windows 10 & Windows 11 Diagnostics
- DirectX Diagnostic Tool: Press Windows Key + R, type
dxdiag, and hit Enter. The "System" tab reveals your computer's exact processor brand, clock speed, installed physical RAM, and BIOS build date. The "Display" tab details your GPU model and VRAM limits. - System Information: Press Windows Key + R, type
msinfo32, and hit Enter. This displays the motherboard manufacturer, baseboard model, secure boot state, and BIOS firmware mode (UEFI vs. Legacy). - PowerShell Instant Query: Open PowerShell and execute
Get-CimInstance Win32_Processor | Select-Object Name, NumberOfCores, NumberOfLogicalProcessorsto receive a clean, immediate readout of your exact processor model.
macOS (Apple Silicon & Intel) Diagnostics
- System Information GUI: Click the Apple Menu in the top-left corner > About This Mac > System Report. This provides an exhaustive breakdown of your Apple Silicon chip (M1, M2, M3, M4) or Intel Core processor, unified memory bandwidth, and battery cycle counts.
- Terminal CPU Probe: Open Terminal and execute
sysctl -n machdep.cpu.brand_stringto print your processor's hardware identifier.
Linux Workstations & Servers
- CPU Architecture Audit: Open your shell and execute
lscpu. This outputs socket counts, physical core allocations, threads per core, CPU family, microarchitecture, and L1/L2/L3 cache sizes. - PCI Peripheral Inventory: Execute
lspci -nnk | grep -i vga -A3to isolate your physical GPU controller, kernel driver in use, and kernel modules.
Troubleshooting Hardware Bottlenecks Identified by the Scanner
Interpreting your diagnostic output allows you to troubleshoot hardware degradation and browser performance bottlenecks effectively:
1. Low Rendering Frame Rate (Under 60 FPS)
If the Live Performance chart consistently dips below 60 FPS while running on a standard monitor, inspect the GPU card on the "Graphics & Display" tab. If the ANGLE Backend indicates software emulation (or triggers the red "Hardware Acceleration Disabled" warning), navigate to your browser settings, search for "Hardware Acceleration", enable it, and restart your browser. If acceleration is already active, thermal throttling or intense background tabs may be exhausting your main thread.
2. Device Memory Tier Showing "Untracked"
The navigator.deviceMemory API is supported predominantly in Chromium engines (Chrome, Edge, Brave, Opera). If you are testing within Mozilla Firefox or Apple Safari, memory reporting will read "Untracked". This is normal expected behavior and reflects Mozilla and Apple's strict anti-fingerprinting privacy standards rather than a flaw with your hardware.
3. Display Pixel Discrepancies
If your reported screen dimensions differ from your monitor's manufacturer specifications, check your operating system's display scaling setting. A 3840×2160 (4K) panel running at 150% scaling reports a logical resolution of 2560×1440 px. The scanner displays both logical CSS pixels and estimated physical raster pixels to help developers test responsive media layouts accurately.
Frequently Asked Questions
Why does my processor show logical threads instead of physical CPU model?
Why is my RAM reported as 8 GB or more?
How does the scanner identify my graphics card?
Explore Other Diagnostic Tools
Verify external peripherals, display fidelity, and audio subsystems directly in your browser:
Adeel is a software developer and diagnostic tools specialist with over a decade of hands-on experience building cross-platform utilities, benchmarking suites, and client-side web applications. He leads development at pctester.online with an emphasis on zero-install performance profiling, privacy-respecting architectures, and accessible web standards.