Error: Cannot find module '@ffmpeg/core' means ffmpeg.wasm 0.11 has no core to load. Pin @ffmpeg/core@0.11.0 and delete global fetch, or let ReelSDK run native ffmpeg 8.1 at $0.02 per compute minute.

Error: Cannot find module '@ffmpeg/core'

We reproduced it on Node.js 22 with @ffmpeg/ffmpeg 0.11.6: the core took two more fixes before a 2-second cut ran in about 16 seconds. ReelSDK did the same cut in under 4 seconds, with nothing installed.

ErrorsUpdated

Node.js 22, @ffmpeg/ffmpeg 0.11.6, no @ffmpeg/core installed
Error: Cannot find module '@ffmpeg/core'
Require stack:
- /tmp/mod/node_modules/@ffmpeg/ffmpeg/src/node/getCreateFFmpegCore.js
- /tmp/mod/node_modules/@ffmpeg/ffmpeg/src/node/index.js
- /tmp/mod/node_modules/@ffmpeg/ffmpeg/src/createFFmpeg.js
- /tmp/mod/node_modules/@ffmpeg/ffmpeg/src/index.js
    at /tmp/mod/node_modules/@ffmpeg/ffmpeg/src/node/getCreateFFmpegCore.js:6:31 {
  code: 'MODULE_NOT_FOUND',

Source: ffmpeg.wasm 0.11.6: getCreateFFmpegCore.js, checked November 2026.

Where it shows up

At ffmpeg.load(), in Node.js with ffmpeg.wasm 0.11

You install @ffmpeg/ffmpeg 0.11.6, call createFFmpeg() and then ffmpeg.load() in Node.js. On Node.js 22 the load threw Error: Cannot find module '@ffmpeg/core' with code MODULE_NOT_FOUND, from the package's own getCreateFFmpegCore.js, before any video was read.

Every frame of the require stack sits inside node_modules/@ffmpeg/ffmpeg/src, so the trace points at the library, not at your code. The project has the wrapper but not the core it loads.

Why it happens

0.11 loads a core package it does not install

ffmpeg.wasm 0.11 ships in two parts: @ffmpeg/ffmpeg, the JavaScript API, and @ffmpeg/core, the WebAssembly build of ffmpeg. In Node the default is corePath: '@ffmpeg/core', and load() simply calls require(corePath).

But 0.11.6 depends only on is-url, node-fetch, regenerator-runtime and resolve-url. The core is a dev dependency, used for its own tests, so npm never installs it for you, and the require fails.

Causes and fixes

Each step we ran with @ffmpeg/ffmpeg 0.11.6

Each step we ran with @ffmpeg/ffmpeg 0.11.6
SetupNode.jsResult
No core installed22Error: Cannot find module '@ffmpeg/core'
npm i @ffmpeg/core (0.12)22ReferenceError: self is not defined
@ffmpeg/core@0.11.022 and 24TypeError: Failed to parse URL from .../ffmpeg-core.wasm
0.11.0 with --no-experimental-fetch22Works
0.11.0 with --no-experimental-fetch24Flag rejected, exit code 9
0.11.0, delete globalThis.fetch22 and 24Works

Source: ffmpeg.wasm 0.11.6: getCreateFFmpegCore.js, checked November 2026.

The local fix

Install @ffmpeg/core@0.11.0, then remove global fetch

Do not install the latest core: npm i @ffmpeg/core gives you the 0.12 line, a browser build, and 0.11.6 then fails with ReferenceError: self is not defined. Pin @ffmpeg/core@0.11.0. That clears the module error, but on Node 22 and 24 the next run failed with TypeError: Failed to parse URL from .../ffmpeg-core.wasm: the core reads its .wasm with fetch() when one exists, and Node now has one.

node --no-experimental-fetch fixed that on Node 22, but Node 24 rejects the flag as an invalid negation. Deleting globalThis.fetch before load() worked on both, at about 16 seconds a run on Node 22. Native ffmpeg did the same cut more than 3 times faster.

terminal
npm i @ffmpeg/ffmpeg@0.11.6 @ffmpeg/core@0.11.0
convert.mjs
import { readFile, writeFile } from "node:fs/promises";
import { createFFmpeg } from "@ffmpeg/ffmpeg";

// The 0.11 core reads its .wasm with fetch() when it exists, which fails on a file path
delete globalThis.fetch;

const started = Date.now();
const ffmpeg = createFFmpeg({ log: false });
await ffmpeg.load();

ffmpeg.FS("writeFile", "in.mp4", await readFile("in.mp4"));
await ffmpeg.run("-i", "in.mp4", "-t", "2", "-vf", "scale=720:-2", "out.mp4");
await writeFile("out.mp4", ffmpeg.FS("readFile", "out.mp4"));
console.log(`ok in ${Date.now() - started} ms`);
process.exit(0);

Skip the binary

Or skip WebAssembly and call the API

POST /v1/ffmpeg runs native ffmpeg 8.1 on a fresh machine per job, so your Node project installs neither package. The same cut and scale came back as a 720x1280 out.mp4 in under 4 seconds.

Compute is $0.02 per minute, billed per second, so the job cost under a fifth of a cent.

convert.mjsTry it
const res = await fetch("https://api.reelsdk.com/v1/ffmpeg?wait=60", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.REELSDK_KEY}`, "Content-Type": "application/json" },
  body: JSON.stringify({
    "inputs": {
      "in.mp4": "https://api.reelsdk.com/f/lib/demo/clip.mp4"
    },
    "args": ["-i", "in.mp4", "-t", "2", "-vf", "scale=720:-2", "out.mp4"],
    "outputs": ["out.mp4"]
  }),
});
const { job } = await res.json();
The same 2-second cut and scale on the API, at 720x1280.Input: clip.mp4

Why not upgrade to 0.12?

Because 0.12 does not run in Node. ffmpeg.wasm dropped Node.js support in 0.12.0, and @ffmpeg/ffmpeg 0.12 threw Error: ffmpeg.wasm does not support nodejs as soon as we loaded it. 0.12 is for browsers, where you pass coreURL and wasmURL to load() instead of installing a core package for require.

In Node your choices are the old 0.11 pair with the fixes above, a native ffmpeg binary, or an API. Native was more than 3 times faster on our machine.

FAQ

Questions, answered

Which @ffmpeg/core version goes with @ffmpeg/ffmpeg 0.11.6?

0.11.0. It is the only 0.11 release of @ffmpeg/core and the version 0.11.6 lists in its own dev dependencies. The latest core, from the 0.12 line, is a browser build and fails in Node with ReferenceError: self is not defined.

Why do I get Failed to parse URL after installing the core?

The 0.11.0 core loads its .wasm with fetch() whenever fetch exists, and fetch can't read a file path. Node 22 and 24 have a global fetch; delete globalThis.fetch before load(), or run node --no-experimental-fetch on Node 22.

Can I use @ffmpeg/ffmpeg 0.12 in Node.js?

No. 0.12 throws Error: ffmpeg.wasm does not support nodejs; ffmpeg.wasm dropped Node support in 0.12.0. Use 0.11 with a pinned core, native ffmpeg, or an API.

Is ffmpeg.wasm slower than native ffmpeg?

Yes, by a lot. The same 2-second cut took about 16 seconds in ffmpeg.wasm on Node 22 and about 5 seconds with native ffmpeg on the same machine.

Ready to build?

Ship video from your app today

Your first $0.50 is free, and one key covers every endpoint.

Moonlit lake with a lit cabin under the mountains