remotion-dev/remotion · error

The version of the function that was specified as "rendererF

Error message

The version of the function that was specified as "rendererFunctionName" is ${VERSION} but the version of the function that invoked the render is ${params.launchFunctionConfig.version}. Please make sure that the version of the function that is specified as "rendererFunctionName" is the same as the version of the function that is invoked.

What it means

The renderer Lambda checks that the @remotion/lambda version running inside the renderer function matches the version embedded in the launch payload (launchFunctionConfig.version). A mismatch means the render would run with incompatible internals, so it refuses to proceed.

Source

Thrown at packages/serverless/src/handlers/renderer.ts:82

				audioOutputLocation: string | null;
				isAudioOnly: boolean;
				completedAt: number;
		  }) => Promise<void>)
		| null;
	cancelSignal: CancelSignal | null;
}): Promise<{}> => {
	if (params.type !== ServerlessRoutines.renderer) {
		throw new Error('Params must be renderer');
	}

	const chromiumOptions =
		insideFunctionSpecifics.normalizeChromiumOptions?.({
			chromiumOptions: params.chromiumOptions,
			logLevel: params.logLevel,
		}) ?? params.chromiumOptions;

	if (params.launchFunctionConfig.version !== VERSION) {
		throw new Error(
			`The version of the function that was specified as "rendererFunctionName" is ${VERSION} but the version of the function that invoked the render is ${params.launchFunctionConfig.version}. Please make sure that the version of the function that is specified as "rendererFunctionName" is the same as the version of the function that is invoked.`,
		);
	}

	const inputPropsPromise = decompressInputProps({
		bucketName: params.bucketName,
		expectedBucketOwner: options.expectedBucketOwner,
		region: insideFunctionSpecifics.getCurrentRegionInFunction(),
		serialized: params.inputProps,
		propsType: 'input-props',
		providerSpecifics,
		forcePathStyle: params.forcePathStyle,
		requestHandler: null,
	});

	const resolvedPropsPromise = decompressInputProps({
		bucketName: params.bucketName,
		expectedBucketOwner: options.expectedBucketOwner,

View on GitHub (pinned to b2f4e34732)

Solutions

1. Redeploy the Lambda functions so they bundle the same @remotion/lambda version (deployLambdaFunction or npx remotion lambda functions deploy)
2. Deduplicate node_modules so a single @remotion/lambda version is installed (bun install / check lockfile)
3. Delete stale functions (remotion lambda functions rm) and deploy fresh
4. Pin @remotion/lambda (and all Remotion packages) to the same exact version across app and deployed functions

Example fix

// before
bun install @remotion/lambda@latest
// then render without redeploying -> version mismatch
// after
bun install @remotion/lambda@latest
npx remotion lambda functions deploy --region us-east-1  # redeploy matching function version

import {VERSION} from '@remotion/lambda';
import {getFunctions} from '@remotion/lambda';
const fns = await getFunctions({region, compatibleOnly: true});
if (!fns.length) throw new Error('Deploy a Lambda function matching @remotion/lambda@' + VERSION);

null

try {
  await renderMediaOnLambda({...});
} catch (e) {
  if (String((e as Error).message).includes('rendererFunctionName')) {
    // redeploy functions with matching version, then retry
  } else { throw e; }
}

When it happens

Trigger: params.launchFunctionConfig.version !== VERSION in the renderer handler — caused by deploying a new @remotion/lambda while the deployed Lambda function still bundles an older (or newer) version, or an orchestrator on a different version launching an older renderer function.

Common situations: Upgrading @remotion/lambda locally without redeploying the Lambda functions; multiple package versions in node_modules (duplicate @remotion/lambda); deployLambdaFunction skipped in CI; blue/green function versions out of sync.

Related errors

• Version mismatch: When calling renderMediaOnCloudRun(), you
• Deploying the site failed, and removing the generated bundle
• could not parse Lambda progress response: %w
• Lambda was created but has no name
• Invalid JSON: ${JSON.stringify(decoded)}

AI-assisted analysis of remotion-dev/remotion@b2f4e34732 (2026-09-09). Data as JSON: /api/errors/d88a9662b7482bc6. Report an issue: GitHub.