How to Run the Volume Shader BM Test: A Step-by-Step Guide

The Volume Shader BM Test is a free, browser-based GPU benchmark that measures how well your graphics hardware handles complex volumetric effects. Because it runs entirely on WebGL, there is nothing to download or install — you can test a laptop, a desktop, or a phone in under two minutes. This guide walks through every step so that your first run produces numbers you can actually trust.

What you need before you start

The requirements are minimal, which is the whole point of a browser benchmark:

• A device with a modern browser: Chrome, Edge, Firefox, or Safari.
• A GPU driver that is reasonably current (within the last 12 months).
• A few minutes of idle time on the machine.

The test pushes your GPU intentionally hard. That is how it measures performance, but it also means hot or busy machines will report lower scores. Prepare your device before benchmarking.

Step-by-step: run the Volume Shader BM Test

1. Open the benchmark page

From the homepage, click Start GPU Benchmark, or go directly to the run-test page. The tool initializes a WebGL context and detects your renderer. You will see something like the panel below:

API:      WebGL 1
Browser:  Chrome 124
GPU:      ANGLE (NVIDIA, RTX 3060)
OS:       Windows 11

If the GPU line reads Generic WebGL Device, the browser is hiding your hardware for privacy. The benchmark still works — it just cannot label your exact chip.

2. Close everything else

Background apps steal GPU time and skew results. Before you press start:

• Quit games, video editors, and screen recorders.
• Close extra browser tabs, especially media-heavy ones.
• Pause cloud sync and large downloads.
• Plug in laptops — power-saving mode throttles the GPU.

3. Start the default workload

Click Start Benchmark. The current tool uses one default volumetric shader and a fixed 1024 × 1024 drawing buffer. It does not offer separate Basic, Advanced, or Stress presets, resolution scaling, or an automatic duration selector.

For a repeatable short comparison, use the default shader, keep the page visible, and pause after the same amount of active running time, such as 30 seconds. A longer run observes the same workload over time. The shader editor is for custom GLSL geometry; changing its code changes the workload, so label custom results separately.

Use Pause to end the run and CSV or JSON to save its measurements. Restart clears the run for a new comparison. Keep the default camera position unchanged when comparing devices.

4. Read the metrics

While the test runs, watch three numbers:

1. FPS (current) — instantaneous frames per second.
2. FPS (avg) — rendered frames divided by active running time.
3. Frame time — milliseconds per frame; lower and steadier is better.

A stable 60 FPS with tight frame times is a strong result for almost any modern device. Higher resolution always means lower FPS — actually, the benchmark controls its own internal resolution, so do not conflate your desktop resolution with the test resolution.

Interpreting your score

There is no universal pass/fail or verified hardware ranking for this workload. Compare your own repeated runs with the same shader, browser, camera, power state, and run duration. Browser animation callbacks can be capped by the display refresh rate; reaching that cap does not establish the GPU’s maximum throughput.

The most useful thing you can do is run the test three to five times and average the results. A single run can be distorted by a background update or a momentary thermal spike.

Common pitfalls

• Thermal throttling. A hot GPU slows itself down. Let it cool, then re-test.
• Power saving. Laptops on battery often cap GPU clocks. Run on AC power.
• Outdated drivers. Old WebGL drivers miss performance fixes. Update them.
• Browser choice does not matter. It does — browser graphics backends and settings can change results. Test the browsers you actually use.

Comparing two devices fairly

When you want to compare two machines, control the variables on both sides: the same browser, the same power state, the same room temperature, and the same default shader and camera. Record the average FPS and the frame-time stability for each device. Remember that a machine with a slightly lower average but steadier observed frame intervals often feels smoother in real use, so weigh consistency alongside raw throughput rather than chasing one big number.

Tips for repeatable results

For numbers you can compare week to week, keep conditions constant:

1. Benchmark at the same time of day on the same power profile.
2. Use the same browser each time.
3. Let the machine idle for two minutes before starting.
4. Record the average FPS across at least three runs.

Follow these steps and the Volume Shader BM Test becomes a reliable, repeatable yardstick for your hardware — whether you are validating a new build, checking an overclock, or just satisfying your curiosity about how fast your machine really is. Ready? Launch the benchmark and see where your GPU lands.