AI Video Isn’t Bottlenecked By AI. It’s Bottlenecked By ffmpeg.

You’ve probably seen the demos. An autonomous agent writes a script, generates some images, spits out a voiceover, and boom—a short documentary is posted to TikTok. It feels like magic. It feels like the future of content is already here, fully automated and practically free.

But when you actually build the pipeline, the magic evaporates real fast. You aren’t staring at a marvel of artificial intelligence; you’re staring at an AWS billing dashboard, praying your cloud compute doesn’t bankrupt you before the video finishes rendering.

Recently, a developer managed to get this entire autonomous short-documentary pipeline down to 30 seconds. It uses GLM-5.2 for scripts, Nano Banana 2 Lite for images, and GPT-4o-mini for TTS. The cost? About 25 cents per video. That sounds incredibly cheap until you look under the hood and realize where the money and time are actually going.

We are so obsessed with teaching machines to imagine that we forgot they still have to render.

Everyone assumes the bottleneck for AI video is the generative AI itself. They think we’re just waiting for the next big model to drop a better text-to-image engine. But the reality is far more mundane. The actual speed bottleneck in this 30-second pipeline isn’t the LLM writing the script or the diffusion model drawing the picture. It’s the video compilation step—using ffmpeg to string those images together and add a Ken Burns zoom effect.

To get that compilation step to run fast enough, the developer had to spin up a massive 64-vCPU EC2 instance. You read that right. To generate a 30-second TikTok documentary, you need enterprise-grade cloud compute just to stitch the frames together without timing out.

The future of automated content isn’t bottlenecked by artificial intelligence; it’s bottlenecked by cloud computing unit economics.

Then there’s the cost breakdown. Of the 25 cents it costs to make the video, 90% goes to image generation. The text is cheap. The voiceover is cheap. The images are bleeding the budget dry at 3.3 cents a pop. And to top it off, the Ken Burns zoom effect still has a noticeable shake that no one can seem to fix.

This is the dirty secret of the AI content revolution. The glamorous part—the models hallucinating scripts and generating art—is already dirt cheap and blazing fast. The boring part—compiling the video and paying for the images—is what’s actually holding the entire ecosystem back.

If you’re a developer or a founder looking to build the next wave of automated content, stop trying to optimize the LLM prompts. The models are good enough. Stop chasing model breakthroughs and start optimizing the boring infrastructure. The first person to make image generation 10x cheaper or ffmpeg rendering 10x faster will own the automated content space.

FAQ

Q: If it costs 25 cents and takes 30 seconds, why isn't everyone doing this?

A: Because the 25 cents only covers the generation. Running the 64-vCPU EC2 instance required to compile the video in that timeframe will eat your wallet alive if you're doing this at scale.

Q: What's the practical implication for builders?

A: Founders should stop optimizing LLM prompts and start optimizing image generation costs and ffmpeg rendering speeds. That's where the actual margins are won or lost.

Q: What's the contrarian take?

A: AI video isn't bottlenecked by AI. It's bottlenecked by ffmpeg and cloud compute pricing. The next big content platform won't be built on a new AI model, but on a better video rendering engine.

📎 Source: View Source