remotion-dev/remotion · error · Error

The 'frame' prop of <Freeze /> must be a real number, but it

Error message

The 'frame' prop of <Freeze /> must be a real number, but it is NaN.

What it means

Thrown by <Freeze /> when frame is the value NaN. This typically results from an arithmetic bug (0/0, parsing failure, undefined math) rather than a missing prop.

Source

Thrown at packages/core/src/freeze.tsx:41

	active = true,
}) => {
	const frame = useCurrentFrame();
	const videoConfig = useVideoConfig();

	if (typeof frameToFreeze === 'undefined') {
		throw new Error(
			`The <Freeze /> component requires a 'frame' prop, but none was passed.`,
		);
	}

	if (typeof frameToFreeze !== 'number') {
		throw new Error(
			`The 'frame' prop of <Freeze /> must be a number, but is of type ${typeof frameToFreeze}`,
		);
	}

	if (Number.isNaN(frameToFreeze)) {
		throw new Error(
			`The 'frame' prop of <Freeze /> must be a real number, but it is NaN.`,
		);
	}

	if (!Number.isFinite(frameToFreeze)) {
		throw new Error(
			`The 'frame' prop of <Freeze /> must be a finite number, but it is ${frameToFreeze}.`,
		);
	}

	const isActive = useMemo(() => {
		if (typeof active === 'boolean') {
			return active;
		}

		if (typeof active === 'function') {
			return active(frame);
		}

View on GitHub (pinned to 78fe4bb3fd)

Solutions

1. Trace the NaN to its source: log the operands of the frame expression.
2. Default the operands: frame={(a ?? 0) / (b ?? 1)}.
3. Guard before render: if (Number.isNaN(frame)) return null;.
4. Use Remotion's interpolate with clamp to avoid undefined math.

Example fix

// before
const frame = Number(input.offset) / step; // NaN when input.offset undefined
<Freeze frame={frame}>{scene}</Freeze>

// after
const offset = typeof input.offset === 'number' ? input.offset : 0;
<Freeze frame={offset / step}>{scene}</Freeze>

const frame = computeFrame(input);
if (Number.isNaN(frame)) {
  console.warn('frame resolved to NaN; defaulting to 0');
  return <Freeze frame={0}>{children}</Freeze>;
}
return <Freeze frame={frame}>{children}</Freeze>;

const isRealNumber = (v: unknown): v is number => typeof v === 'number' && !Number.isNaN(v);

When it happens

Trigger: Passing frame={someCalc} where someCalc evaluated to NaN — e.g. Number(undefined), parseInt failure, or division by zero.

Common situations: Frame computed from optional input props that resolved to undefined then coerced via Number(); broken arithmetic in a frame-calculation helper.

Related errors

• The <Freeze /> component requires a 'frame' prop, but none w
• The 'frame' prop of <Freeze /> must be a number, but is of t
• The 'frame' prop of <Freeze /> must be a finite number, but
• The "trimBefore" prop of <Sequence /> must be a real number,
• The "freeze" prop of <Sequence /> must be a number, but is o

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