Ask most production teams how they are using AI and the conversation drifts straight to script drafts and writers’-room assistants. That framing is comfortable, and it is also where the smaller budget lives. The money in a feature or a streaming season sits in post — compositing, roto, cleanup, set extension, de-aging, crowd replication, conform. If your generative-AI strategy stops at the page, you have built tooling that helps the people who cost the least and ignored the pipeline where the spend concentrates. That is the failure this article is about. Not that LLMs are useless in film — they are genuinely good at coverage notes, continuity tracking, and first-pass dialogue variants — but that LLM-centric framing has become a default that quietly narrows the surface. Generative AI in film is a much wider category than text generation, and the parts that move a production budget are mostly not text. Why LLM-Only Framing Misses the Budget The mechanism is simple. LLMs are the most visible generative tools because they are the most accessible — a browser tab and a prompt. So when a studio technology lead is asked to “look into generative AI,” the path of least resistance is a chat interface, and the deliverable is a script tool. The trap is that visibility and budget impact are inversely correlated here. A feature’s above-the-line writing costs are real but bounded. The post-production pipeline — visual effects, color, sound, conform — is where labor-hours stack up and where schedules slip. Generative AI that touches that pipeline operates on a different family of models entirely: diffusion models for image synthesis and inpainting, video-generation models for temporal coherence, and multi-modal systems that condition on plates, depth maps, and camera tracks rather than on prose. This is the broader-than-LLMs framing we treat as the starting point for any generative AI engineering engagement — the question is never “which chatbot” but “where in the pipeline does a generative model replace or accelerate a labor-bound step.” When the framing collapses to text, the diffusion and video surface — the expensive surface — never gets scoped. The Generative-AI Surface in Film, Decomposed It helps to lay the surface out explicitly, because “AI in filmmaking” is not one thing and the model families behind each use are genuinely different. Production stage Generative use Model family Where the value lands Development / writing Coverage, dialogue variants, continuity Large language models Speed in the writers’ room (bounded budget) Pre-visualization Concept frames, mood boards, storyboard fills Diffusion (image) Faster iteration before any plate is shot Cinematography assist Shot framing suggestions, lighting reference Multi-modal / vision Director and DP iteration speed VFX / compositing Inpainting, rig removal, set extension, cleanup Diffusion + video Labor-hour reduction (large budget) De-aging / face work Identity-consistent face synthesis Diffusion + identity conditioning Replaces frame-by-frame manual work Crowd / background Background generation and replication Video-generation models Replaces plate shoots and manual duplication Conform / cleanup Temporal denoise, upscale, restoration Video diffusion Post-pipeline throughput The point of the table is not the rows individually — it is that exactly one row uses LLMs, and it sits at the top where the budget is smallest. A film-production AI programme that only fills that row has, in our experience, addressed a fraction of the addressable cost (observed across the film and post-production engagements we have scoped; not a published benchmark). How Diffusion and Video Models Fit a Post-Production Pipeline The integration question is where most studio conversations stall, because the models do not drop into existing pipelines the way an LLM API does. A post-production pipeline already runs on Nuke, Houdini, Resolve, and a render farm with strict color management and frame-accurate conform. A diffusion model that hallucinates a different result on every frame is worse than useless there — it breaks temporal coherence, and a flickering set extension is a reshoot, not a saving. So the engineering problem is conditioning and consistency, not generation. Practical pipelines condition diffusion models on the existing plate, depth, optical flow, and matte channels so the generated content is locked to the shot rather than invented from a text prompt. Video-generation models add temporal attention so that a cleaned or extended region stays stable across the cut. Frameworks like PyTorch and runtimes such as TensorRT show up here for the same reason they show up in any latency-bound vision system: the model has to run at production resolution across thousands of frames, and a per-frame inference cost that is fine in a demo becomes a render-farm line item at scale. This is precisely the territory our work on cinematic VFX and AI-enhanced post-production covers in detail — how generative models slot into compositing and cleanup without breaking the conform. The cinematography-assist surface, where models suggest framing and lighting rather than generate final pixels, is a different integration problem covered in our piece on AI for next-level cinematography. The script-augmentation row — the one LLM row in the table — is treated on its own terms in whether AI can write TV-show scripts. What “AI Has Been Used in Movies” Actually Means The honest answer to “has AI been used in any movies” is yes, routinely, and mostly invisibly. De-aging work, voice restoration, background cleanup, and upscaling have used machine-learning tools for years before “generative AI” became the headline phrase. The visible, controversial cases — synthetic performances, voice cloning, fully generated shots — are a small and contested slice of a much larger, quieter adoption inside the post pipeline. That distinction matters for scoping. A production lead who reads the headlines and concludes that “AI in film” means generating whole scenes from a prompt is calibrating against the most legally and creatively fraught use, and will either over-fear the technology or chase the wrong tool. The mundane, high-value uses — cleanup, set extension, rig removal — are where most studios that adopt generative tooling actually land first, because they reduce labor-hours on work nobody enjoys doing by hand. Shipping Into the Pipeline Incrementally The second failure mode, after LLM-only framing, is waiting for a single tool launch. Generative film tooling does not arrive as one product; it arrives as a sequence of pipeline integrations, each of which has to produce packageable value on its own or it will not survive a production schedule. A de-aging step that works for one show, a cleanup pass that ships in one season, an upscaling stage that lands in conform — each is a deliverable, not a milestone toward some monolithic launch. We structure delivery so every milestone produces something the pipeline can use, rather than betting a season on a single integration that lands all at once. That is partly a project-management choice and partly a risk choice: a generative step that proves itself on one sequence can be hardened and rolled wider; a step that fails has cost one sequence, not a release window. The 60/30/10 framing some productions use for budget allocation — roughly sixty percent to the core, thirty to supporting work, ten held for contingency — maps onto this well, because incremental generative integration is exactly the kind of work that belongs in the contingency-and-supporting bands first, where a failure does not threaten the core schedule. FAQ How is AI being used in filmmaking? Across the whole production surface, not just writing. LLMs assist the writers’ room with coverage and dialogue variants; diffusion models handle concept frames, inpainting, set extension, and rig removal; video-generation models address temporal cleanup, crowd replication, and de-aging. Most of the labor-hour savings land in the post-production pipeline, not on the page. What is the 60/30/10 rule in filmmaking? It is a budget-allocation heuristic — roughly sixty percent to the core production, thirty to supporting work, and ten held for contingency. It maps usefully onto generative-AI adoption: incremental, unproven generative integrations belong in the supporting and contingency bands first, where a failed step does not threaten the core schedule. Has AI been used in any movies, and what movies contain AI? Yes, routinely and mostly invisibly. De-aging, voice restoration, background cleanup, and upscaling have used machine-learning tools for years across mainstream releases. The visible, contested cases — synthetic performances and fully generated shots — are a small slice of a much larger quiet adoption inside the post pipeline. Which generative-AI tools are studios using for VFX and post-production today? Diffusion models conditioned on plates, depth, and matte channels for inpainting, set extension, and rig removal; video-generation models with temporal attention for cleanup, upscaling, and crowd work; and identity-conditioned diffusion for de-aging. These run on frameworks like PyTorch with runtimes such as TensorRT because they must execute at production resolution across thousands of frames. How do diffusion and video-generation models fit into a film post-production pipeline? The constraint is conditioning and temporal consistency, not generation. Models are conditioned on the existing plate, depth, optical flow, and mattes so output locks to the shot rather than being invented from a prompt, and video models add temporal attention so cleaned or extended regions stay stable across the cut. Otherwise flicker turns a cost saving into a reshoot. What are the controversies and risks of using AI in the film industry? The fraught cases — synthetic performances, voice cloning, fully generated scenes — raise consent, rights, and creative-displacement concerns and are the focus of most public debate. They are also a narrow slice of actual use; calibrating an entire AI strategy against the most contested case leads teams to either over-fear the technology or chase the wrong tool while ignoring the high-value cleanup and post-pipeline uses. If you take one thing from the surface table above, let it be the question you ask before scoping any film-production AI work: which pipeline stage is labor-bound, and which model family — text, diffusion, or video — actually operates on it? Answer that honestly and the LLM-only default falls away on its own. A generative-AI feasibility assessment is the structured way to put that question to your own pipeline before committing a schedule to it.