Beat-aware coverage suggestions
Dialogue-heavy scenes get reverse singles; action lines trigger insert proposals. You stay in control of every row.
Shot lists should not be a spreadsheet you rebuild after every rewrite. ScreenWeaver derives coverage from scene structure and storyboard frames so size, movement, and subject stay tied to the script.
You build a shot list in a spreadsheet while the script lives in another app and boards sit in a folder. Change one scene order and three documents disagree about what scene 8 means.
AI video tools need shot-level intent: subject, framing, movement, duration. Without a list rooted in the script, you guess prompts shot by shot and burn time on unusable clips.
Department heads want clarity, not poetry. When shot rows lack scene numbers and reference frames, meetings stall on basics instead of creative decisions.
ScreenWeaver reads scene beats and optional storyboard panels to propose shot rows with size, subject, movement, and scene IDs already filled.
Edit coverage in context: add a push-in for the reveal, mark a one-er for the argument, export a list that AI video tools and a real crew can follow without translation layers.
Choose a sequence or full script. ScreenWeaver lists scenes with character count and location data to help you prioritize coverage.
The system proposes master, coverage, and insert shots based on action and dialogue density. You accept, merge, or split rows in seconds.
Link storyboard panels to shot rows so framing intent is visible to the DP, story artist, or AI video operator.
Download a production shot list or push rows into AI video generation with prompts that inherit scene and shot metadata.
Lin has twelve hours to shoot a custody confrontation in one apartment. She imports the scene, accepts a proposed master and three singles, adds a slow push for the confession beat, and attaches the approved board frames. The exported list goes to her gaffer and to an AI previz pass so everyone references scene 31, not vague thumbnail names.
Dialogue-heavy scenes get reverse singles; action lines trigger insert proposals. You stay in control of every row.
Thumbnails from your storyboard strip appear on shot rows so framing notes have a visual anchor.
Tag ECU, WS, handheld, dolly, or static per row using standard terms your crew already speaks.
Each row can export a structured prompt for AI video tools with scene ID, subject, and motion fields filled.
Without structure
With ScreenWeaver
No. ScreenWeaver can draft shot rows from script beats alone. Boards are optional references that make each row clearer for visual collaborators.
Yes. Edit size, movement, and equipment fields per row or set project defaults that match your production's naming conventions.
When scenes change, affected shot rows are flagged. You review additions, deletions, or renumbers instead of rebuilding the entire list.
CSV export includes scene numbers, shot IDs, descriptions, and estimated complexity fields you can map into scheduling tools.
Shot lists work best with scripted scenes. For documentary, import outline beats as pseudo-scenes and build coverage around interview blocks or planned B-roll.
Each row can generate a prompt package with framing, subject, movement, and duration hints plus optional board thumbnails so AI passes match your coverage plan.
AI generation is not the hard part anymore. Keeping the film coherent is. Start in ScreenWeaver and build the chain before you burn credits.
Start creating with ScreenWeaver