ApexMark › GPU stress test
GPU stress test online
Put your graphics processor to work in the Oméga 3D scene. Watch live FPS, move the camera and adjust the load, from 360p up to native 8K on supported devices. Use it for a quick demonstration or keep the scene running for a longer GPU stress test.
Open GPU tortureWatch a real WebGPU scene run
The GPU live test renders the ApexMark Oméga scene continuously. Its FPS measurement waits for submitted GPU work to finish and counts completed workload frames.
This requires WebGPU support in your browser and device. Availability can differ between browsers on the same machine.
Start a quick preview or a sustained GPU test
Open Live test in the menu and choose GPU torture. Rendering starts automatically after preparation while the page is visible. If your browser requests reduced motion or the page is hidden when opened, choose Start once it is visible.
Resolution changes the image’s pixel count. Complexity selects increasingly demanding versions of the existing scene workload.
Start with a short demonstration to see the scene and controls. For sustained observation, keep the page visible and the conditions steady.
Explore from 360p to native 8K
The resolution range starts at 640 × 360 and includes 4K and native 7680 × 4320. The 8K option is explicit and subject to device limits and successful allocation.
Higher settings can require considerably more resources. Increase the load deliberately, then inspect the resulting history.
- Select a supported resolution and wait for preparation to finish.
- Change complexity while keeping resolution and camera view fixed.
- Use fullscreen to inspect the scene, and Stop to end rendering.
Understand what the FPS reading measures
Frames are measured from one completion to the next, including browser scheduling and delivery. The large FPS reading averages frame times over the latest second.
The green trace shows FPS over the last 30 seconds. The amber 1% low trace needs 100 complete frames, then uses up to the latest 1,000 frame durations.
Compare changes without losing the recent trace
Adjusting resolution or complexity retains the recent graph and session duration. Orange markers identify applied changes and expose their time and before-and-after settings.
The new settings restart current FPS, average, minimum and the 1% low collection. Stop freezes the graph, and restarting begins a fresh session.
Keep graphics observations in context
This live workload is useful for demonstrating WebGPU and exploring how render settings affect observed throughput. The separate GPU benchmark is the route for fixed, verified scored measurements.
The test runs in your browser without an account, saving or submitting a live score. It does not diagnose a damaged GPU, certify thermal stability or predict commercial-game performance. A lower reading is an observation to investigate, not a hardware verdict.
Frequently asked questions
Do I need WebGPU for this GPU stress test?
Yes. The live scene requires WebGPU support from the browser and device. If it is unavailable, use a supported browser or device. The tool does not replace the scene with a fake GPU measurement.
Can I run a real 8K rendering workload?
The tool offers a native 7680 × 4320 target. It runs only when device limits and allocation allow it. Preparation errors stop that setting; the tool does not silently render at a lower resolution.
Why can FPS exceed my monitor’s refresh rate?
The test measures completed workload frames without refresh-rate pacing. A monitor displays at its own refresh rate. Workload throughput and the number of images physically shown on screen are different measurements.
What changes when I raise complexity?
The scene uses a more demanding existing workload. Resolution remains a separate control. Compare at the same camera view and power conditions to make the observed difference easier to interpret.
What happens to the graph when I change settings?
Recent history and duration stay visible, and an orange marker records the applied change. Current statistics and the rolling 1% low restart. Renderer preparation is left as an unmeasured gap.
Does a long run prove that my graphics card is stable?
No. It demonstrates sustained operation of this particular browser workload. It does not certify hardware health or thermal stability, predict gaming FPS or produce a saved public benchmark score.