GPU Test

This page reads your graphics card's vendor and renderer strings directly through the WebGL API, no download required. Click into the Graphics adapter panel above and it will show the identified chip along with WebGL and GLSL versions.

Those names mean your browser fell back to a software renderer instead of your real hardware. This usually happens when hardware acceleration is disabled in browser settings, a GPU driver crashed, or you're inside a virtual machine or remote desktop session without GPU passthrough.

No, and it isn't trying to be. Browser-based WebGL tests are throttled by the browser's compositor, driver overhead, and power-saving settings, so scores will be lower than a native DirectX or Vulkan benchmark. Use this test to compare relative performance across your own devices or browsers, not to compare against native benchmark databases.

It's a browser extension that unmasks the real GPU vendor and model, since WebGL normally reports a generic string for privacy reasons. Firefox with resistFingerprinting enabled, and some privacy-focused browsers, block this extension entirely, so you'll see generic labels instead of your actual hardware name.

Common causes include the browser tab running on battery-saver mode, another heavy tab or app competing for the GPU, an external monitor forcing a lower refresh path, or browser hardware acceleration being turned off. Try closing other GPU-heavy tabs and re-running the test.

The score is derived from the average frames per second sustained during the five-second stress render, scaled so that typical integrated graphics land in the low hundreds and dedicated GPUs land much higher. It's a relative number for comparing runs, not an industry-standard unit.

Yes, mobile Safari, Chrome for Android, and most mobile browsers support WebGL and will run the stress test, though mobile GPUs typically throttle after a few seconds of sustained load to manage heat, which is reflected honestly in the sparkline.

Browsers only enable a subset of possible WebGL extensions depending on the platform, driver, and security policy. A lower extension count doesn't necessarily mean weaker hardware, it can also reflect a more conservative browser configuration or an outdated GPU driver.

No. The stress render only runs for five seconds and uses a lightweight fractal shader, which is far short of what would cause thermal issues. If you want a longer sustained load test, run it multiple times and watch whether the frame rate drops between runs, which can indicate thermal throttling.

Open your browser's settings and search for 'hardware acceleration', then make sure it's turned on and restart the browser. If it's already on, update your GPU driver from your manufacturer's website (NVIDIA, AMD, or Intel), since an outdated or corrupted driver is the most common cause of WebGL being disabled automatically.

Yes, if your operating system is routing the browser's rendering through the eGPU. Check your OS graphics settings (Windows Graphics settings, or macOS System Settings) to confirm which GPU is assigned to your browser process, since some systems default back to the integrated GPU for windowed applications.