CPU Stress Test

Load every thread from your browser and see whether throughput holds or drops as the processor heats up. This is a load test, not a benchmark.

About the CPU Load Test

This page puts your processor under heavy load and shows whether it keeps its pace.

A load test, not a benchmark

Each worker runs an arithmetic loop as fast as the browser allows and counts the passes. The count depends on the browser, its version and what else is running, so it isn't a score. Use it to compare this machine with itself during the run.

Watch for a drop in throughput

Throughput rises for a few seconds, then levels off. If it holds for five minutes, the machine sustains the load. If it drops and stays down, heat, a power limit or a battery saver is slowing the chip. The page reports this once it has enough data.

What a browser can't read

No web page can read temperatures, clock speeds, fan speeds or the processor model. The browser reports only the thread count, and Safari and private modes lower even that. For temperatures, run a monitoring app next to this page.

All cores, or just one

All threads heat the whole chip, which is how you test cooling. One thread leaves the other cores idle, so that core reaches its highest boost clock. The system picks the core: a web page can't choose it.

Why there is an intensity slider

Some faults appear only at partial load, and a fan curve is easier to hear at a steady 40%. The slider makes each worker compute for part of every 100 ms and idle for the rest.

Is it safe to run

Yes. Thermal and power protection in the hardware slows the chip down or shuts the machine off before any damage. Expect heat, loud fans and, on a laptop, fast battery drain. If the machine shuts down during a run, the cooling or the power supply isn't coping.

Stress the graphics card too?
Load the graphics card in the browser and watch for artifacts, driver resets and falling frame rates.
Open the GPU test
Checking the whole machine?
Dead pixels, refresh rate, backlight bleed and more display tests in one place.
Open the screen test

When to run a CPU load test

Frequently asked questions

Choose the run length, threads and intensity, then press Start. Each thread runs an arithmetic loop and the page shows how fast. Keep the tab in front: browsers slow down background tabs.
No. The figure is loop passes per second in your browser's JavaScript engine, and it changes with the browser and its version. Compare it only with itself during the run.
No. The chip slows itself down when it gets too hot, and the machine shuts off if that isn't enough. Expect heat, fan noise and, on a laptop, fast battery drain.
No. Web pages can't read temperatures, clock speeds or fan speeds. Run a monitor next to this page: HWiNFO or Core Temp on Windows, Stats or iStat Menus on macOS, lm-sensors on Linux.
Browsers report logical threads, not physical cores. Safari and private modes lower the number, and hybrid chips count performance and efficiency cores together. It's enough to size the load, but don't quote it as your core count.
The machine couldn't keep the pace it settled at after the first minute. Usually it's heat: dust in the fans, dried thermal paste or a blocked vent. A power limit, a battery saver or another program look the same, so check with a temperature monitor.
All threads to test cooling, one thread to see the highest single-core boost. The system picks the core, so a single-thread run tells you about the chip, not one specific core. The run panel shows each thread separately.
One minute is enough to hear the fans. For heat, run at least five: most laptops throttle in the third or fourth minute. For faults that show up later, use Endurance and keep the tab in front.
No. The load runs in Web Workers, separate from the page. With all threads loaded the page may feel a little slower, but Stop always works and ends the load at once.