Device overview
Read browser-visible screen, processor, memory, language, connectivity, and platform signals in one place.
Open testA practical first-day sequence for confirming the visible specification, display, keyboard, pointing device, camera, microphone, audio, battery report, and graphics path.
Read browser-visible screen, processor, memory, language, connectivity, and platform signals in one place.
Open testInspect viewport size, screen resolution, pixel ratio, orientation, color depth, and fullscreen behavior.
Open testCycle solid red, green, blue, white, black, and neutral backgrounds to inspect the panel edge to edge.
Open testUse black and low-gray fields to inspect bright corners, edge leakage, clouding, and viewing-angle effects.
Open testRecord keydown and keyup events, inspect codes, and see how many simultaneous keys the browser receives.
Open testVerify pointer movement, primary and auxiliary buttons, wheel direction, double clicks, and browser-reported coordinates.
Open testOpen a local camera preview, inspect reported track settings, switch devices, and confirm permission behavior.
Open testOpen a local microphone stream, view a live level meter, inspect track settings, and verify stop behavior.
Open testPlay short, low-level left, right, and centered tones to verify channel routing and obvious distortion.
Open testParse a locally selected Windows battery-report HTML file for design capacity, full-charge capacity, cycle count, and a simple health ratio.
Open testCreate a local WebGL context, inspect limits and extensions, and run a brief animation workload.
Open testWhat to verify while return and exchange options are still simple: identity, exterior, display, input, media, battery evidence, ports, updates, and recovery.
Read guideA browser can verify useful behavior without becoming firmware diagnostics, a lab instrument, a repair tool, or proof of internal component identity.
Read guide