Volumeshader_bm GPU Test
Volumeshader_bm GPU test: WebGL fractal stress test, right in your browser.
WebGL fractal stress test · rendered at a fixed 1920×1080 so scores stay comparable across devices.
Why this tester
Nothing to install
Pure WebGL — open the page and run the heavy volumeshader_bm fractal stress test. No downloads, no disk space, no software.
Live FPS monitor
A real-time frame-rate counter sits in the top corner of the test view, showing exactly how the GPU holds up under load.
Scale the load to the limit
Customize the fractal parameters to ramp the load from a light warm-up to a worst-case power draw.
How to start the test
- 01 · Start the test
Click "Start test" to open the parameter page. On a low-end GPU, do not raise the defaults carelessly.
- 02 · Adjust view & parameters
In the fullscreen view, drag with the left button to rotate, right button to pan, wheel to zoom; double-click for the quick settings panel.
- 03 · Watch the FPS, then exit
Keep an eye on the live FPS counter. When you are done, press "Exit test" to return to the page.
Parameter guide
The parameter page only accepts numeric edits. Defaults are the standard load; here is what each value does:
- Iterations: for(int i=0;i<5;i++)
- Fractal complexity and detail. Suggested i<3 (easy), i<5 (standard), i<8 (heavy), i<12 (extreme).
- Angle scale: *8.0
- Angle transform magnitude. Suggested *4.0 (mild), *8.0 (standard), *12.0 (intense), *16.0 (extreme).
- Power exponent: pow(b,8.0)
- Scaling strength and recursion depth. Suggested pow(b,4.0) light, pow(b,8.0) standard, pow(b,12.0) strong, pow(b,16.0) extreme.
- Break threshold: if(b>6.0)
- Boundary of the fractal. Suggested b>4.0 small, b>6.0 standard, b>8.0 large, b>10.0 extra large.
- Return value: return 4.0-
- Surface density and visibility. Suggested 2.0- dense, 4.0- standard, 6.0- sparse, 8.0- very sparse.
GPU terms explained
- WebGL
- The browser-native 3D graphics API. The toadstool test is a WebGL ray-marched fractal renderer — no plugins needed.
- FPS
- Frames per second. A weak GPU drops FPS sharply and the animation visibly stutters — the most direct number for comparisons.
- Fractal rendering
- Math-generated infinite detail computed in real time. The huge floating-point and ray-marching workload is a brutal GPU workout.
- Core temperature & power
- A stress test pushes the GPU to full load — power draw maxes out and temperatures climb, the perfect probe for cooling and PSU headroom.
Use cases
Second-hand GPU check
Run it for 15 minutes and watch for artifacts, driver crashes or black-screen reboots — classic mining-card symptoms.
Cooling limit test
Raise the load to reach thermal equilibrium quickly and judge your case airflow and cooler headroom.
Phone SoC comparisons
A favorite with reviewers to compare peak performance and thermal throttling across phones.
Overclock stability
After an OC tune, verify clocks and voltage quickly — faster than a full 3DMark loop.
Troubleshooting guide
Black screen / reboot mid-test
Usually an over-current protection trip (undersized PSU) or core overheating. Check PSU wattage and clean dust.
Snow, mosaic or colored stripes
Classic VRAM failure or a cracked BGA (artifacts) — common on ex-mining cards. Stop testing and contact support.
Render freezes, system alive
A driver crash: unstable clocks or a driver bug. Reset clocks and cleanly reinstall drivers with DDU.
FPS absurdly low
Check the monitor cable is plugged into the graphics card (not the motherboard iGPU), and that the browser uses the dGPU on laptops.
Frequently asked questions
Can the test damage my GPU?
Generally no. Modern cards throttle or shut down on over-temperature and respect power limits. Still, extreme parameters plus poor cooling can accelerate aging — use judgment.
Why do some call this the "toadstool" (毒蘑菇) test?
The original project is volumeshader_bm. The fractal looks mushroom-like and the load is "poisonous" for GPUs, so Chinese users gave it the informal nickname 毒蘑菇 (toadstool) — the official name is Volumeshader_bm GPU Test.
Can I run it on a phone?
Yes, if the browser supports WebGL — but it will heat the SoC heavily, and older phones may freeze or reboot.
The render is completely black — why?
Check that hardware acceleration is enabled in your browser settings; WebGL cannot render properly without it.
Can I lower the load via parameters?
Yes. In the parameter page, change the iteration count in for(int i=0;i<5;i++) from 5 to 2 or 3 for a much lighter load — or raise it for the extreme version.