CPU Stress Test

Stress test your CPU in the browser with one Web Worker per core. Pick a thread count, watch live operations per second, and get an instant performance score.

This runs heavy math on every selected core at full speed. Fan noise, warmth, and battery drain are normal, and the page may feel less responsive at maximum threads. Stop the test if your device gets too hot.

Worker threads

4 logical cores detected

Loads every core at once

Choose how many threads to load and press Start to begin.

See How Your Processor Handles Real Sustained Load

A processor spends most of its life far below its limits, so problems like overheating, aggressive throttling, or a weak core only show up under sustained pressure. This test creates that pressure safely in your browser: each selected thread runs an endless stream of integer and floating-point math, the same kind of work that video encoding, compiling, and simulations throw at a CPU. Start with a single thread to get a baseline, then load every core and watch how the numbers hold up.

Why Use This CPU Test?

One Worker per Core

The test spawns a real Web Worker for every thread you select, so the load lands on separate cores instead of fighting over one.

Single-Core vs All-Core

Run one thread first, then all of them, and compare. The gap between the two numbers tells you how well your CPU scales under full load.

Live Throughput Tracking

Current, average, and peak operations per second update in real time, so a sudden drop from thermal throttling is visible the moment it happens.

No Install, No Upload

Everything runs inside your browser tab. Stop the test for an instant score without downloads, sign-ups, or any data leaving your device.

How this CPU Stress Test works

When you press start, the tool creates one Web Worker for every thread you selected. A Web Worker is a separate JavaScript thread that the browser is free to schedule on its own CPU core, which is what makes a genuine multi-core test possible inside a web page. Each worker immediately enters an endless loop of work: it scrambles a number with bit-shifting operations, takes a square root, and repeats, mixing the integer and floating-point math that real programs rely on.

Every fifth of a second, each worker reports how many operations it finished since its last report. The page adds up these reports across all workers and converts the total into millions of operations per second. It keeps a short rolling window of recent samples for the current reading, a running total for the average, and remembers the single best second as the peak, since one instantaneous number on its own can be misleading.

The number of logical cores comes from the hardwareConcurrency value your browser exposes, which counts hardware threads rather than physical cores. When you stop the test, every worker is terminated instantly and the average throughput per thread is compared against a typical browser target to produce a plain-language score.

The workload never touches your files, network, or hardware settings. It is ordinary JavaScript math running in the browser sandbox, and closing the tab ends it completely.

How to use this CPU Stress Test

1

Choose your threads

Pick how many worker threads to run, from a single core up to every logical core your browser detects.

2

Start the load

Press start and watch live operations per second while every selected thread crunches math at full speed.

3

Stop and compare

Stop the test anytime for a performance score, then rerun with different thread counts to see how your CPU scales.

Frequently Asked Questions

Is it safe to stress test my CPU in a browser?
Yes. The test runs ordinary JavaScript inside the browser sandbox, and your operating system stays in charge of scheduling. Every modern processor also has built-in thermal protection that lowers its clock speed automatically before heat can become a problem.
Can this test damage or overheat my computer?
No. The workload is the same kind of math that video exports, games, and compilers run for much longer periods. If temperatures climb, the CPU throttles itself down; the worst realistic outcome is louder fans and a slower tab, not hardware damage.
Why is the all-core result not simply the single-core result multiplied by my core count?
Three reasons: hyperthreading counts two logical cores per physical core but they share hardware, boost clocks are higher when only one core is active, and heat builds up faster under full load. A total that scales to 60 or 70 percent of the theoretical maximum is normal for most machines.
What does the test actually calculate?
Each worker thread repeatedly scrambles a number using bit-shift operations and then takes a square root, in an endless loop. This mixes integer and floating-point work, which resembles what real software does far more closely than a single repeated instruction would.
Why do my numbers drop after the first minute?
That is almost always thermal throttling: the CPU starts at its boost clock, heats up, and settles at a lower sustained speed. Watching how far the number falls is actually one of the most useful things this test shows, especially on thin laptops.
My fans got loud during the test. Is that normal?
Yes. Full load on all cores makes any processor draw more power and produce more heat, and the fans respond immediately. It is the same behavior you would see during a long video export. Everything returns to normal within seconds of stopping the test.
Why does my result differ from a friend with the same CPU?
Browser version, background programs, power plan, and cooling all move the numbers. A laptop on battery power can lose a large share of its performance to energy saving alone. For fair comparisons, use the same browser, power settings, and thread count.
Is this as accurate as Cinebench or Prime95?
No, and it does not try to be. Desktop benchmarks run optimized native code and can read temperatures and clock speeds directly, which a browser cannot. Treat this as a quick, no-install way to check behavior under load, not as a lab-grade measurement.
Does the test work on phones and tablets?
Yes, in any modern mobile browser. Expect lower numbers and earlier throttling than on a desktop, since phones rely on passive cooling. Keeping the screen awake during the run gives the most consistent readings.
What is a logical core, and why does the tool show more cores than my CPU has?
Browsers report hardware threads, not physical cores. Many CPUs run two threads per core using hyperthreading or SMT, so an 8-core processor often shows up as 16. Note that some browsers also cap or round this value for privacy reasons.
Does closing the tab stop the test immediately?
Yes. The worker threads exist only inside the page, so closing the tab or navigating away terminates all of them instantly. Nothing keeps running in the background afterwards.
When is a browser CPU test actually useful?
It is a quick way to check whether throttling has gotten worse after a repair or repaste, to compare power modes on a laptop, to verify that all cores respond under load, or to see how much performance battery mode really costs you.

Related Tools

The CPU Stress Test is maintained by CodeItBro. We aim to provide the best free developer tools on the web. If you have feedback or suggestions, please visit our contact page.

Comments

Questions, corrections, and useful tips are welcome. Comments are reviewed before publication.

Loading comments...

Comments are stored and moderated using Cusdis Cloud. Email is optional. Privacy Policy

As featured on

CodeItBro - Free dev tools + practical guides to help you ship faster | Product HuntCodeItBro - Free Online Developer Tools badgeCodeItBro badge