{"id":5082,"date":"2026-02-05T14:31:27","date_gmt":"2026-02-05T06:31:27","guid":{"rendered":"https:\/\/crepal.ai\/blog\/?p=5082"},"modified":"2026-02-05T14:31:30","modified_gmt":"2026-02-05T06:31:30","slug":"blog-how-to-fix-remotion-render-failed","status":"publish","type":"post","link":"https:\/\/crepal.ai\/blog\/aivideo\/blog-how-to-fix-remotion-render-failed\/","title":{"rendered":"How to Fix \u201cRemotion Render Failed\u201d (FFmpeg\/FFprobe, Missing Assets, Decode Errors)"},"content":{"rendered":"\n

I spent three hours last Tuesday staring at “Render failed” errors. The video previewed perfectly in Remotion Studio<\/a> \u2014 smooth animations, audio synced, everything looked great. Hit render, and… crash. No helpful error message, just a vague failure.<\/p>\n\n\n\n

Turns out, there are about five common reasons Remotion renders fail, and once you know what to look for in the logs, most of them take 2 minutes to fix. I’m Dora. I tested these fixes across different setups on February 2-4, 2026, and documented what actually works.<\/p>\n\n\n\n

Here’s how to diagnose the failure fast, fix the usual suspects, and avoid them next time.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

Diagnose in 60 Seconds (Which Log Lines Matter)<\/h2>\n\n\n\n

When a render fails, Remotion dumps a wall of text. Most of it is noise.<\/p>\n\n\n\n

Three critical patterns to find:<\/strong><\/p>\n\n\n\n

    \n
  1. FFmpeg\/FFprobe errors:<\/strong>Command failed with exit code 1: ffmpeg<\/code> or ffprobe<\/code> \u2014 FFmpeg can’t find a file or can’t decode something<\/li>\n\n\n\n
  2. Asset errors:<\/strong>Error loading image\/video\/audio<\/code> or No such file or directory<\/code> \u2014 wrong path or missing file<\/li>\n\n\n\n
  3. Decode errors:<\/strong>Cannot decode<\/code> or Compositor error: No frame found<\/code> \u2014 corrupted file or unsupported format<\/li>\n<\/ol>\n\n\n\n

    Quick diagnosis:<\/strong> Scroll to the bottom of the error first. The last 5-10 lines usually contain the actual failure. Everything above is just stack traces.<\/p>\n\n\n\n

    I wasted 20 minutes reading logs top-to-bottom my first time. The actual error \u2014 ffprobe: No such file or directory<\/code> \u2014 was right at the end.<\/p>\n\n\n\n

    Example error:<\/strong><\/p>\n\n\n\n

    Error: Command failed with exit code 1: ffprobe -v error \n\/tmp\/remotion-assets\/371949071995914.mp4: No such file or directory<\/code><\/pre>\n\n\n\n
    This tells you: FFprobe tried to analyze a video that doesn’t exist. Asset problem, not FFmpeg problem.<\/p>\n\n\n\n
    Fix FFmpeg\/FFprobe Issues (Auto-Install vs PATH vs Custom Binaries)<\/h2>\n\n\n\n
    Good news: Remotion v4.0+ <\/a>bundles FFmpeg automatically. You don’t need to install anything.<\/p>\n\n\n\n
    \n
    \"\"<\/figure>\n<\/figure>\n\n\n\n
    But sometimes it still breaks.<\/p>\n\n\n\n
    Issue 1: You’re on Remotion v3 (Upgrade)<\/h3>\n\n\n\n
    Check your version:<\/p>\n\n\n\n
    bash<\/p>\n\n\n\n
    npm list @remotion\/cli<\/code><\/pre>\n\n\n\n
    If it says 3.x.x<\/code>, upgrade to v4:<\/p>\n\n\n\n
    bash<\/p>\n\n\n\n
    npm install @remotion\/cli@latest @remotion\/renderer@latest<\/code><\/pre>\n\n\n\n
    According to the v4 migration docs<\/a>, FFmpeg is now baked into @remotion\/renderer<\/code> \u2014 no manual installation needed.<\/p>\n\n\n\n
    \n
    \"\"<\/figure>\n<\/figure>\n\n\n\n
    Can’t upgrade?<\/strong> On v3, force FFmpeg reinstall:<\/p>\n\n\n\n
    bash<\/p>\n\n\n\n
    npx remotion install ffmpeg\nnpx remotion install ffprobe<\/code><\/pre>\n\n\n\n
    (These commands don’t exist in v4 <\/a>since FFmpeg is bundled.)<\/p>\n\n\n\n
    Issue 2: Custom FFmpeg Binary Conflicts<\/h3>\n\n\n\n
    If you set ffmpegExecutable<\/code> or ffprobeExecutable<\/code> in your render config, remove them \u2014 v4 doesn’t support these options.<\/p>\n\n\n\n
    javascript<\/p>\n\n\n\n
    \/\/ \u274c Remove this<\/em>\nawait renderMedia({\n  ffmpegExecutable: '\/usr\/local\/bin\/ffmpeg',\n});\n\n\/\/ \u2705 Use this<\/em>\nawait renderMedia({\n  composition,\n  outputLocation: '.\/out.mp4',\n});<\/code><\/pre>\n\n\n\n
    “Cannot Decode” Root Causes + Safe Asset Rules<\/h3>\n\n\n\n
    The most frustrating errors: Cannot decode<\/code> or No frame found at position X<\/code>. These happen when FFmpeg can’t decode your file’s data.<\/p>\n\n\n\n
    Root cause 1: Unsupported codec<\/strong><\/p>\n\n\n\n
    Remotion supports<\/a>: H.264, H.265, VP8, VP9, ProRes (video); AAC, MP3, Opus (audio). Anything else won’t work.<\/p>\n\n\n\n
    Check your codec:<\/p>\n\n\n\n
    bash<\/p>\n\n\n\n
    npx remotion ffprobe your-video.mp4<\/code><\/pre>\n\n\n\n
    Look for Video:<\/code> and Audio:<\/code> lines. If unsupported, re-encode:<\/p>\n\n\n\n
    bash<\/p>\n\n\n\n
    npx remotion ffmpeg -i input.mp4 -c:v libx264 -c:a aac output.mp4<\/code><\/pre>\n\n\n\n
    Root cause 2: Variable frame rate (VFR)<\/strong><\/p>\n\n\n\n
    Screen recordings often use VFR. Remotion needs constant frame rate (CFR).<\/p>\n\n\n\n
    Convert to CFR:<\/p>\n\n\n\n
    bash<\/p>\n\n\n\n
    npx remotion ffmpeg -i input.mp4 -vsync cfr -r 30 output.mp4<\/code><\/pre>\n\n\n\n
    Root cause 3: Corrupted file<\/strong><\/p>\n\n\n\n
    Test if the file is readable:<\/p>\n\n\n\n
    bash<\/p>\n\n\n\n
    npx remotion ffmpeg -i your-video.mp4 -f null -<\/code><\/pre>\n\n\n\n
    If this throws errors, re-download or re-export.<\/p>\n\n\n\n
    Root cause 4: Container issues<\/strong><\/p>\n\n\n\n
    Re-mux to fix weird metadata:<\/p>\n\n\n\n
    bash<\/p>\n\n\n\n
    npx remotion ffmpeg -i input.mp4 -c copy -map 0 output.mp4<\/code><\/pre>\n\n\n\n
    Safe asset rules:<\/strong><\/p>\n\n\n\n