remotion-dev/remotion · critical · Error

Waves shader compile failed: ${log ?? '(no log)'}

Error message

Waves shader compile failed: ${log ?? '(no log)'}

What it means

Thrown by compileShader() inside the waves effect when gl.getShaderParameter(shader, gl.COMPILE_STATUS) returns false. This means the GLSL ES 3.00 shader source failed to compile on the current GPU driver. The error includes the GL driver's info log for diagnostics. Since WAVES_VS and WAVES_FS are static library constants, this is a driver/GPU compatibility issue, not a user param issue.

Source

Thrown at packages/effects/src/waves.ts:375

}
`;

const compileShader = (
	gl: WebGL2RenderingContext,
	type: number,
	source: string,
): WebGLShader => {
	const shader = gl.createShader(type);
	if (!shader) {
		throw new Error('Failed to create WebGL shader');
	}

	gl.shaderSource(shader, source);
	gl.compileShader(shader);
	if (!gl.getShaderParameter(shader, gl.COMPILE_STATUS)) {
		const log = gl.getShaderInfoLog(shader);
		gl.deleteShader(shader);
		throw new Error(`Waves shader compile failed: ${log ?? '(no log)'}`);
	}

	return shader;
};

const linkProgram = (
	gl: WebGL2RenderingContext,
	vs: WebGLShader,
	fs: WebGLShader,
): WebGLProgram => {
	const program = gl.createProgram();
	if (!program) {
		throw new Error('Failed to create WebGL program');
	}

	gl.attachShader(program, vs);
	gl.attachShader(program, fs);
	gl.linkProgram(program);

View on GitHub (pinned to 78fe4bb3fd)

Solutions

1. Update GPU drivers to the latest version — shader compile failures on valid source are driver bugs.
2. For headless/server rendering (Remotion Lambda, CI), ensure the Chrome build is current and supports the GLSL constructs used.
3. Check chrome://gpu (or equivalent) for WebGL2 support status and any driver denylisted features.
4. Try a different GPU or toggle hardware acceleration to switch between driver and SwiftShader paths.
5. Report the issue with the full info log from the error message.

try {
  const state = setupWaves(canvas);
} catch (e) {
  if ((e as Error).message.startsWith('Waves shader compile failed')) {
    console.warn('GPU driver rejected waves shader:', (e as Error).message);
    // fall back to a non-WebGL effect
  }
}

When it happens

Trigger: Called transitively from setupWaves() at packages/effects/src/waves.ts:446. Fires when the GPU driver rejects valid GLSL ES 3.00 — e.g., the driver doesn't fully support WebGL2/GLSL 3.00, or has a bug with a specific built-in function or precision qualifier used in WAVES_FS. Most common with older or buggy GPU drivers, or software rasterizers with partial support.

Common situations: Headless Chrome with SwiftShader in CI rejecting a GLSL construct; outdated mobile GPU drivers; virtual machines with passthrough rendering bugs; older integrated GPUs (Intel HD) with known GLSL compiler issues; a browser version that downgraded its WebGL2 backend.

Related errors

• Waves program link failed: ${log ?? '(no log)'}
• Linear gradient shader compile failed: ${log ?? '(no log)'}
• Linear gradient program link failed: ${log ?? '(no log)'}
• Linear progressive blur shader compile failed: ${log ?? '(no
• Noise shader compile failed: ${log ?? '(no log)'}

AI-assisted analysis of remotion-dev/remotion@78fe4bb3fd (2026-08-12). Data as JSON: /api/errors/6fb87754bbb3af91. Report an issue: GitHub.