# Make an AI short film and check it against a $200 budget

> Plan a multi-shot AI film in Claude, make Nano Banana Pro and Seedance 2.0 shots in Luma, test their actual files in Resolve, and check the finished film's full cost.

By BIGCHANGE.AI Editorial

Published: 2026-10-24T21:49:02.473Z
Updated: 2026-10-24T21:49:02.473Z
Canonical: https://bigchange.ai/blog/make-ai-short-film-verify-full-cost-under-200-guide

![Conceptual charcoal illustration of an empty editing suite with a wall-mounted display showing five joined abstract shot thumbnails and an audio track above a physical editing console.](https://bigchange.ai/api/media/file/ai-short-film-multishot-edit-hero-v3.png)
AI-generated conceptual illustration by BIG CHANGE. No actual film, provider interface, playback, rights check or under-$200 result is depicted.

A short AI video clip is a useful ingredient, but it is not a finished film. This guide takes an owned story through planning in Claude, a visual bible and generated shots in Luma, and a complete edit and export in DaVinci Resolve. The cost test covers the finished film, including subscriptions, failed attempts, rights and fees. A plan below $200 is only a forecast; the final claim needs the film, permissions and actual receipts.

BIG CHANGE has checked the current product documentation, not run these accounts, generated shots, imported a Seedance file or measured a film's cost. The first paid clip therefore doubles as a compatibility test before you spend on the rest.

## The big change

**What:** Luma's current Agents board can hold the scene references and generated media for a multi-shot production, with Nano Banana Pro images feeding Seedance 2.0 image-to-video clips. **How:** Make and test one clip, inspect its real file, then build the remaining shots and finish the edit in Resolve. **Why:** The first-file test exposes codec or import trouble while most generation spend is still uncommitted. The film qualifies as under $200 only after a fixed, all-in USD calculation using actual charges. Luma's [Seedance guide](https://lumalabs.ai/learning-center/articles/seedance-2.0-complete-guide) describes short outputs, usually four to 15 seconds, so a multi-shot film needs an edit; it does not establish the codec of your downloaded file.

## Before you pay for a shot

You need a story concept you own or have permission to use, cleared references and rights for any likeness, logo, voice, music or sound effect you intend to upload or distribute. Write down the intended audience, approximate runtime, shot count, aspect ratio and 720p or 1080p target. Save the licenses and consent alongside the script. If recognizable realistic faces run into Seedance's restrictions, revise the concept or use permitted stylized or non-identifiable characters. Do not evade a provider block.

Check access in your actual accounts: paid Claude with Cowork and Projects; a Luma App plan that exposes **Nano Banana Pro** and **Seedance 2.0 image-to-video** with the rights required for your intended use; and DaVinci Resolve **21.1 free** on Windows 10 Creators Update or later for the media route below. This guide uses Luma's current **Agents board**. Its controls and model availability may change. If either named model, the necessary commercial permission or a downloadable video file is missing, record a hold rather than substituting another model.

Set one **USD all-in budget basis before the first charge**. For a Claude or Luma plan newly required for this film, count its entire first paid billing period. For a required plan already active, count a monthly allocation from its real invoice: the monthly invoice amount, or the annual invoice divided by 12. Fix those allocations in the record now even if the project adds no subscription charge. Add estimated paid top-ups and overages, rights-cleared assets, software if required, taxes, card and transaction fees, FX fees and a bounded retry reserve. Track bundled-credit consumption, but do not count those credits as another cash charge after allocating the plan. Include every rejected or failed paid attempt.

Use the account's displayed quote for each model, duration and resolution. Public credit tables and unrelated API prices cannot tell you your actual bill. For each non-USD item, record the native amount, currency, dated issuer or processor USD rate (or named rate source), conversion and expected fees. Use the same conversion method when reconciling the actual transaction and its realized rate. An unknown mandatory price, allocation, tax or conversion rate is a budget hold.

Copy this record and fill it with your own quotes; the empty fields are deliberate:

```text
Film / budget approval date:
New required plan, full first period, USD:
Existing required plan, invoice and monthly allocation, USD:
Forecast paid top-ups / overages, USD:
Rights, assets and required software, USD:
Tax, card, transaction and FX fees, USD:
Bounded retry reserve, USD:
Preflight all-in total, USD:               (must be < 200)
Non-USD quote / currency / dated rate source / converted USD:
Per-shot ID / model / displayed quote / attempts / credits / charge / accepted:
Before each paid attempt: 200 - (committed all-in USD + remaining mandatory estimated work + reserved retries) = USD margin:
Final actual all-in total, same basis, USD:
Rights and consent checked by / date:
Film export filename / full playback checked by / date:
Verdict: complete film and known rights/receipts with total < 200, or HOLD and reason
```

Proceed with a paid attempt only while that recalculated margin remains **positive**. A projected excess calls for a shorter or simpler approved plan, a larger budget, or a hold. Changing to an incremental-cash calculation after production would answer a different question.

## 1. Turn the owned story into a shot plan

In [Claude Cowork](https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork), create a [Project](https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork) for the film and supply only the brief and files you are authorized to process there. Ask for a script with a beginning, development and ending; a numbered scene and shot list; intended seconds per shot; necessary dialogue or narration; reference and sound needs; and a cost worksheet. This is planning material. Read it against the real story and permissions, cut unsupported facts, and approve each shot ID and duration yourself. Save the checked script and list locally. Do not ask Claude to invent provider rates or certify that a film exists.

## 2. Make a Luma visual bible and one image

Create a film board in [Luma Agents](https://lumalabs.ai/learning-center/articles/welcome-to-luma-agents). Organize the approved shot IDs with frames and notes for aspect ratio, palette and lighting, character silhouette and wardrobe, location anchors and framing. Upload only cleared references. [Luma's reference guide](https://lumalabs.ai/learning-center/articles/how-to-use-references-properly) describes controls that guide consistency; you still need to inspect every result.

In the board's [image tool](https://lumalabs.ai/learning-hub/luma-toolbar-guide-tools-shortcuts-workflow-tips), explicitly select **Nano Banana Pro**. Make only the minimum budgeted character or location reference sheet and the image for the first shot. Compare the image with the approved bible, check subject, wardrobe and setting, then save it with its shot ID. Leave every other paid shot image until the video-file test passes.

## 3. Generate and test one Seedance clip

Select **Seedance 2.0 image-to-video** in Luma's video tool. Supply the approved first-shot image in its explicit `@Image` reference role and write one focused motion, action or camera instruction. Before Generate, confirm the displayed model, image/reference limits, duration, aspect ratio, 720p or 1080p resolution and account-specific credit quote. Budget one four-to-15-second clip and record the displayed charge. If the result fails or a response is uncertain, inspect the job and credit history before a bounded retry so that you do not pay for an unseen duplicate.

Watch the first clip for the intended beat, artifacts, identity drift and prohibited content. Save its prompt, source image, model, duration, consumed credits and actual charge whether you accept it or reject it. **Do not buy the remaining images or clips yet.**

Download the original first clip as `first-shot-original.<actual extension>` and keep it untouched. The Seedance guide's MP4/MOV description concerns *video inputs*; it does not promise your output container or codec. Use the official [ffprobe](https://www.ffmpeg.org/ffprobe.html) utility on the actual download, saving its JSON:

```sh
ffprobe -v error -show_entries format=format_name,duration:stream=index,codec_type,codec_name,profile,pix_fmt,width,height,r_frame_rate,avg_frame_rate,sample_rate,channels -of json "first-shot-original.<actual extension>"
```

Record container, video codec and profile, pixel format and bit depth, dimensions, nominal and average frame rate, audio codec and channels, and duration. A filename extension proves none of them. Compare the result with Blackmagic's [Resolve 21.1 supported codec matrix](https://documents.blackmagicdesign.com/SupportNotes/DaVinci_Resolve_21_Supported_Codec_List.pdf), specifically the Windows 10 **free** rows. The September 2026 matrix lists H.264 in MP4 for 8-bit OS-supported profiles for decode and encode, and embedded AAC in MP4 under Windows audio where supported. The installed Windows decoder still matters.

If the real file matches that route, import the **original** in Resolve's Media page or media pool. Make a 720p or 1080p timeline at the inspected frame rate and play the full clip, checking picture and any audio. A compatible table row without an actual import and full playback is insufficient.

If its container, codec or profile is unsupported, or it imports without usable picture or audio, keep the original and use a separate conversion only if your installed FFmpeg can decode its real streams and has the required encoders. [FFmpeg's codec documentation](https://www.ffmpeg.org/ffmpeg-codecs.html) covers `libx264` and AAC; check your build's available decoders and encoders or its actual error. This command refuses to overwrite a file and creates a newly named H.264 8-bit 4:2:0/AAC MP4:

```sh
ffmpeg -n -i "first-shot-original.<actual extension>" -map 0:v:0 -map 0:a:0? -c:v libx264 -pix_fmt yuv420p -crf 18 -preset medium -c:a aac -b:a 192k -movflags +faststart "first-shot-resolve.mp4"
```

Probe the conversion, import it and play it all the way through in Resolve. Compare its duration, framing, motion, sound and colors with the untouched original. Retain both identities by shot ID. Renaming a file extension does not convert it. If decoding or conversion fails, or Resolve still cannot play the result, **hold before paying for any other shot**.

## 4. Generate the remaining shots, then finish the film

After the first-file gate passes, produce the remaining budgeted **Nano Banana Pro** shot images against the visual bible. For each approved image, generate its planned **Seedance 2.0 image-to-video** clip with a focused `@Image` motion prompt. Recalculate the same all-in USD margin **before every paid image or video attempt**. Review story beat, motion, identity, continuity and rights; inspect job history before retrying. Download and probe each accepted file, then import it using the tested original or conversion route. Preserve paired originals and conversions by shot ID.

In Resolve 21.1 free, put the shots in approved script order and trim them into a complete story. Add titles or captions where needed. Bring in separately cleared sound, mix speech, music and effects in Fairlight, and use Color for shot continuity. Blackmagic's [Resolve overview](https://www.blackmagicdesign.com/products/davinciresolve) and [training](https://www.blackmagicdesign.com/products/davinciresolve/training) document those work areas; they do not verify this particular production.

In Deliver, choose an **MP4 container, H.264 video with an 8-bit OS-supported profile, timeline-matched 720p or 1080p resolution and frame rate, and AAC audio where the installed Windows controls offer it**. Render to a new local filename. If those options are absent, check the current installed-build matrix and hold instead of quietly using an unsupported export or a Studio-only feature. Probe the final render and watch it from first frame to last. Check that the whole script is present, cuts and color are coherent, dialogue and other sound are intelligible, credits are correct and the distribution rights cover the finished work.

## 5. Reconcile the actual under-$200 result

Fill in the final record on the **same preapproved USD all-in basis**: full first paid periods for newly required plans or the fixed monthly equivalent of existing required plans; paid top-ups and overages; rejected generations and retries; assets, licenses and any required software; tax, transaction and realized FX charges. Keep bundled credits as a consumption log without billing them twice. Attach invoices, account charge history, licenses, the shot log and the export/playback record. You may calculate incremental cash separately, but it does not replace this test.

Mark **pass** only if the entire accepted multi-shot film exists and plays, rights and consent are cleared, all final charges are known, and the fixed-basis total is **strictly less than US$200**. At $200, above it, or with an unknown charge, blocked right or failed export, record the precise hold. Neither a cost forecast nor one good clip establishes the outcome.

## Sources & further reading

- [Claude Cowork setup](https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork) and [Cowork Projects](https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork) describe the planning workspace. Check your own paid access and file permissions.
- [Luma Agents boards](https://lumalabs.ai/learning-center/articles/welcome-to-luma-agents), [image/video toolbar](https://lumalabs.ai/learning-hub/luma-toolbar-guide-tools-shortcuts-workflow-tips), [references](https://lumalabs.ai/learning-center/articles/how-to-use-references-properly) and the [Seedance 2.0 guide](https://lumalabs.ai/learning-center/articles/seedance-2.0-complete-guide) document the board, model selection and short clips. [Plans](https://lumalabs.ai/app), [pricing](https://lumalabs.ai/pricing) and [terms](https://lumalabs.ai/legal/terms-of-service) still require an account-specific price and rights check.
- Blackmagic's [Resolve 21.1 codec matrix](https://documents.blackmagicdesign.com/SupportNotes/DaVinci_Resolve_21_Supported_Codec_List.pdf), [product page](https://www.blackmagicdesign.com/products/davinciresolve) and [training](https://www.blackmagicdesign.com/products/davinciresolve/training) define the documented Windows free-edition route. Test your actual files and installed controls.
- The [ffprobe](https://www.ffmpeg.org/ffprobe.html), [FFmpeg](https://www.ffmpeg.org/ffmpeg.html), [codec](https://www.ffmpeg.org/ffmpeg-codecs.html) and [format](https://www.ffmpeg.org/ffmpeg-formats.html) manuals support metadata inspection and the optional local conversion. They do not establish the codec of a Seedance download.

## Sources

- [Get started with Claude Cowork](https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork) — Paid planning access and local-file task context; not a film run.
- [Organize your tasks with projects in Claude Cowork](https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork) — Project context and file organization.
- [Welcome to Luma Agents](https://lumalabs.ai/learning-center/articles/welcome-to-luma-agents) — Board organization for scenes, concepts and references.
- [Luma toolbar guide](https://lumalabs.ai/learning-hub/luma-toolbar-guide-tools-shortcuts-workflow-tips) — Image/video tools and Nano Banana Pro selection.
- [Seedance 2.0 complete guide](https://lumalabs.ai/learning-center/articles/seedance-2.0-complete-guide) — Image reference roles and short output; input MP4/MOV wording is not an output promise.
- [Luma App plans and pricing](https://lumalabs.ai/app) — Plan/model access; account checkout controls final cost.
- [Luma terms of service](https://lumalabs.ai/legal/terms-of-service) — Input and output rights and paid commercial-use conditions; not copyright clearance.
- [DaVinci Resolve 21 supported codec list](https://documents.blackmagicdesign.com/SupportNotes/DaVinci_Resolve_21_Supported_Codec_List.pdf) — September 2026 Resolve 21.1 Windows free H.264 MP4 8-bit OS-supported rows and embedded AAC; actual file test still required.
- [ffprobe documentation](https://www.ffmpeg.org/ffprobe.html) — Actual stream and format metadata inspection.
- [FFmpeg codecs](https://www.ffmpeg.org/ffmpeg-codecs.html) — Optional local libx264 and AAC conversion, subject to installed build and real input decode.