AI Content Disclosure Rules on Every Platform in 2026

Short answer

Most clipping work does not require an AI disclosure. YouTube's rules trigger on synthetic realism — making a real person appear to say something they did not, altering a real event, or generating a realistic scene that never happened — and explicitly exempt captions, upscaling, colour correction and AI-written scripts.

That exemption list is the part almost nobody writes about, and it covers the overwhelming majority of what an automated clipping pipeline does to a video.

Where you do need care is generated footage, cloned voices that are not your own, and the labels platforms apply automatically from embedded metadata — those you cannot remove.

Key takeaways

Why this suddenly matters to clippers

Two things converged. AI tooling moved from the edges of the editing workflow to the middle of it — reframing, captioning, dubbing, B-roll generation, thumbnail creation — and platforms shipped disclosure systems that apply labels whether or not you ask for them.

The result is a lot of anxious guessing. Creators disclose defensively on clips that need no disclosure, which is harmless but signals to viewers that the video is synthetic when it is not. Others assume nothing applies to them, which is fine right up until a generated B-roll shot of a real place trips a rule.

The useful frame is not "did I use AI" but "does the finished video misrepresent reality". Every major platform's rule is built on that distinction, and once you hold it, most of the ambiguity evaporates.

Using an AI tool is not the trigger. Producing footage a viewer would reasonably mistake for a real recording of something that did not happen is the trigger.

YouTube's three disclosure triggers

YouTube requires disclosure when altered or synthetic content is realistic — specifically, when your video (Source: YouTube Help, 2026-09):

• Makes a real person appear to say or do something they did not. A synthesised clip of a public figure endorsing a product. A face-swapped guest. A voice clone of someone other than yourself.
• Alters footage of a real event or place. Adding smoke to a real building. Removing a person from real news footage. Changing what a real location looks like in a way a viewer would read as documentary.
• Generates a realistic scene that did not occur. A photoreal shot of a street, a room, or an incident that never existed.

The word doing the work in all three is realistic. Obviously stylised, animated, or clearly unreal content does not fall under the requirement, because no viewer is being misled about what happened in the world.

Disclosure on YouTube is made at upload, and YouTube then surfaces a label on the video. Note that the label is descriptive, not punitive — a disclosed video is not demoted for being disclosed.

The exemption list: most clipping work is exempt

This is the section that should change how you feel about your pipeline. YouTube explicitly exempts the following from its disclosure requirement (Source: YouTube Help, 2026-09):

Run an ordinary clipping workflow against that table. Transcription and captions: exempt. Auto-reframe: not in the trigger list, because cropping and repositioning a real recording does not alter what happened in it. Loudness normalisation and audio cleanup: exempt. Translated captions: captioning, exempt. Dubbing in your own cloned voice: exempt.

The honest conclusion is that a clip produced from real source footage by an automated editing tool, with generated captions and no synthesised imagery, does not require a YouTube AI disclosure.

Auto-applied labels you cannot remove

Disclosure is not only something you choose. YouTube may apply a label itself — via its own creation tools, via C2PA provenance metadata embedded in the file, or via internal detection (Source: YouTube Help, 2026-09). Those labels are not creator-removable.

C2PA is the mechanism worth understanding, because it is invisible in normal use. Content credentials are written into the file by the generating tool and travel with it through re-encodes that preserve metadata. If a generated asset entered your edit three steps upstream, the resulting upload can carry provenance you never consciously added.

Separately, all video generated by Google's Veo and Flow carries a SynthID watermark, and the Gemini app can verify whether a given video was produced by Google AI. Watermarking of this kind is designed to survive ordinary editing.

The practical consequence: if you use generated footage anywhere in a clip, assume the platform can tell, and disclose rather than hoping the metadata was stripped.

Documented consequences for failing to disclose when required are label application, content removal, or suspension from the YouTube Partner Program. YouTube's own documentation confirms those consequences exist but does not publish a specific enforcement start date or a fixed strike sequence — you will see both asserted online, and neither is confirmed by the official page.

TikTok's AIGC toggle, and Meta's account-level labels

TikTok. TikTok requires creators to mark AI-generated content content using the platform's AIGC toggle at upload. That requirement is clear. What is not documented in any verified form is a tiered penalty ladder — you will find blog posts describing escalating consequences, and none of them trace to an official TikTok source. Use the toggle when your content is AI-generated; do not plan around an enforcement schedule nobody can cite.

Instagram and Meta. Meta operates two distinct layers, and conflating them causes most of the confusion:

• A per-post "AI info" label that auto-applies from C2PA and IPTC metadata, rolled out from May 2024. When both layers apply, the per-post label takes precedence.
• An account-level label, reported to have been renamed from "AI creator" to "AI-generated profile" on August 31, 2026, with distribution restrictions for AI-persona profiles that do not self-label.

The Meta details here are secondary-sourced rather than confirmed against a primary Meta policy page, so treat the account-level naming and the August 2026 date as reported rather than settled. The underlying behaviour — automatic per-post labelling driven by embedded metadata — is consistent across every account we have seen.

A decision tree for your workflow

Work through this in order. It resolves nearly every real case in under a minute.

1. Is any footage or imagery in the clip generated rather than recorded? If no, and you only transcribed, captioned, reframed, cleaned audio or colour-corrected, you are in the exempt set on YouTube. Stop here.
2. Does the clip depict a real, identifiable person saying or doing something they did not? If yes, disclose. This is the clearest trigger on every platform.
3. Does it alter real footage of a real event or place in a way a viewer would read as documentary? If yes, disclose.
4. Is there a realistic generated scene? If yes, disclose. Stylised or obviously unreal imagery does not require it.
5. Is there a cloned voice? Your own voice for dubbing is exempt on YouTube. Anyone else's is not.
6. Did any asset come from a generative tool that embeds C2PA or SynthID? Assume the platform can detect it and disclose rather than gamble.
7. Publishing to TikTok? Set the AIGC toggle if the content is AI-generated.

AutoClip's pipeline sits in step 1 for the ordinary case: it selects moments from your real source video, reframes, captions, and translates. Caption translation across 31 languages and AI dubbing across 25 are the two features worth a second look — translated captions are captioning, and dubbing in your own cloned voice is exempt, but a dub in a voice that is not yours is a different matter. Related reading: how to uniquify clips without copyright problems and AI search optimization for video creators.