A useful AI film breakdown explains the creative intention, shows a meaningful before-and-after comparison, names the work done outside generation, and records what changed. Use evidence from your own project rather than treating a tool list as an explanation. This is an editorial guide, not a Milan AI Festival submission requirement.
Start with a scene and a decision
Choose a short sequence you can explain in detail. A complete production diary can become difficult to follow; one scene gives the reader a concrete place to begin. Describe what the scene needed to do in the film. Did it establish a relationship, introduce a place, or interrupt a rhythm? Keep the description specific enough that someone can assess the result.
For example, a fictional scene might need a character to feel isolated without using dialogue. The breakdown would then focus on framing, movement, duration, and sound choices that supported that intention. This is an illustrative exercise, not a description of a real festival film. Replace it with the actual intention behind your own sequence.
Show an early version beside the selected version
Keep an early image, clip, or edit that reveals a meaningful change. Pick something that helps explain your decisions, rather than simply choosing the least successful output to make the final version look impressive. Label both versions so the audience can tell whether they are looking at generated material, a working edit, or a finished scene.
Write two or three sentences about the difference. Perhaps the first image communicated the wrong mood, or a camera movement distracted from the subject. Say what you changed and why. If several aspects changed at once, acknowledge that you cannot attribute the improvement to one prompt revision alone. A clear account of uncertainty is more useful than an oversimplified success story.
Separate generation from the rest of the work
Describe the role of generated material within the project. Then account for selection, shot assembly, compositing, colour, titles, and any filmed or photographed elements. A reader should be able to understand where each kind of work enters the sequence, even if they have never used your tools.
A compact production table can help: element, origin, revision, and contribution to the final scene. For instance, a background might be generated and then cropped; a voice might be performed by a collaborator; the pacing might come from several rounds of editing. Only include categories that apply to your work, and credit collaborators for their actual contributions.
Explain sound and timing with the same care
An image comparison leaves out a large part of a film’s experience. Explain how sound enters or leaves the scene, why you held a shot for a particular length, and what the cut changes for the viewer. If the piece is silent, describe that as a creative choice when it was one.
Try showing the sequence with and without its final sound as a private review exercise. Write down what becomes easier or harder to understand. The purpose is not to prove that one version is objectively better. It is to identify which parts of the experience depend on sound, and to make those decisions visible in your explanation.
Keep a small, readable evidence pack
Save the selected working versions, a short decision log, relevant credits, and the final excerpt. Give files names that distinguish stages, and record dates while you work. If you share prompts or settings, explain which version they belong to. A prompt pasted without the corresponding result offers little evidence about what happened.
Before publishing, check that you have permission to share the material and any collaborator contributions. Remove private information and unpublished work that is not yours to disclose. A breakdown does not need to expose every internal file to be useful: a few carefully chosen examples can communicate the process clearly.
Finish with what you would change next
End with a limitation or an unresolved question. Perhaps a transition still feels abrupt, an expression is hard to read, or the sequence relies too heavily on its explanation. Naming that limitation makes the breakdown a starting point for discussion and gives other makers something specific to respond to.
Use this structure for your own portfolio, an artist conversation, or an editorial pitch. Check each event’s official rules before using it as submission material. Milan AI Festival has not yet announced a programme or submission requirements. Explore our five questions for discussing AI-assisted creativity, or follow the festival information page for confirmed announcements.