`react-doctor/remotion-no-next-image`

Next.js Image can flicker in Remotion

Category: Bugs
Severity: error
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: remotion:4
Tags: react-jsx-only
Default: Enabled

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/remotion-no-next-image. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.

Compare the code

The corrected pattern shows a focused way to address the diagnostic.

Reported pattern

import Image from "next/image";
import { useCurrentFrame } from "remotion";

const Scene = () => {
  useCurrentFrame();
  return <Image src={staticFile("cover.png")} alt="" fill />;
};

Corrected pattern

import { Img, useCurrentFrame } from "remotion";

const Scene = () => {
  useCurrentFrame();
  return (
    <Img
      src={staticFile("cover.png")}
      alt=""
      style={{
        height: "100%",
        inset: 0,
        position: "absolute",
        width: "100%",
      }}
    />
  );
};

How to fix

Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.

Copyable fix prompt

Copy this self-contained prompt into your coding agent after you confirm the diagnostic.

Fix every confirmed react-doctor/remotion-no-next-image diagnostic in the current repository. Required change: - Use Img from remotion, which delays rendering until the image is loaded.

Reference transformation:Before:

import Image from "next/image";
import { useCurrentFrame } from "remotion";

const Scene = () => {
  useCurrentFrame();
  return <Image src={staticFile("cover.png")} alt="" fill />;
};

After:

import { Img, useCurrentFrame } from "remotion";

const Scene = () => {
  useCurrentFrame();
  return (
    <Img
      src={staticFile("cover.png")}
      alt=""
      style={{
        height: "100%",
        inset: 0,
        position: "absolute",
        width: "100%",
      }}
    />
  );
};

Constraints: - Confirm the reported code matches the Before pattern. - Make the smallest change that fixes the root cause. - Preserve behavior and interfaces unrelated to this diagnostic. - Reuse existing project components, utilities, and conventions. - Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations. - Adapt identifiers and framework details instead of copying blindly. - Do not disable the rule or suppress matching code. - Confirm this rule is enabled for the project: remotion:4. Verification: - Run focused tests for the changed behavior. - Run React Doctor and confirm this diagnostic no longer appears. - Report the files changed and any checks you could not run.

More Bugs rules from the rules reference:

react-doctor/remotion-stable-delay-render-handle: delayRender handle is recreated during render
react-doctor/rendering-conditional-render: Change to `{items.length > 0 && <List />}` or use a ternary: `{items.length ? <List /> : null}`
react-doctor/rendering-hydration-mismatch-time: Wrap dynamic time/random values in useEffect+useState (client-only) or add suppressHydrationWarning to the parent if intentional
react-doctor/require-render-return: Require class component render() methods to return a value — a missing return renders nothing.
react-doctor/rerender-dependencies: Extract to a useMemo, useRef, or module-level constant so the reference is stable

react-doctor/remotion-no-next-image