Skip to main content

Could not play video/audio with src

The following error may occur in your Remotion project during development or while rendering:

diff
- Error: Could not play video with src [source] [object MediaError]
diff
- Error: Could not play video with src [source] [object MediaError]

or

diff
- Error: Could not play audio with src [source] [object MediaError]
diff
- Error: Could not play audio with src [source] [object MediaError]

This error happens when you are trying to embed a <Video/> or <Audio/> tag in your Remotion project but the browser is unable to load and play the media. Although the browser does not report the exact error, there are two common reasons for this error.

Codec not supported by Chromium​

Unlike Google Chrome, the Chromium Browser does not include proprietary codecs. This means you cannot play MP4/H.264 videos and some audio codecs (more codecs may not be supported).

Workaround 1: Use Chrome, not Chromium.

Workaround 2: Convert videos to WebM, use Chrome instead of Chromium, or use <OffthreadVideo>.

note

Since v4.0.18, downloads a browser that includes codecs automatically if you don't have a local browser.

Invalid source​

Make sure you are trying to load a video that is either available locally or publicly on the internet. Open the DevTools, go to the Network tab, track the asset being loaded, and open it in a new tab. Does it actually start playing?

Wrong headers or status code​

In order for the browser being able to play the media, it should be loaded with:

  • a 200 status code
  • a suitable Content-Type header
  • A Content-Range header in order to support seeking.

Open the DevTools and go to the network tab to validate that this is the case.

Internet Download Manager​

Internet Download Manager is known to manipulate the network traffic causing problems for the browser to load media. Disable it if you have it.

Other unsupported codecs​

You might be importing a video that is not compatible with Chrome at all, e.g. FLV.

Too many video tags​

The error message might contain error creating media player, appearing if too many video tags are created.
First check that you are not accidentially creating an infite render loop. For example, changing the key frequently will re-create the video tag on every frame:

tsx
import { Video } from "remotion";
 
export default function SBSVideo() {
  return (
    <>
      {[
        "https://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4",
        "https://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4",
      ].map((video, i) => {
        return <Video key={uuidv4()} src={video} />;
      })}
    </>
  );
}
tsx
import { Video } from "remotion";
 
export default function SBSVideo() {
  return (
    <>
      {[
        "https://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4",
        "https://commondatastorage.googleapis.com/gtv-videos-bucket/sample/BigBuckBunny.mp4",
      ].map((video, i) => {
        return <Video key={uuidv4()} src={video} />;
      })}
    </>
  );
}

If you ruled out this possibility, use <OffthreadVideo> instead as it does not rely on a <video> tag.

Recover from this errorv3.3.89​

You can handle this error and replace it with a different video by passing the onError() prop to the <Video> or <OffthreadVideo> component.

See also​