A WebGL test checks whether your browser can draw 3D graphics with your graphics card. WebGL is the standard that lets websites, browser games, maps and 3D viewers use the GPU; WebGL 2 is its newer version, and WebGPU is the next-generation interface that recent browsers add on top. This page tests all three in one click, shows the renderer the browser reports (which tells you whether hardware acceleration is on or you are stuck with slow software rendering), lists the limits and extensions developers ask about, and draws a known test image on your GPU and reads the pixels back, so you know rendering really works rather than just being switched on. If something is missing, the steps below show how to enable WebGL and hardware acceleration in Chrome, Edge, Firefox, Safari and Opera.
What does the WebGL test check?
- WebGL 1 and WebGL 2. The page asks the browser for each kind of drawing context. If it gets one, that version works.
- WebGPU. It asks for a WebGPU adapter and shows what the browser says about it, plus its limits and optional features.
- Hardware acceleration. It reads the renderer name. A name such as SwiftShader, llvmpipe or Microsoft Basic Render Driver means the browser is drawing with the processor instead of the graphics card.
- Render check. It draws a gradient where red rises from left to right and green from bottom to top, then reads four pixels back. Each must match the expected colour to within about 2%.
Worked example: reading a renderer string
A typical Windows result reads "ANGLE (Intel, Intel(R) Iris(R) Xe Graphics (0x000046A6) Direct3D11 vs_5_0 ps_5_0, D3D11)". ANGLE is the translation layer the browser uses; Intel is the vendor; Iris Xe Graphics is the chip; 0x000046A6 is its device ID; and Direct3D11 is the graphics API underneath. So WebGL is hardware accelerated on the Intel graphics. On a Mac you would see "ANGLE (Apple, ANGLE Metal Renderer: Apple M2...)", and in Firefox or Safari often a shorter, generic name, which is a privacy feature rather than a fault.
How to test WebGL: step by step
Step 1: Press Run WebGL test
The page creates WebGL 1 and WebGL 2 contexts, asks for a WebGPU adapter, and reads the renderer the browser reports. It takes under a second.
Step 2: Read the checks
Each line says OK, Check or Problem: WebGL 1, WebGL 2, WebGPU, hardware acceleration and the render check.
Step 3: Look at the render check image
A square with a smooth gradient from dark to red, green and yellow means the GPU drew it and the colours came back right.
Step 4: Fix what is missing
If hardware acceleration is off or WebGL is missing, follow the steps for your browser below, restart it and run the test again.
WebGL 1 vs WebGL 2 vs WebGPU
| WebGL 1 | WebGL 2 | WebGPU | |
|---|---|---|---|
| Based on | OpenGL ES 2.0 | OpenGL ES 3.0 | Modern APIs (Direct3D 12, Metal, Vulkan) |
| Released in browsers | 2011 | 2017 | 2023 (Chrome), later Safari and others |
| Adds | Basic 3D drawing | 3D textures, instancing, multiple render targets, integer textures | Compute shaders, lower overhead, explicit control |
| Used by | Older sites, simple viewers | Most current web games and 3D sites | New engines, AI in the browser, heavy rendering |
Our GPU benchmark, GPU stress test and volume shader test use WebGPU where it is available and WebGL 2 otherwise, so this test tells you which one they will run on.
How to enable WebGL and hardware acceleration
WebGL is on by default in every current browser. When it fails, hardware acceleration is usually off, or the browser has blocked the graphics driver.
Chrome
Settings, System, turn on "Use graphics acceleration when available", then Relaunch. To see why WebGL is off, open chrome://gpu: it lists each feature as hardware accelerated, software only, or disabled, with the reason.
Microsoft Edge
Settings, System and performance, turn on "Use graphics acceleration when available", then Restart. The details page is edge://gpu.
Firefox
Settings, General, Performance: untick "Use recommended performance settings", then tick "Use hardware acceleration when available" and restart. about:support shows the Graphics section with WebGL status. In about:config, webgl.disabled must be false.
Safari (Mac, iPhone and iPad)
WebGL is always on in current Safari and cannot be switched off in the normal settings. If it fails on a Mac, update macOS; on an iPhone or iPad, update iOS or iPadOS.
Opera
Settings, Advanced, Browser, System, turn on "Use graphics acceleration when available", then relaunch. Opera is based on Chromium, so opera://gpu shows the details.
WebGL not working? Common fixes
- Update the graphics driver from NVIDIA, AMD or Intel. Browsers block WebGL on drivers known to crash. Our graphics driver finder points you to the right download.
- Restart the browser after changing settings or drivers; a crash can also make the browser turn WebGL off until it restarts.
- Remote desktop and virtual machines often have no real GPU, so the browser falls back to software rendering.
- Laptops with two GPUs: in Windows, Settings, System, Display, Graphics, set your browser to High performance so it uses the dedicated card.
- Extensions and privacy settings can block WebGL or hide the renderer. Try a private window with extensions off.
- Try another browser. If WebGL works in one browser but not another, the problem is the browser's settings, not the GPU.
WebGL limits explained
Developers check these when a 3D site fails on some devices. Open Limits and extensions after the test for your values.
- MAX_TEXTURE_SIZE: the largest image the GPU accepts, in pixels per side. Desktop GPUs usually report 16,384; some phones less.
- MAX_RENDERBUFFER_SIZE and MAX_VIEWPORT_DIMS: the largest area that can be drawn into at once.
- MAX_TEXTURE_IMAGE_UNITS: how many textures a shader can read at the same time.
- MAX_SAMPLES (WebGL 2): the highest anti-aliasing level for multisampled drawing.
- Extensions: optional features such as floating point render targets or compressed texture formats. A site that needs an extension your browser lacks will fail or fall back.
- WebGPU limits such as maxTextureDimension2D and maxComputeWorkgroupSizeX, and features such as shader-f16, matter for WebGPU apps and AI models in the browser.
Does WebGL tell sites which graphics card I have?
Often, yes: Chrome and Edge report the model, which is how our what GPU do I have page and Can my PC run it can suggest your card. Firefox and Safari usually give a generic name to make tracking harder. This page reads it only inside your browser and does not send it anywhere.
Why we built this WebGL test
Most people reach a WebGL test because something failed: a browser game, a map or a 3D viewer says "WebGL is not supported", or a site feels slow. What they need to know is short. Does WebGL work, does the browser use the graphics card, and if not, what do I change? Nitin Raja, who builds this site, tried a lot of WebGL report pages before building this one: many print every parameter as a raw value, check WebGPU on a separate page, and stop there, leaving you to work out whether anything is wrong and how to fix it.
So this test answers in one sentence first, flags software rendering, actually draws a test image on the GPU and checks the pixels, and keeps the fixes for each browser on the same page. The raw values are still there, under Limits and extensions, for developers who need them.
What this WebGL test measures
The checks are described above in what the WebGL test checks. These are the browser APIs behind them:
- Support.
canvas.getContext('webgl')andgetContext('webgl2'), andnavigator.gpu.requestAdapter()for WebGPU. - Renderer and vendor.
UNMASKED_RENDERER_WEBGLandUNMASKED_VENDOR_WEBGLfrom the WEBGL_debug_renderer_info extension, or the plain RENDERER and VENDOR values when the browser hides them. For WebGPU, the adapter info: vendor, architecture and description. - WebGL limits. VERSION, SHADING_LANGUAGE_VERSION, MAX_TEXTURE_SIZE, MAX_RENDERBUFFER_SIZE, MAX_VIEWPORT_DIMS, MAX_TEXTURE_IMAGE_UNITS, MAX_VERTEX_ATTRIBS and MAX_FRAGMENT_UNIFORM_VECTORS; with WebGL 2 also MAX_SAMPLES, MAX_3D_TEXTURE_SIZE and MAX_DRAW_BUFFERS; and the full list from
getSupportedExtensions(). - WebGPU limits. maxTextureDimension2D, maxBufferSize, maxStorageBufferBindingSize, maxComputeWorkgroupSizeX, maxComputeInvocationsPerWorkgroup and maxBindGroups, plus the adapter's optional features.
- Render check. A 256 x 256 gradient drawn with WebGL 2, then four pixels read back with
readPixels. Each colour channel must be within 6 steps (on the 0 to 255 scale) of the expected value.
What it does not measure: speed or frame rate, graphics memory, the driver version, or whether one particular site will run. For speed, use the GPU test or the GPU benchmark.
How accurate is this WebGL test?
Support checks are exact: the browser either creates a context or it does not. Two things to keep in mind. The renderer name is whatever the browser chooses to report, so a generic name does not mean acceleration is off; the render check confirms drawing works either way. And a pass means the basics work; a specific site can still fail on a missing extension or a driver bug. For performance rather than support, run the GPU test or the GPU benchmark.
Why this WebGL test is different
Each point below can be checked on this page or in your browser's developer tools.
- Nothing runs before you press the button, and nothing is sent anywhere: the renderer name and limits stay in your browser.
- A hidden GPU name is not called a fault. When Firefox or Safari report a generic renderer, the test marks hardware acceleration as "probably on" with a Check badge, and the render check settles it.
- Copyable result. Copy result gives every check with its OK, Check or Problem badge as plain text, ready for a support forum or a bug report.
- Same engine as our GPU tests. The render check uses the rendering code of our GPU benchmark and volume shader test.
- Cleans up after itself. The test contexts are released with WEBGL_lose_context when it finishes.
- 15 languages. The same test and the same fixes in English and 14 other languages.
This WebGL test vs other WebGL report pages
| This test | Typical WebGL report page | |
|---|---|---|
| WebGL 1, WebGL 2 | Yes | Yes |
| WebGPU | Yes, with limits and features | Often a separate page |
| Hardware acceleration verdict | Plain sentence, software rendering flagged | Raw values to interpret yourself |
| Render check | Draws and reads back a test image | Some show a spinning cube, few verify pixels |
| How to fix | Steps for five browsers on the same page | Rare |
| Limits and extensions | Key ones, plus the full extension list | Usually every parameter |
Sources
- Khronos Group, WebGL 1.0 and WebGL 2.0 specifications, and the WebGL extension registry.
- W3C, WebGPU specification.
- MDN, WebGL API, WEBGL_debug_renderer_info and WebGPU API.
- ANGLE project (the WebGL to Direct3D, Metal and Vulkan translation layer).
WebGL test FAQ
How do I check if WebGL is enabled?
Press Run WebGL test on this page. It tells you whether WebGL 1, WebGL 2 and WebGPU work, and whether the browser uses your graphics card or software rendering. In Chrome and Edge you can also open chrome://gpu or edge://gpu and look at the WebGL lines.
How do I enable WebGL in Chrome?
Open Settings, System, and turn on "Use graphics acceleration when available", then relaunch Chrome. WebGL itself is on by default. If it still fails, update the graphics driver; Chrome blocks WebGL on some old or faulty drivers.
What is the difference between WebGL and WebGL 2?
WebGL 1 is based on OpenGL ES 2.0 and works almost everywhere. WebGL 2 is based on OpenGL ES 3.0 and adds features such as 3D textures, multiple render targets and instanced drawing, which many newer web games and 3D sites need. Every current major browser supports both.
What is WebGPU?
WebGPU is the newer graphics and compute interface for the web, designed after Direct3D 12, Metal and Vulkan. It is faster for heavy work and supports general GPU computing. Recent Chrome and Edge have it on Windows, macOS and ChromeOS, and recent Safari has it too.
Why does my browser say WebGL is not supported?
Usually hardware acceleration is off, the graphics driver is old or blocked by the browser, or the browser runs in a remote desktop or virtual machine without a GPU. Turn on acceleration, update the driver, restart the browser, and try another browser to narrow it down.
Why does the renderer say ANGLE?
ANGLE is a translation layer that Chrome, Edge and Firefox use on Windows: WebGL calls are turned into Direct3D 11 calls for the graphics driver. "ANGLE (NVIDIA, NVIDIA GeForce RTX 3060 Direct3D11...)" still means your RTX 3060 is drawing.
Is WebGL safe?
Yes. WebGL runs in the browser's sandbox and cannot read your files. The one privacy concern is fingerprinting: the renderer name and limits help sites tell devices apart, which is why Firefox and Safari often report a generic name. This test reads them only in your browser and sends nothing anywhere.
Related tools
GPU testA quick health check: renders correctly, runs smoothly, no artifacts
GPU benchmarkFour short scenes, one score, average and 1% low frame rates
Volume shader testA raymarched 3D fractal cloud with a live frame rate
GPU stress testLoad your graphics card for up to 10 minutes and watch for throttling
What is my screen resolutionScreen resolution, browser window size and pixel ratio
Can my PC run itCheck popular games against your graphics card, CPU and RAM, no download