YouTube AI labels you cannot appeal: Veo and C2PA metadata
YouTube says labels from its own AI tools or full-AI C2PA metadata cannot be appealed, though you can update disclosure status in Studio. What it means for you.
Some YouTube AI labels are final. The YouTube blog post on AI labels, read on 2026-10-05, says that labels applied because a video was made with YouTube's own tools, such as Veo and Dream Screen, or because it carries C2PA metadata marking it as fully AI, cannot be appealed. It also says creators can update the disclosure status in YouTube Studio.
The post says YouTube has been auto-labelling significant photorealistic AI content since May 2026. So there are three ways a label can get onto your video, and they differ in what you can do about them.
Which labels you can change
| How the label got there | Can you appeal it? | What you can do |
|---|---|---|
| You disclosed in Studio | Not an appeal; it is your setting | Update the disclosure status in Studio |
| YouTube's automatic detection of photorealistic AI | The post says creators can update status in Studio | Update the disclosure status |
| Made with YouTube tools such as Veo or Dream Screen | No, cannot be appealed | Accept the label |
| C2PA metadata marks the file as fully AI | No, cannot be appealed | Remove the cause only by changing the file you upload |
The Sume angle
A clip generated through the Sume video API is not made with YouTube's tools, so the Veo row does not apply. The C2PA row might, if the file carries full-AI credentials. Sume's docs say nothing about C2PA, so I cannot say whether a Sume clip does; check the delivered file and see how YouTube treats it on a private test upload.
If you are tempted to strip metadata so YouTube does not read it, do not. Hiding the signal does not change what the video is, and the honest fix is accurate disclosure in Studio.
Practical steps
The blog post is from YouTube itself; details of Studio menus may differ from what you see. 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.
- Upload new AI clips as private or unlisted first and look at which label appears.
- If the label is wrong and not in the cannot-appeal group, update the disclosure status in Studio.
- If it is in the cannot-appeal group, accept it and plan the thumbnail and title around it.
- Keep the generator job id and the original file.
Sources
Related posts
More in Use cases
- AI B-roll on YouTube: when real places and events need the label
YouTube asks for disclosure when AI alters footage of a real event or place, or makes a realistic scene that did not occur. Four triggers, applied to B-roll.
- YouTube AI label for a prompt-made AI presenter: three cases
A Sume avatar made from a prompt that looks like a real person sits on the disclose side of YouTube's rule. Three cases, what to tick and where.
- What YouTube can do if you skip the altered-content disclosure
YouTube's page names manual labeling, content removal and Partner Program suspension for non-compliant creators. A pre-upload gate for teams shipping AI Shorts.
- YouTube B-roll batch: ten 8-second AI clips on Sume, cost and waves
Ten 8-second 16:9 B-roll clips cost $8.00 on Omni 1080p and $10 on Wan 720p. How many waves a Free, Pro or Startup plan needs to render them.
Written by Sume