Courtyard Reel: One Render Into a Cinematic reel

You have one render. You want a film.

Most AI architecture animations fall apart the same way. The camera pulls back and suddenly the building has four floors instead of two. The courtyard moves. The road becomes a car park. It looks impressive for three seconds and then it stops being your project.

This playbook is the fix. It's the complete workflow I used to build a 70-second cinematic site film from a single render, with the building, the landscape and every material staying identical across fifteen shots.

What's inside

• The derivation method: how to generate every angle from your hero render's actual pixels instead of a fresh prompt, so you get the same building and not a lookalike
• The chaining technique: using the last frame of each clip as the first frame of the next, so your cuts are genuinely invisible
• Every prompt, verbatim — hero render, massing model, dusk, night, facade macro, plus all five video prompts, ready to copy and paste
• The negative prompt template that actually stops drift, and why generic "no morphing" wording does nothing
• A seven-point audit checklist that catches a wrong building before you waste money animating it
• How to get real camera movement (it comes from your keyframes, not your prompt — this one surprised me)
• Assembly: normalising, colour matching, where to cut and where to dissolve

Written from a real production, including the failures. Two continuity errors are documented as worked examples with before-and-after images, because they teach more than any warning. About a sixth of my budget went on fixing mistakes an audit would have caught. That section alone will save you more than this costs.

Who it's for: architects, visualisers and design studios who can already produce a render and want to turn it into content that moves.

What you need: Nano Banana or a similar image model, Kling 2.5 for video, FFmpeg for assembly. No coding.

24 pages, PDF, instant download.

— Nitish Jain, Xelion Labs