Serverless ffmpeg

The serverless ffmpeg handbook: every runtime, one API

Every serverless runtime shuts ffmpeg out for its own reason, and the fix differs by platform. This is the index: what each host blocks, and the single call that routes around it. Start from your platform, or jump straight to the operation you need.

By platform

Why the native ffmpeg binary can't run on each serverless runtime — and the one-call fix. Pick yours for the full guide.

PlatformNative ffmpegWhat blocks it
Run ffmpeg on VercelNo250MB unzipped Node function bundle cap — ffmpeg plus codecs don't fit
Run ffmpeg on SupabaseNoDeno runtime has no child_process/subprocess API, so you can't exec the ffmpeg binary
Run ffmpeg on NetlifyNoffmpeg binary + libs exceed Netlify's 50MB-zipped Lambda deploy cap
Run ffmpeg on Cloudflare WorkersNoV8 isolate: no native binaries — can't install or exec the ffmpeg binary
Run ffmpeg on AWS LambdaBarelyRuns only via a self-packaged ffmpeg layer kept under the 250MB unzipped limit
Run ffmpeg on Deno DeployNoV8 isolates have no subprocess API and no FFI, so the ffmpeg binary can't launch

Ship it with one API call

Grab a free key and make your first call in under five minutes.