Browser Test
See your browser name, version and user agent, and which web features your browser supports.
WebGL Test
If the WebGL row below reads Supported, WebGL is enabled in this browser. The page also shows the graphics renderer the browser reports and draws a rotating cube so you can see it rendering.
Support
- WebGLChecking
- WebGL 2Checking
Renderer
- Vendor
- Checking
- Renderer
- Checking
- Software rendering
- CheckingJudged from the renderer name only.
- Shading language version
- Checking
- Max texture size
- Checking
- Max viewport
- Checking
- Antialiasing
- Checking
—fps
Averaged over the last second. Limited by your display refresh rate; not a benchmark.
Checking WebGL support
Runs entirely in your browser. Test results, audio and video never leave your device.
How to check if WebGL is enabled
- Read the Support list. WebGL and WebGL 2 each read Supported, with the version string the browser reports, or Not supported.
- Read Vendor and Renderer in the Renderer list. They usually name your graphics card; a note marks a generic value the browser shows instead.
- Check Software rendering. Likely means the renderer name is one that draws on the processor, such as SwiftShader or llvmpipe.
- Watch the rotating cube and the fps readout. Press Pause to stop the cube and Play to start it again.
- If WebGL reads Not supported, work through the steps below, then reload the page.
What is WebGL?
WebGL is the browser feature that lets web pages draw 2D and 3D graphics in a canvas element, usually on your graphics card and without a plugin. WebGL 1 is based on OpenGL ES 2.0 and WebGL 2 on OpenGL ES 3.0, and current versions of Chrome, Edge, Firefox and Safari support both. Maps, 3D viewers, design apps and browser games use it.
How to enable WebGL
WebGL is on by default in current browsers, so when it fails, a setting, the graphics driver or an extension is usually blocking it. Work through these steps and reload this page after each change.
- See why: open the browser's graphics report, chrome://gpu in Chrome, edge://gpu in Edge or about:support in Firefox. It shows the WebGL status and any problems the browser detected.
- Turn on the graphics or hardware acceleration setting, under Settings > System in Chrome or Settings > System and performance in Edge. Restart the browser afterwards.
- Update the graphics driver from the maker of your graphics card or computer. Browsers turn WebGL off for drivers with known problems.
- In Firefox, open about:config and make sure webgl.disabled is set to false.
- Turn off extensions that block WebGL or fingerprinting, or test in a private window, where extensions are usually off.
- On a remote desktop or in a virtual machine, try the computer itself: these sessions often have no graphics acceleration.
Which graphics card is my browser using?
The Renderer row names the graphics hardware the browser draws with, when the browser reveals it. Software rendering is judged from that name alone: Likely for a known software renderer, Unlikely for any other real name, and Cannot tell for a generic one.
| Renderer shows | What it means |
|---|---|
| An NVIDIA, AMD, Intel, Apple or Qualcomm chip, often inside ANGLE (…) | WebGL runs on that graphics hardware. ANGLE is the layer many browsers use to translate WebGL for the system's graphics API. |
| SwiftShader, llvmpipe or Microsoft Basic Render Driver | Software rendering: the processor draws instead of the graphics card, usually because acceleration is off or the driver is missing or blocked. |
| Apple GPU, Mozilla, WebKit or another generic name, marked by the page | The browser hides the real hardware for privacy. Your system settings show the graphics card. |
| Your laptop's integrated graphics, when it also has a dedicated graphics card | The browser is using the power-saving chip. Windows graphics settings let you set the browser to use the faster one. |
What this test can detect
- Whether WebGL and WebGL 2 contexts can be created, with the version string each one reports.
- The vendor and renderer the browser reports, which usually name your graphics card, with generic values marked.
- Likely software rendering, when the renderer name is SwiftShader, llvmpipe or another renderer that draws on the processor.
- The shading language version, maximum texture size, maximum viewport and whether antialiasing is on.
- Live rendering: a rotating cube with a frame rate averaged over the last second.
How it works
The page asks for WebGL 2 and WebGL 1 contexts on canvases that are never shown, reads their version strings and releases them. Vendor and renderer come from the WEBGL_debug_renderer_info extension where the browser offers it.
The cube is 36 vertices in six flat colors, drawn with WebGL 1 and turning about 29° and 52° per second around two axes. The fps readout averages the frames drawn in the last second and updates every 500 ms. It stops while the tab is hidden, starts paused when your system asks for reduced motion, and resumes after the browser restores a lost context.
Limitations
- This is not a benchmark. A cube this simple usually runs at your display's refresh rate even with software rendering, so a normal fps readout does not prove the graphics card is in use.
- The fps readout cannot exceed the display's refresh rate, and browsers can slow animation to save power.
- Software rendering is judged from the renderer name alone, so a software renderer the page does not recognize reads Unlikely.
- Safari, Firefox and privacy settings can report a generic or simplified renderer instead of the real graphics card.
- The page does not list WebGL extensions or deeper limits. The Browser Test checks other web features your browser supports.
Frequently asked questions
What GPU do I have?
The Renderer row usually names the graphics card your browser uses, when the browser reveals it. For the exact model, open Task Manager > Performance > GPU on Windows, which also shows the driver version, or Apple menu > About This Mac on a Mac.
Is WebGL safe to leave on?
Yes, for everyday browsing: every major browser turns it on by default and checks WebGL commands before they reach the graphics driver. It does let sites read your graphics renderer, one of the signals trackers use for fingerprinting, which is why some browsers report a generic name.
Why does the fps readout show 60?
The cube is drawn once per screen refresh, so the readout follows your display's refresh rate: about 60 on a 60 Hz screen and about 144 on a 144 Hz screen. To check the refresh rate itself, use the Refresh Rate Test.
Why does WebGL work but WebGL 2 does not?
The graphics hardware or driver cannot provide what WebGL 2 needs, the browser has blocked WebGL 2 for that driver, or the browser is too old: Safari added WebGL 2 in version 15. Updating the browser and the graphics driver is the first thing to try.
Can this page test WebGPU?
No. It checks WebGL 1 and WebGL 2 only. WebGPU is a newer, separate graphics API with its own browser support, so a working WebGL does not mean WebGPU is available.