If you see We couldn’t load the editor with a message about WebGL 2, your browser couldn’t initialize the graphics technology Jitter needs for editing in your browser.
This error can happen because of browser settings, a temporary graphics issue, or a device that doesn’t support WebGL 2.
Reload and restart your browser
Click Reload on the error page.
If the error comes back, save any work in other tabs, then fully quit and reopen your browser.
Open Jitter and try again with just one Jitter tab open. Close other tabs and apps you don’t need, especially those using video or graphics.
Your browser can temporarily lose access to graphics resources, even on a compatible computer. Restarting it may help. If it doesn’t, try restarting your computer.
Enable graphics acceleration
Graphics acceleration lets Chrome use your computer’s graphics hardware.
Open Chrome’s Settings.
Select System.
Turn on Use graphics acceleration when available.
Click Relaunch if prompted, then try opening Jitter again.
If this setting is already enabled, leave it on and continue below. Enabling it doesn’t guarantee that WebGL 2 will be available.
If the setting is locked on a work or school computer, ask your IT team for help.
Use the latest version of Chrome
Jitter works best in the latest version of Google Chrome on a desktop or laptop. If you’re using another browser, a phone, or a tablet, try Chrome on your computer.
To check for updates, open Chrome’s menu and select Help → About Google Chrome. Install any available update and relaunch Chrome when prompted.
Read more about Jitter’s supported browsers and devices.
If WebGL is still unavailable
Check for updates to your operating system and graphics drivers. Use your computer or graphics card manufacturer’s official update tools, or ask your IT team to help.
Some older devices don’t support WebGL 2. Browsers may also disable graphics features when they detect compatibility or stability problems. If you’re connecting through a remote desktop or virtual machine, try opening Jitter directly on your computer instead.
If possible, try another computer. This can help narrow down whether the issue is specific to your setup—it doesn’t necessarily mean you need to replace your device.
Still having trouble?
Go back to your files and contact us through the help widget. Please include:
A screenshot of the error.
Your browser version, operating system, and computer model.
Whether it happens with one file or every file you try to open.
Whether the editor worked before, and which steps you’ve tried.
The approximate time the error happened, including your time zone.
If you can, also open chrome://gpu in Chrome and send a screenshot or report of the Graphics Feature Status section, including the WebGL and WebGL2 lines.