WebGL test
This WebGL test checks whether your browser can draw graphics with WebGL 2 and WebGL 1.
Checking WebGL…
Drawing a triangle with each WebGL version…
Enable WebGL in your browser
Choose your browser below. Paste settings addresses into the address bar; ordinary web links cannot open those settings.
Chrome
- On desktop, paste chrome://settings/system into the address bar. Turn on Use graphics acceleration when available, then choose Relaunch. Return here and press Retest.
- Open chrome://gpu and read Graphics Feature Status and Problems Detected. A software-only or disabled entry helps distinguish a graphics setting or driver problem from a game that simply cannot load its files.
- Update Chrome through Help → About Google Chrome. On Windows, check Windows Update or your computer maker for graphics drivers; on macOS, install available system updates. Restart after an update, then retest.
- If you changed experimental graphics options, restore those specific changes to Default in chrome://flags, then relaunch. Avoid forcing Ignore GPU blocklist as a routine fix. A work or school policy may require your administrator to change the acceleration setting. On a phone, update the browser and operating system instead of looking for the desktop System toggle.
Edge
- On desktop, open edge://settings/system. Search settings for graphics acceleration if the page layout differs. Enable Use graphics acceleration when available and restart Edge before retesting.
- Open edge://gpu to inspect Graphics Feature Status. Check edge://settings/help for a browser update, then update the graphics driver through Windows Update or your device maker. On a Mac, use Software Update.
- Return any experimental graphics flags you changed in edge://flags to Default, then restart. A managed device may lock the acceleration setting: Microsoft documents that a disabled acceleration policy prevents Edge from using it. Ask the device administrator when the setting is locked.
Safari
- Update Safari by installing the available macOS, iOS or iPadOS update. Quit and reopen Safari on a Mac; close and reopen the browser on an iPhone or iPad. Return to this page and retest.
- Safari has no Chrome-style graphics acceleration toggle. If you changed WebGL options in Develop → Feature Flags on a Mac, restore those changes to their defaults. Apple's guide explains how to open Feature Flags; leave unrelated experimental features alone.
- On a Mac, graphics driver updates arrive with system updates. If the test still fails, restart the device and compare with another updated browser. A privacy setting can hide the GPU name while both drawing checks still pass, so use the PASS or FAIL rows to judge rendering.
Firefox
- On desktop, open Settings → General → Performance. Clear Use recommended performance settings to reveal Use hardware acceleration when available. Enable acceleration, quit Firefox completely and open it again before retesting.
- Open about:support and read the Graphics section for WebGL renderer details and failure notes. Update Firefox and your operating system or graphics driver, restart, then retest. Mozilla's driver guide covers Windows and Linux update routes.
- If you previously changed WebGL preferences in about:config, reset those changes to their defaults. In particular, webgl.disabled set to true disables WebGL. Advanced preferences affect browser behavior; do not force webgl.force-enabled just to get a green result. On a managed device, a locked preference needs the administrator.
What the results mean
Each check opens its own 8 × 8 canvas, compiles vertex and fragment shaders, draws a green triangle and reads its centre pixel. The expected red, green and blue values are 64, 204 and 128, with a tolerance of three levels for each channel. A context opening alone does not produce a pass. A shader error, wrong pixel, graphics error or lost context produces a failure.
The two checks run independently. If WebGL 2 fails and WebGL 1 passes, you can still use applications built for the older version. If both fail, start with the instructions for your browser above. Close other graphics-heavy tabs before retesting: an exhausted graphics context is a different problem from an unsupported device.
Vendor and Renderer are the strings the graphics API reports. GPU / driver uses the optional debug extension, when available. ANGLE may appear because the browser translates graphics calls for the operating system. A generic name, missing debug details or an unrecognized renderer does not establish whether your physical graphics card is in use. MDN explains the renderer extension and privacy restrictions.
The test reads these values locally and does not upload or save them. The mountain scene is drawn in your tab after a pass. It demonstrates simple geometry; its appearance is separate from a game's frame rate. Site analytics counts visits separately; this test does not send GPU strings or pixel results to it.
Compare WebGL games by graphics requirements and controls.
WebGL test questions
How do I test WebGL?
Open this page with JavaScript enabled. It automatically draws a triangle separately with WebGL 2 and WebGL 1, reads a pixel back and shows PASS or FAIL for each version. Press Retest after changing a browser setting.
How do I enable WebGL in Chrome?
On desktop Chrome, open Settings, then System, and turn on Use graphics acceleration when available. Relaunch Chrome and retest. If it still fails, inspect chrome://gpu, update Chrome and the graphics driver, and restore any experimental graphics flags you changed.
Why does WebGL 1 pass while WebGL 2 fails?
The browser drew through the older graphics API. Check your browser’s acceleration settings and graphics driver, then retest.
Why does the test show SwiftShader or llvmpipe?
Those renderer names identify software graphics implementations. A software renderer can draw successfully while a demanding game runs slowly. Check graphics acceleration and the driver, then restart the browser and retest.
Why is my GPU name hidden?
Browsers can restrict the debug extension that exposes GPU and driver strings. A hidden name is separate from a failed draw. Read the WebGL result rows even when GPU details say Not exposed.
Does a WebGL pass mean every game will work?
A pass confirms a small shader draw and pixel readback in this tab. A game can need additional features or fail because of its network requests, memory use or embedding rules. Try its direct maker link when graphics pass but the game does not load here.