CAN'T USE SCRATCH.MIT.EDU!!!

Looks like the problem has been solved on Microsoft Edge 146.0.3856.97

Microsoft are currently working to add WebGL support to Edge.

Open Edge, then paste this into the address bar and press Enter>

edge://flags

Perform a search in there for webgl

You should find the experimental 'WebGL Draft Extensions' setting, enable that and restart Edge to test if that resolves the problem.

If not, in Edge, press Alt + Shift + i to open the Edge Feedback panel, and suggest to the Edge developers they add WebGL support in a future update to Edge.

Microsoft Edge does support WebGL and WebGL 2, and sites like Scratch and Wix are expected to work when WebGL and hardware acceleration are available.

If Scratch or Wix report that WebGL is not available, the most likely causes are:

1. Hardware acceleration is disabled in Edge
   • In Edge, go to edge://settings/system.
   • Ensure that hardware acceleration is enabled (the setting should not indicate that hardware acceleration is disabled).
   • If it was disabled and is now enabled, restart Edge and test Scratch again.
2. 3D APIs are blocked by policy (enterprise / managed devices)
   • The Disable3DAPIs policy can prevent web pages from accessing the GPU, which blocks WebGL and Pepper 3D APIs.
   • If this policy is enabled (set to true) by an administrator, WebGL will not work in Edge.
   • On managed devices, only the administrator can change this policy.
3. Hardware acceleration policy interaction
   • If the HardwareAccelerationModeEnabled policy is set to false, Edge treats Disable3DAPIs as if it were true, effectively blocking WebGL.
   • In that case, WebGL will not be available until hardware acceleration is allowed again by policy.
4. Edge version and WebGL backend changes
   • Starting with Microsoft Edge Stable version 144 on Windows systems without a physical GPU, Edge uses the Windows Advanced Rasterization Platform (WARP) as the software backend for WebGL instead of SwiftShader.
   • On non‑Windows platforms, a physical GPU is required for WebGL.
   • If WebGL is failing specifically because SwiftShader was removed and the environment relies on it (for example, some headless or virtualized setups), an administrator can temporarily enable the EnableUnsafeSwiftShader policy to continue using SwiftShader. This is a temporary, security‑risk workaround and is scheduled for removal in a future release.
5. Browser or OS not meeting WebGL requirements
   • For the best experience with WebGL 2, use the new Microsoft Edge, Chrome, or Firefox.
   • WebGL browser support is required for running WebGL‑based sites such as Scratch or WebGL‑based SharePoint spaces.

If this is a personal (non‑managed) Windows 11 device, check hardware acceleration in Edge settings first. If the device is managed by an organization (school or work), contact the IT administrator to verify that Disable3DAPIs and hardware acceleration policies are not blocking WebGL.

References:

• Disable3DAPIs
• EnableUnsafeSwiftShader
• Archived release notes for Microsoft Edge Stable Channel
• Device support for SharePoint spaces