Shader Effects fail in Fimga Desktop and Chrome despite HTTP 200 downloads
Hello Figma Support,
Shader Effects fail on seven corporate Windows PCs in both Figma Desktop and Google Chrome. Affected effects include Pattern Refraction, Pixelate, and Chromatic Metal. Our team reports that these effects work on macOS.
Steps to reproduce
-
Open a Figma Design file and place a JPG or PNG on the canvas.
-
Select the image and apply Effects → Shader → Pattern Refraction.
-
Check the image on the canvas. The same issue has been reported with Pixelate and Chromatic Metal.
Expected behavior: The shader visibly changes the image.
Actual behavior: Users have seen “This shader effect failed to load.” In our diagnostic run, the effect appeared in the Effects panel, but the image did not visibly change.
Diagnostics
-
Chrome network capture: Shader metadata requests to
www.figma.com/file/…/custom_tool_artifacts/batchand the corresponding shader package URLs ons3-alpha.figma.comreturned HTTP 200 OK. The package responses hadContent-Type: application/zip. The Pattern Refraction and Chromatic Metal ZIP bodies were present in the HAR and contained readablemain.jsandfeatures.jsonfiles. Figma loggedcustom_tool.artifact_downloadwithstatus: successfor Pattern Refraction, Chromatic Metal, and Pixelate. -
Chrome graphics: Chrome
158.0.8127.36on Windows build26200.8875, with an NVIDIA RTX 3050 and driver32.0.15.9579. Figma loggedwebgpu_success.chrome://gpureports hardware acceleration, an available Dawn D3D12 backend for the RTX 3050, and zero GPU process crashes. -
Figma Desktop graphics: Figma Desktop
126.12.7(Electron44.11.3) loggedgraphicsAPI: "WebGPU"andwebGPUVendor: "intel"with Intel UHD Graphics 730. The renderer finished initialization, and the shader issue was still observed in Desktop. -
Desktop frontend commit:
9047f5995fcc763e7cd63542af5cb22ff8c8a433 -
Desktop Sentry event ID:
f15a8abf7d5a4796978e33a5ab86352a
Could you look up the Sentry event and check whether it points to a shader execution or rendering error? Is there a known Windows issue that matches this behavior? If you need a specific log from the shader worker or rendering pipeline, please let us know how to capture it. A workaround we can deploy across the affected Windows PCs would also help.
