Skip to main content
I/O Checkup
System ready

GPU WORKLOAD LIBRARY

GPU Stress Tests

Find the right workload. See how your browser handles it.

Explore 15 graphics and compute workloads, each with its own live scene, adjustable settings, and readable results. Start small, then choose the path you want to investigate.

15dedicated workloadsNo installationRuns stay local
Explore all workloads
NEW HERE? START WITH THISWebGL

Workload illustration

Volume shader

An easy first look: watch a ray-marched scene while the tool records frame delivery. Begin with the 15-second quick check; increase the load only when you are comfortable.

Try the volume shader

01 / WORKLOAD SELECTOR

Different workloads. Different questions.

Choose by what you want to explore. Every card opens a dedicated tool—not a test running in the background.

15 / 15 tests shown

Rendering & effects

Explore the work behind pixels, light, and multi-pass effects.

WebGL

Volume shader

Trace rays through a mathematical volume; control detail and sampling steps.

Choose this forA visual first check and adjustable pixel load
Open this workload
WebGL

Shader arithmetic

Repeat pixel shader calculations to vary arithmetic cost.

Choose this forIncreasing calculation work per pixel
Open this workload
WebGL

Shader ray tracing

Trace a small procedural scene in a shader; no hardware ray-tracing claim.

Choose this forShader-based rays and reflection work
Open this workload
WebGL

Post-processing passes

Apply image effects through repeated render passes.

Choose this forLayering effects and render passes
Open this workload
WebGL

Lighting and shadows

Increase shader lighting and shadow sampling work.

Choose this forMore lights and shadow samples
Open this workload

Geometry & particles

Explore triangles, repeated objects, and busy particle scenes.

WebGL

Geometry throughput

Submit triangles and observe browser rendering throughput.

Choose this forDense scenes and triangle load
Open this workload
WebGL

Instanced objects

Draw repeated objects with shared geometry and per-instance transforms.

Choose this forMany copies of shared geometry
Open this workload
WebGL

Particle field

Render many moving points; vary particle count and pixel load.

Choose this forLarge fields of moving points
Open this workload

Textures & transfers

Explore sampling, uploads, and a bounded readback check.

WebGL

Texture sampling

Sample generated textures within the selected allocation budget.

Choose this forTexture sampling under a set memory budget
Open this workload
WebGL

Texture round-trip check

Write known texture patterns and compare sampled readback values. This does not test all physical VRAM.

Choose this forChecking sampled texture write/read results
Open this workload
WebGL

Texture upload

Transfer generated pixel data into textures during the run.

Choose this forRepeated pixel-data transfers
Open this workload

Compute & simulation

Separate GPU compute from a mixed CPU/GPU simulation.

CPU + GPU workload

Particle simulation

Simulate gravity and collisions on the CPU, then draw particles on the GPU. This measures a mixed workload.

Choose this forCPU simulation plus GPU rendering
Open this workload
WebGPU

WebGPU compute

Run a WebGPU compute kernel and inspect its returned values and timing.

Choose this forGPU compute on a WebGPU-capable browser
Open this workload

Video & experiments

Use your own local video or explore an editable shader.

Local video playback

Local video playback

Observe frame delivery from a video selected on this device. The file is not uploaded; this does not prove hardware decoding.

Choose this forLocal video delivery and dropped frames
Open this workload
Editable WebGL shader

Custom shader

Edit a local shader experiment. Results are separate from standard benchmarks.

Choose this forExploring your own fragment shader
Open this workload

02 / Before you begin

A useful run in three steps

  1. 01

    Pick one path

    Choose a workload that matches your question. Use the quick check and a low preset for your first run.

  2. 02

    Change one thing

    Adjust resolution or load—not everything at once. Keep this tab visible and pause other demanding tasks.

  3. 03

    Read the pattern

    Look at frame timing across the run, then repeat with matching settings. One number is not a hardware diagnosis.

03 / READ THE SIGNALS

Read the result, not just the score.

FPS: delivery rate

How many frames the browser delivers per second. Display refresh, the browser, and CPU work can all limit this number.

Frame time: consistency

The interval between frames. Spikes reveal uneven delivery that an average FPS can hide; they are not GPU-only timings.

Slowdown: change over time

Compares earlier and later parts of one run. A drop calls for a repeat—not an automatic diagnosis of overheating.

Want a repeatable comparison?

Use the standard GPU benchmark. Locked settings make matching runs easier to compare than an adjustable stress test.

Open the standard benchmark

04 / GPU Tests

Before you test

Stress test or benchmark: which should I choose?

A stress test lets you vary the load and observe behavior over time. A standard benchmark fixes settings for repeatable comparisons. Compare only the same workload, version, API, settings, and timing method.

Can this measure GPU temperature or test all VRAM?

No. Browser APIs do not expose GPU temperature, power, or total physical VRAM here. The texture check compares sampled readback values within its allocation budget; it is not a complete memory or hardware-health test.

Does low FPS mean my GPU is faulty?

No. A heavy workload, refresh limits, CPU work, power settings, background tasks, or browser scheduling can lower FPS. Repeat a matching run and check hardware acceleration before drawing conclusions.

Are my runs or files uploaded automatically?

No. Runs and reports stay in this browser by default, and selected video files are not uploaded. Public result sharing is optional and requires explicit consent; read the privacy policy before publishing.