What Is Volume Shader BM? Meaning & FPS Explained
Volume Shader BM is a browser GPU test. Learn what its FPS measures, how the original and current engines differ, and try it here.
No install. Live FPS and stability. Starts only when you tap.
Volume Shader BM is a browser GPU benchmark. Here, BM means benchmark: it draws a scene using a fragment shader and reports how quickly your browser renders it. You can run the current test above without installing an app or creating an account.
Original Volume Shader BM or the current test?
The original demo comes from cznull’s Volume Shader BM source. This site maintains its own interface, timed measurements and local result history.
- WebGL 2.0 · Current is the default and uses this site’s scene field.
- WebGL 1.0 · Original preserves the original fractal-field algorithm. Use the original-algorithm button on the homepage to run it.
These engines draw different workloads. The same device can produce different FPS in each. The original algorithm also does not make a timed result identical to a screenshot from another site. Check the engine, mode and rendering dimensions before comparing. Public historical device rows are legacy WebGL 1.0 results; controlled current-engine reference results are still pending.
Run a test and understand the result
- Choose 45-second Medium above, or 30-second Light for a lower load.
- Keep this tab visible. Switching to the background stops the test.
- Read average FPS and stability after completion. Repeat under the same conditions to compare with an earlier matching run in local history.
FPS is frames per second. A higher number means more frames were rendered in this particular workload. It is not a gaming FPS prediction or a ranking of overall GPU performance. Near 60 FPS can reflect a 60 Hz refresh limit, so it does not prove that two GPUs have the same capacity. Read the FPS guide.
Why can the result be low or change between runs?
Resolution, engine, browser version, hardware acceleration, power settings, heat and background applications can all affect the result. Low FPS alone does not identify a faulty GPU or prove thermal throttling. Try Light, close demanding tabs and repeat with the same settings. If rendering fails, use the WebGL diagnostic guide.
For phone comparisons, keep browser orientation, charging state and power mode consistent. Allow the device to cool between runs. See the phone test guide and measurement method.
What stays on my device?
Rendering and measurement happen in your browser. The latest 10 completed results are saved locally and can be cleared or exported. With optional analytics enabled, test events and summary metrics such as FPS can be sent to Google Analytics. The GPU renderer and full browser version in the result stay local unless you share or export them. See the privacy policy.
