Before choosing coverage, use the free local moodboard maker to give your character, lighting and location references clear roles.
If the full narrative still needs explaining, use the film treatment guide with an original complete story and free editor before moving into detailed coverage or timing.
What is a script breakdown
A script breakdown is the production inventory of a screenplay, organised scene by scene. It connects what happens on the page to what must be available to make the scene: people, location, objects, clothing, sound and any special requirements. It can support scheduling and budgeting, but a list of elements is not itself a schedule or a cost estimate.
For an AI film or short drama, the same inventory helps you decide which references to approve before generating takes. A character who appears in three scenes needs a consistent identity. An important ticket needs a readable design. A key passed between characters needs a tracked position. Recording those decisions early gives you something concrete to compare with the returned footage.
StudioBinder’s breakdown guide describes the scene-level production process. Our workflow below applies it to a small original screenplay and gives you a local worksheet. The examples are planning material, not a claim that a model has filmed the script or maintained its continuity.
Start with the original script breakdown example
Download The Last Tram original screenplay. It has two scenes: an archive at night and a tram stop at dawn. Mara leaves Niko a mustard ticket reading PLATFORM 4. A cobalt key also matters to the exchange. The second scene changes location and light while keeping the two main characters and their wardrobe.
Press Load reviewed example above to see a filled planning sheet. The first scene contains a silent night porter in the action. Because the porter never has a dialogue cue, the initial speaker detector does not list them. The reviewed example adds the porter manually. That distinction is central to a useful breakdown: speaking cues are evidence of some cast, not a complete cast list.
The source also leaves a small continuity question. Mara slides the ticket toward Niko in the archive, while the key is in Mara’s hand at the tram stop. The sheet records that the final key position in scene one still needs a decision. A production note should expose that gap so the director can resolve it. It should not silently invent an offscreen transfer and present it as something the writer specified.
Use a script breakdown format that supports decisions
| Field | What to record | The Last Tram example |
|---|---|---|
| Scene number and heading | A stable identifier and source heading | 12A and the archive at night |
| Location and story time | The setting and intended time of day | Archive, night |
| Cast | Speaking and silent characters, plus background needs | Mara, Niko and the silent porter |
| Props | Objects used by the action and exact visible text | Mustard ticket reading PLATFORM 4 and cobalt key |
| Wardrobe | Approved clothes and scene-specific changes | Coral jacket, teal coat and gray raincoat |
| Sound and effects | Dialogue, ambience, offscreen cues and special work | Clock ticking, then an offscreen tram bell |
| Continuity | Positions and states that must agree across shots | Ticket in Niko’s right hand in scene two |
| Scene brief | The next production decision | Establish geography before separate dialogue coverage |
This compact script breakdown form combines several departments into editable notes. A larger live-action production may need separate extras, makeup, vehicles, animals, stunts, set dressing and equipment fields. Add those columns to the CSV when they apply. Leaving an irrelevant category empty is reasonable; leaving an important requirement unreviewed is a different problem.
Use consistent names throughout your sheet. If the same object is called blue key in one row and cobalt key in another, decide whether those labels refer to one asset. In a generated production, assign the accepted reference file a stable name too. A descriptive prompt alone is not a reference inventory.
How to break down a script in seven steps
- Read the entire current draft before tagging the first scene.
- Check the headings and preserve existing scene numbers.
- Create one sheet for each scene.
- Record explicit requirements from action and dialogue.
- Add implied requirements as review notes, separating them from source facts.
- Reconcile recurring cast, wardrobe, props and sound across the story.
- Export a dated revision and use it to plan shots, assets and production work.
Read once for the story and again for requirements. An actor can mention a tram without a tram appearing in frame. A bell can be an offscreen sound rather than a visible vehicle. In The Last Tram, the source specifies a bell beyond the frame; automatically adding a detailed tram model would change the planned work. Ask what the audience must actually see or hear.
Keep the approved draft beside the sheet. A rewrite can add a silent character, remove a prop or change day to night while leaving the main dialogue intact. If you only compare speaker names, you can miss the expensive change. After any revision, inspect the scenes whose requirements changed and check the adjacent continuity as well.
Try the free script breakdown sheet above
Paste plain text into Script text, then choose Build sheet and replace edits. The tool recognises conventional scene-heading prefixes including INT, EXT, EST, INT/EXT, INT./EXT and I/E when a dot or space follows the prefix. It also recognises a single leading period for a forced heading. Keep a blank line before and after each heading. Existing scene numbers inside hash marks are retained.
The official Fountain syntax defines a much larger screenplay format. This worksheet implements a small subset, not a full Fountain reader. It does not interpret notes, boneyards, dual dialogue, sections or every forced character cue. Remove excluded passages before pasting, and inspect the source shown under every detected scene. PDFs and Final Draft files need a plain-text export first.
Uppercase lines followed by text may be suggested as speakers. Uppercase action can resemble a cue, and silent characters can be missed. Correct those suggestions before relying on them. Location and time are split from the heading as a starting point; unusual headings may need manual correction. The tool does not infer props, wardrobe or sound from prose.
You can work on up to 30 scenes and 50,000 characters per sheet. If you change the source after building a sheet, exports are disabled until you rebuild. Rebuilding replaces your field edits, as the button states. Download the existing version first if you need it. Work stays in the open page and is lost on refresh, so export before leaving.
Download a script breakdown template and filled form
- Blank CSV script breakdown template
- Filled original script breakdown example
- Original two-scene screenplay
- Reviewed example scene briefs
Open the CSV in your spreadsheet software and keep one row per scene. Duplicate the blank row as needed and add department columns for your production. The browser tool’s CSV export preserves multiline notes and quotes. Text beginning with a spreadsheet formula prefix is escaped as text, which may leave an apostrophe visible in some importers. Inspect the imported sheet before sharing it with collaborators.
The filled example is a reference for how to record decisions, not a universal list of production requirements. Its effects field says none specified in source. That does not certify that no effects work will be needed for a chosen execution. A director might later request rain, a moving background or a composited tram; each would require a new note and a revised plan.
Turn the breakdown into an AI cinema workflow
First group the recurring assets. Approve Mara and Niko as separate character references, choose the coral jacket and teal coat, and prepare the ticket and key. Make a location reference for each setting. If the selected generation workflow supports those references, use the accepted files; otherwise, record the limitation and inspect the output carefully.
Next build the visual coverage. The archive scene might need a wide view, two complementary dialogue views and an insert of the ticket. Those are shot-list decisions made after the scene inventory. Use the free shot list maker to keep edit positions and camera setup groups in one downloadable plan. Use the shot reverse shot planner for dialogue geography and the AI storyboard guide for frame planning. Try the animatic maker to test an editorial rhythm before generating final takes.
A proposed brief for scene 12B could read: Establish the dawn tram stop with the accepted Mara and Niko references. Keep Niko’s teal coat and Mara’s coral jacket. Show the mustard ticket in Niko’s right hand and the cobalt key in Mara’s left palm. Preserve PLATFORM 4 on the ticket where it is meant to be readable. Do not add a visible tram merely because the sound cue is present.
That is an untested creative brief, not a model payload or a guarantee. In Clout AI Cinema, choose the currently supported image and video workflow, then review the actual result against the sheet. Check hands, object ownership, exact text and wardrobe across cuts. Regenerate or edit the failing shot rather than accepting continuity because the prompt requested it. For episodes, continue to the AI short drama workflow.
Script breakdown versus shot list and script coverage
The breakdown asks what the scene requires. A shot list asks how the camera will cover it. A storyboard sketches those views, and an animatic tests their sequence and timing. Script coverage usually evaluates the screenplay’s story and development prospects. These documents can inform one another, but substituting a plot summary for a production inventory leaves practical work hidden.
An AI script breakdown service may help propose elements, but test its omissions on the current draft. Check silent characters, implied objects, offscreen sound and recurring wardrobe. Ask whether its scene IDs survive revisions and whether its export remains editable. This free worksheet uses deterministic text rules instead of inference, making its limits inspectable while leaving production decisions to you.
Do not confuse page eighths with running time
Page eighths describe the extent of scenes on a consistently paginated screenplay. They are useful production notation, not a reliable duration extracted from a pasted paragraph. Scriptation’s breakdown overview discusses scene elements and page eighths within a production workflow. This tool deliberately leaves page length, shoot days, render credits and runtime uncalculated.
Once your draft is properly formatted, add the appropriate page measurements in your production software. Budget and schedule with the people responsible for the work. For generated scenes, estimate costs from the actual selected model, supported duration, output settings and revision plan. A two-scene script can require many takes; a neat sheet makes those decisions easier to track, but it cannot promise a finished film at a fixed cost.
