How to mark a Vimeo video as AI-generated: the steps for a Sume clip
Vimeo's AI label is a per-video checkbox in Settings, Content. The steps, the three cases that need it, and what to log for a Sume-generated clip.

To mark a Vimeo video as AI-generated, open the video's settings, go to the Content section, tick "Includes AI-generated content that appears real", and then choose Audio, Visuals or both. That is the path in Vimeo's how-to article, which I read on 2026-10-05. The two Vimeo help pages I read describe only this per-video setting. They do not mention an API field or a bulk option, so I would plan on doing it once per upload.
If you make clips with Sume and host them on Vimeo, the label is your step, not Sume's. Sume's video generation docs describe a job that returns a hosted clip; they say nothing about a Vimeo label or a platform flag, so nothing happens on Vimeo until you set it.
When Vimeo says to label
Vimeo's guidance names three cases: a real person shown doing or saying something they did not, a real event or location that was altered, and a lifelike scene that never happened. A Sume text-to-video clip of a realistic office, a realistic spokesperson or a photoreal street scene fits the third case. A face-swapped or voice-matched clip of a real person fits the first.
Vimeo says no label is needed for fantasy animation, obvious effects, beauty filters or noise removal. A clearly stylised cartoon explainer therefore sits outside the rule, while a photoreal product demo with a generated presenter does not.
What the label looks like
| Question | What Vimeo says |
|---|---|
| Where is the setting? | Video settings, Content section, one checkbox per video |
| What do you choose? | Audio, Visuals, or both |
| Where does viewers' label show? | Under the title and in the embedded player |
| Does labelling hurt the video? | Vimeo says it will not lower a video's rating |
| Is there an API or bulk path? | Not mentioned on either page I read |
What to keep on your side
Because the checkbox is manual, a spreadsheet beats memory when you publish many clips. For each Sume job, store the job id, the model you picked, the Vimeo URL and the date you ticked the box. Sume lets you attach your own metadata to a job; the docs say it is stored on the job and not sent to the provider, so it is a safe place for a tag such as vimeo_ai_label: audio+visuals.
One more habit: label by what the viewer would reasonably believe, not by which tool made the pixels. If a Sume clip is a plainly animated mascot, skip the box. If a viewer could take it for footage, tick it and pick the right Audio or Visuals option.
Sume's docs describe a metadata field on video, image and music jobs that Sume stores on the job and does not send to the provider. I found nothing in the docs about Sume adding, keeping or removing C2PA credentials, watermarks or platform labels, so treat that as undocumented and check the delivered file.
Sources
Related posts
More in Use cases
- Hugo: process a Sume image with Fill and a WebP output spec
Hugo reads PNG, JPEG and WebP and can write WebP itself. Save a Sume PNG into the page bundle, then use Fill to cut a 1200x630 card and output WebP.
- HVAC Seasonal Maintenance Reminder as an AI Avatar Video
A seasonal HVAC tune-up reminder rendered as a Sume avatar video: script, seconds per scene, request JSON, and cost per clip and per customer list.
- Replace headline text on a finished ad with Ideogram 4.5 on Sume
Send the finished ad as the first reference to ideogram/ideogram-v4.5 on Sume, name the new headline, omit aspect_ratio. List cost $0.03-$0.22.
- Ideogram 4.5 banner translation, then animation: $0.70 per language
Edit the text in one banner image per language with Ideogram 4.5 ($0.075), then animate it with Omni Flash 1.1 (5 s, $0.625). Python code and the cost math.
Written by Sume