Before assuming a component is broken, ChromeOS has a built-in Diagnostics app that tests hardware directly — no downloads, no third-party tools. Here’s how to find it and read the results.
How to Open the Diagnostics App
- Click the launcher (circle icon) and type “Diagnostics.”
- Alternatively, go to Settings > About ChromeOS, then click Diagnostics in the left sidebar.
- The app opens with four main tabs: System, Battery, CPU, Memory, Connectivity, and Input (input appears only on models with supported hardware).
Battery Test
- Open the Battery tab to see current charge percentage, cycle count, and battery health as a percentage of original design capacity.
- Run the “Battery discharge test” while unplugged to measure real-world drain over a set period — useful for confirming a battery that’s degrading faster than it should.
- Compare the reported design capacity against your model’s spec sheet; anything below roughly 80% of original capacity explains noticeably shorter runtime.
For deeper battery diagnosis and what the numbers mean, see our Battery Health Check guide.
CPU and Memory Tests
- Open the CPU tab and click “Run test” to stress-test all cores — useful for confirming overheating or throttling issues under load.
- Watch the temperature readout during the test; sustained high temperatures paired with a sudden frequency drop indicates thermal throttling, not a fault, but repeated shutdowns during the test point to a cooling problem.
- Open the Memory tab and run the RAM test, which can take several minutes — this checks for faulty memory that could cause random crashes or freezes.
Connectivity Test
- Open the Connectivity tab to see current Wi-Fi signal strength, IP address, and connection speed without opening a separate speed-test website.
- If Bluetooth devices are paired, their connection status also appears here — useful for confirming whether a mouse or headphones dropout is a Bluetooth radio issue.
Input Test (Keyboard and Touchpad)
- On supported models, an Input tab lets you run a keyboard test that highlights each key as you press it, confirming which specific keys aren’t registering.
- The touchpad test shows a heatmap-style grid — move your finger across the full pad to confirm every zone responds, which helps pinpoint a partially dead trackpad sensor.
This is the exact test referenced in our hardware repair guides — for example, confirming a trackpad replacement is actually needed rather than a software glitch.
Still Seeing Problems After Testing?
A failed battery, CPU, or memory test confirms a hardware issue — at that point, check our relevant repair guides rather than trying more software fixes. A passed test with symptoms still present usually points back to software: try the steps in our Chromebook running slow guide for performance complaints that don’t show up as a hardware fault.
FAQ
Does running Diagnostics tests use a lot of battery?
The CPU and memory stress tests do draw more power than normal use, and it’s best to run them plugged in so a mid-test shutdown doesn’t skew results.
Why don’t I see an Input tab?
The keyboard and touchpad test is only available on newer models with supported firmware. Its absence doesn’t mean anything is wrong — just that your model isn’t in the supported list yet.
Can Diagnostics fix problems, or does it only test?
It’s test-only. It identifies whether a component is faulty but doesn’t repair anything — you’ll still need the relevant fix or replacement guide afterward.
LOG 2 reports