Online GPU Benchmark
volumeshader_bm Test for GPU Performance
Run the fixed volumeshader_bm workflow in your browser, select a preset and rendering API, then measure FPS, frame time, GPU label, browser context, and backend behavior before exporting or submitting an eligible result.
What is volumeshader_bm?
volumeshader_bm is a browser-based GPU benchmark that renders a shader-heavy volumetric scene and measures FPS, frame time, and stability. It is also known as VolumeShader BM, Volume Shader BM, VSBM, or the cznull volume shader benchmark.
Volumeshader_BM Result & Runtime Environment
Rendering Controls and GPU Stats
Benchmark Preset
Entry preset with a slightly lighter load than the previous Low run.
FPS History Chart
FPS History Chart
Waiting for samplesCompare accepted VolumeShader_BM results
After a stable volumeshader_bm run is submitted and accepted, compare it only against the same device class, preset, and rendering API in the public leaderboard.
Compare VolumeShader_BM FPS scoresShare This Benchmark Session
Share this result with another reviewer or teammate.
Need to refine the scene before the next benchmark pass?
If this volumeshader_bm session shows that the scene, shader, or load settings still need work, go back to the volume shader lab first. The home page is the better place to tune kernel code, framing, and palette before you lock another benchmark run.
Open the volume shader lab for editingHow to Use This Benchmark
- Choose a built-in volumeshader_bm preset if you want the volumeshader_bm run to qualify for the leaderboard.
- Keep the session active for at least sixty seconds so the rolling metrics have time to settle.
- Record the browser and device context with each volumeshader_bm run so later comparisons have useful evidence.
- Export the result or copy the share link before you change parameters.
- Submit the record only after the history shape looks stable enough for comparison.
Fair Testing Notes
Close GPU-heavy apps, keep the machine on stable power, and compare only matching preset and API combinations. A volumeshader_bm result becomes far more useful when the surrounding conditions are controlled, especially when you repeat a volumeshader_bm run after changing drivers or browsers.
How to read this benchmark result
A volumeshader_bm result is strongest when you read average FPS together with frame time, history shape, browser, backend, and GPU label. A short spike can look impressive, but a flatter trace across a longer run is usually more useful for fair comparison. The best reading is the one that shows whether the workload stayed coherent after warm-up, user interaction, and ongoing browser scheduling.
When you compare volumeshader_bm runs, keep the preset, API, and device category matched. That keeps one result aligned with the next and avoids mixing unlike workloads. Public descriptions of volumeshader_bm commonly frame it as a browser-based GPU stress test for complex volume and shader workloads, which is exactly why disciplined grouping matters: the result only becomes meaningful when similar runs can be inspected side by side.
That is also why this page separates creative editing from benchmarking. The home lab is where you shape the scene. This page is where you lock the workload, watch the runtime environment, and decide whether a volumeshader_bm record is clean enough to publish. If you need a result that other people can audit, this process has to stay stricter than a casual demo.
Benchmark FAQ
What is the volumeshader_bm test?
The volumeshader_bm test is a browser-based GPU benchmark that renders a shader-heavy volumetric scene and measures FPS, frame time, and stability.
Is volumeshader_bm the same as VolumeShader BM or VSBM?
Yes. Users often search for the same benchmark using names such as volumeshader_bm, VolumeShader BM, Volume Shader BM, or VSBM.
What score should I compare?
Compare volumeshader_bm results only within the same device class, preset, and rendering API. A Desktop High WebGL result should not be compared directly with a Mobile Low WebGPU result.
Why are WebGL and WebGPU results separated?
WebGL and WebGPU use different browser graphics backends, so their results should be treated as separate benchmark buckets.
How do I submit a leaderboard result?
Run a stable volumeshader_bm test with the selected preset and API, review the collected metrics, and submit the eligible result through the benchmark page.
Last updated: March 19, 2026