AI Act closed-loop film previs: where preview ends, output begins
The EU FAQ puts closed-loop film production outside marking scope unless the output is final. Avatar preview stills are never captioned; the final MP4 can be.

The Commission's Article 50 FAQ lists, among outputs outside the marking obligation, outputs used only in closed-loop industrial and product development environments, for example film production, unless they are the final output. So internal previs that never leaves the production loop sits differently from a file you publish. This is a plain reading of the FAQ, not legal advice.
The FAQ text is from the Commission's Article 50 FAQ, read 2026-10-01. Below is how Sume's docs separate previews from final output.
What does the FAQ actually say about film production?
It says the Guidelines on Transparency of AI-Generated Content clarify that some outputs fall outside scope, and one entry is outputs that are only used in closed loop industrial and product development environments, for example for film production, unless they are the final output.
The word only and the clause unless they are the final output carry the weight. A frame reviewed internally and discarded is one thing; the same frame in the delivered cut is another. The FAQ does not define a pipeline stage for you.
Where does Sume separate preview from final?
In Avatar videos, optional captions burns styles into the clean final MP4 after generation, and preview stills are never captioned. So burned-in text only lands on the final file, not on the stills you review.
That is a statement about captions, not about legal status. If your label is a burned-in caption, you add it at the final render and your preview stills stay clean.
| Artifact | What the docs say |
|---|---|
| Avatar preview still | Never captioned |
| Final avatar MP4 | captions burns styles in after generation |
| Frames from a clip | video_frames extracts stills at times you name, per Video frames; unbilled |
| Clip inspection | video_inspect returns probe facts, stills and optional STT |
How do I review a clip without making a new deliverable?
Video frames takes one workspace clip and returns durable image artifacts at the times you name, leaving the source untouched. Video inspect reads one media.sume.com clip and returns probe facts, stills and optional transcription; it never produces an MP4.
Both are review tools. Neither changes the final file you would publish.
What should I decide before shipping?
Decide, per asset, whether it is only in the closed production loop or will be seen by the public. Anything that becomes the final output follows the normal labelling path; see what creators must do under Article 50. Keep the label step on the final render and ask your own adviser about edge cases.
Sources
Related posts
More in Use cases
- Making AI videos for clients: are you an AI Act deployer?
The Commission FAQ treats freelance or regular paid use of an AI system as professional, making you a deployer. Personal use is excluded. Not legal advice.
- AI game trailer generator: 4-30 s shots joined in Timeline
Build a game trailer from separate seedance-2.5 shots of 4 to 30 seconds, then join them in Timeline 1.0 with fade or wipe transitions between slots.
- Amazon Responsive eCommerce Creative: assets to supply
Amazon's REC builds ads from lifestyle images, video, logos and copy. Prepare lifestyle stills with reference-guided edits and short clips.
- Android Automotive Play screenshots: 800x1280 and 1024x768
Play wants 2 portrait (800x1280) and 2 landscape (1024x768) Automotive screenshots of generic system UI. Both fit the ChatGPT Image 2.5 custom-size limits.
Written by Sume