remotion-dev/remotion · error · Error

<Null> has been removed as of Remotion v4.0.228. The native

Error message

<Null> has been removed as of Remotion v4.0.228. The native clipping APIs were experimental and subject to removal at any time. We removed them because they were sparingly used and made rendering often slower rather than faster.

What it means

Thrown unconditionally by the body of <Null> on every render. <Null> was the public entry point of the experimental native clipping API, removed in Remotion v4.0.228 because it was sparingly used and frequently made rendering slower. The component is still exported (deprecated) so that users with imports see a clear removal message instead of a generic 'undefined is not a component' error.

Source

Thrown at packages/core/src/Null.tsx:5

/**
 * @deprecated <Null /> has been removed as of Remotion v4.0.228. The native clipping APIs were experimental and subject to removal at any time. We removed them because they were sparingly used and made rendering often slower rather than faster.
 */
export const Null: React.FC = () => {
	throw new Error(
		'<Null> has been removed as of Remotion v4.0.228. The native clipping APIs were experimental and subject to removal at any time. We removed them because they were sparingly used and made rendering often slower rather than faster.',
	);
};

View on GitHub (pinned to 78fe4bb3fd)

Solutions

Remove all <Null /> usages from your composition.
If you used <Null> to clip children, switch to <Sequence> with cropLeft/cropRight/cropTop/cropBottom, or to absolutely-positioned children inside an <AbsoluteFill> with overflow hidden.
Update imports to drop <Null> from @remotion/core.
Consult the migration note in the message: native clipping was experimental and removed for performance reasons.

Example fix

// before
<Null>
  <AbsoluteFill>...</AbsoluteFill>
</Null>
// after
<AbsoluteFill style={{overflow: 'hidden'}}>
  ...
</AbsoluteFill>

Defensive patterns

Strategy: validation

Validate before calling

// Grep your codebase before upgrading past v4.0.228
// import {Null} from '@remotion/core';
// Remove every <Null /> usage. Fail CI if any reference remains.

Try / catch

try {
  // run a pre-upgrade codemod that removes <Null> references
} catch (err) {
  // surface to upgrade notes
  throw err;
}

Prevention

Search the codebase for `<Null` and `Null` imports before upgrading Remotion past v4.0.228.
Replace clipping use cases with <Sequence> crop props or CSS overflow:hidden.
Keep your Remotion version pinned and read release notes for breaking removals.
Add an eslint rule banning the import name 'Null' from '@remotion/core'.

When it happens

Trigger: Rendering `<Null />` anywhere in a composition; importing and using <Null> after upgrading past v4.0.228; following an outdated tutorial or example that still uses <Null>.

Common situations: Upgrading Remotion past v4.0.228 with code that still references <Null>; copy-pasted code from an old blog post or Stack Overflow answer; generated code from an LLM trained on the old API.

Related errors

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