FPS and frame time
FPS is easy to read, but frame-time consistency is equally important. Spikes can reveal stalls even when the average FPS remains high.
WebGPU
WebGPU on this device
WebGPU is not normally a separate download. Support comes from your browser, operating system, GPU driver and graphics hardware.
CamMicGo stress engine
WebGL 2 for cross-browser consistency
Why WebGPU can be interesting
WebGPU is the modern successor to WebGL. It maps better to modern GPU APIs, supports compute workloads and can reduce CPU-side overhead in well-designed applications. It is not automatically faster in every test.
GPU Stress Test
Load your graphics hardware from the browser and watch frame rate, frame pacing, artifacts and device stability.
This is a stability and behavior test, not a benchmark or GPU ranking.
Graphics hardware
Detecting...
Unavailable · WebGPUUnavailable · WebGL 2Unavailable · WebGL 1
Rendering engine
Selected engine: WebGL 2. Results from different APIs should not be treated as identical benchmark scores.
Your device can get hot during this test
GPU load can increase temperature, fan speed and battery drain. Phones and thin laptops may reduce performance by design.
— FPSLevel 1/100sWebGL 2
The stress scene appears here once you start.
Current FPS
—
Average FPS
—
1% low
—
Dropped samples
—
First → last
—
FPS versus display refresh
Dynamic scale: small FPS changes are magnified so a real decline is easy to see.
Blue: measured FPSDashed blue: display refreshAmber: automatic drop thresholdRed dots: samples below threshold
Threshold, not a score
If the Ramp stops at level 4, it means this scene stopped matching the display refresh there. It does not mean your GPU scored 4 out of 10.
Why the line may stay flat
At 60 Hz, the browser is normally synchronized near 60 FPS until the workload finally becomes too heavy. The zoomed scale makes the first decline much easier to spot.
API matters
WebGPU and WebGL 2 use different browser and driver paths. Compare repeat runs within the same API rather than treating the two as interchangeable benchmarks.
How the progressive GPU load works
CamMicGo increases the graphics work required for each frame until the browser can no longer sustain the target fluidity.
Shader: a small program executed by the GPU to calculate colours, shapes, lighting and visual effects.
Full-screen pass: one complete processing pass over the test image. More passes mean more GPU work per frame.
Load is not watts, kilograms or a guaranteed GPU-usage percentage. It is a reproducible CamMicGo workload made from shader calculations and full-screen passes.
Estimated refresh rate: inferred from browser animation timing. It is not a guaranteed monitor specification read directly from the hardware. The drop threshold is currently about 88% of this estimated rate.
Glossary
Thermal throttling
Automatic GPU speed reduction when temperature becomes too high.
FPS
Frames per second rendered by the browser.
1% low
The slowest 1% of measurements; useful for spotting brief stalls.
Frame time
Time needed to produce one frame.
WebGPU / WebGL 2
Two browser graphics APIs that use different software and driver paths.
Drop threshold
The FPS level below which CamMicGo considers the estimated display target no longer sustained.
Current formula: shader iterations = 24 + (step × 14); full-screen passes = round(1 + step × 1.35). A step is a CamMicGo workload stage, not a physical unit or universal score.