remotion-dev/remotion · error · Error

Program link failed: ${log ?? '(no log)'}

Error message

Program link failed: ${log ?? '(no log)'}

What it means

Thrown by linkProgram() in the chromatic aberration runtime when both shaders compiled but gl.linkProgram() failed (LINK_STATUS false); the program info log is embedded. With the shipped static shaders this typically reflects a driver/GLSL ES 3.00 linker bug or a degraded context rather than a source defect.

Source

Thrown at packages/effects/src/chromatic-aberration/chromatic-aberration-runtime.ts:58

};

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);
	if (!gl.getProgramParameter(program, gl.LINK_STATUS)) {
		const log = gl.getProgramInfoLog(program);
		gl.deleteProgram(program);
		throw new Error(`Program link failed: ${log ?? '(no log)'}`);
	}

	return program;
};

const createProgram = (
	gl: WebGL2RenderingContext,
	vertexSource: string,
	fragmentSource: string,
): WebGLProgram => {
	const vs = compileShader(gl, gl.VERTEX_SHADER, vertexSource);
	const fs = compileShader(gl, gl.FRAGMENT_SHADER, fragmentSource);
	const program = linkProgram(gl, vs, fs);
	gl.deleteShader(vs);
	gl.deleteShader(fs);
	return program;
};

View on GitHub (pinned to 78fe4bb3fd)

Solutions

1. Read the embedded info log for the linker's specific complaint.
2. Update GPU drivers to the latest stable release.
3. Switch to a GPU-accelerated renderer (disable software fallback).
4. Upgrade @remotion/effects to ensure the shipped shaders are intact.
5. Reproduce in Chrome for Testing on different hardware to confirm a driver-specific issue.

try {
  return <ChromaticAberration {...props} />;
} catch (err) {
  const msg = String(err);
  if (/Program link failed/.test(msg)) {
  reportShaderError(msg);
  return <FallbackFrame />;
  }
  throw err;
}

When it happens

Trigger: gl.linkProgram() at chromatic-aberration-runtime.ts:54 completes but gl.getProgramParameter(LINK_STATUS) is false at :55; the info log is read, the program deleted, and the error at :58 is thrown.

Common situations: Buggy/outdated GPU drivers, software rasterizers with incomplete GLSL ES 3.00 linkers, blocklisted GPUs, or a corrupted build of @remotion/effects.

Related errors

• Checkerboard program link failed: ${log ?? '(no log)'}
• Shader compile failed: ${log ?? '(no log)'}
• Failed to create WebGL program
• Checkerboard shader compile failed: ${log ?? '(no log)'}
• Failed to create WebGL program

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