Live FPS
The counter is frames of this WebGL scene, in this browser, at this complexity.
Browser GPU Test
Volume Shader. Live GPU Test with FPS.
Run Volume Shader BM in the browser. A WebGL shader ray marches a Mandelbulb and prints live FPS on your phone or PC. Nothing to install. You can also run a 3D rendering test, a shader test, or a VRAM test.
Four tests
Volume Shader plus 3D, shader, and VRAM loads. Each one stresses a different part of the GPU.
Phone or PC
Same pages on both. Heat, battery saver, and extra tabs still change the number.
- 60+
- Comfortable at this level
- 30
- Usable, some hitch
- 15
- The GPU is strained
- WebGL
- Runs in the tab
What the number actually tells you
FPS here is frames of this scene, in this browser, at this complexity. It is a graphics reading, not a full hardware lab. For the longer read, see what FPS means.
Frames per second
Each frame is one finished Volume Shader image. Higher and steadier FPS means the GPU keeps up. A number that jumps around is lag, even if the average looks fine. Compare two devices only after you match the method in the GPU benchmark notes.
Complexity
Simple, Standard, Advanced, and Extreme change how many ray steps and Mandelbulb iterations the shader runs. Standard is the usual comparison. Extreme is a stress load. Open Run Volume Shader and pick the level under the canvas.
Heat and power
A warm phone throttles. Battery saver caps clocks. Extra tabs steal GPU time. Cool the device, turn power saving off, and close leftover apps before you compare two scores. Prep steps are in how to test a GPU.
What it does not measure
Volume Shader does not score CPU, disk, battery health, or VRAM size. It does not prove a phone is fake. Use the 3D test for raster draw, the shader test for fragment work, and the VRAM test for texture pressure.
Four GPU tests
Volume Shader is the main scene on this site. The other three tests answer narrower GPU questions: raster 3D, fragment shading, and texture sampling.
Main test
Volume Shader
A Mandelbulb volume, ray marched in WebGL 1.0, with live FPS on the canvas. Open it when you want the classic clip or a visual GPU check.
Start the volume test3D rendering test
A grid of tetrahedra, lighting, and a timer. Closest to a general GPU test or graphics card check.
Shader test
Fullscreen procedural noise. Raise iterations to lean on fragment shading, not the volume kernel.
VRAM texture test
Grows a texture atlas and samples it every frame. Reports estimated atlas bytes, not the card's true VRAM.
Phone and computer, same pages
You open the same URLs on mobile and desktop. The GPU, the thermal budget, and the browser still change the result.
On a phone
Volume Shader runs in Chrome or Safari on a phone. Start on Standard. Give the chassis air. If FPS falls after half a minute, the SoC is throttling. That is a useful stress signal, not a crash. For a longer phone load, read GPU stress test on a phone.
Optional native apps are on Google Play and the App Store. This website is the browser test. You do not need an APK to run it.
- Start on Standard, not Extreme
- Turn off battery saver
- Stop if the OS shows a heat warning
On a computer
A discrete GPU should look easy at Standard. Move to Advanced or Extreme if the scene feels light. For a timed score, use the 3D rendering test. Furmark and 3DMark still go deeper on drivers and coolers. We split that in browser vs Furmark and 3DMark.
Note whether the laptop is plugged in. Battery mode often cuts GPU clocks.
- Same browser family when you compare two PCs
- Close extra tabs and overlays
- Use the 3D test when you want a clocked run
Where to start
Start a canvas if you want a live number. Read a guide if you want the method. The name, ray marching, and FPS bands have their own pages.
Live tests
Guides
Run the GPU test.
Volume Shader is the visual test this site is built around. For raster, shader, or texture pressure, start the 3D test, shader test, or VRAM test.
Native apps are on Google Play and the App Store. This website is the browser test. You do not need an install.
Run Volume Shader