A LITTLE MORE KNOW-HOW.

Review AI-generated video disclosure before scheduling

By Aaron Colbry, founder of SocialRoster · Updated 2026-10-31

Review YouTube AI-disclosure requirements and SocialRoster’s synthetic-media flag. Check realistic altered content and verify the actual uploaded video.

New SocialRoster plans schedule YouTube only. Use the YouTube checklist below for new workflows. Notes about other providers apply only to existing legacy connections and do not offer new integrations.

An AI-generated flag in a scheduler is not proof that a native disclosure was sent or that a visible label appears. Review the content, the destination’s current requirements and the actual publishing route before scheduling. This is product guidance, not legal advice or a guarantee of policy compliance.

This guide was updated for the YouTube-only product on October 30, 2026. The current YouTube disclosure help was checked again on that date; dated legacy-platform sources below retain their original check dates. Platform requirements and labeling behavior can change. TikTok connecting, scheduling and publishing are Coming soon.

What SocialRoster currently sends

For YouTube uploads marked AI-made, SocialRoster sends the synthetic-media disclosure flag in the upload metadata.

• YouTube: when the post’s is_aigc flag is true, SocialRoster sends status.containsSyntheticMedia: true in its upload metadata. When the flag is false, this field is omitted. YouTube documents the field as a way to disclose realistic altered or synthetic content. Verify the uploaded video’s settings and presentation; the flag alone is not a guarantee of a visible label.
• Legacy Instagram Reels connections only: the current publisher sends the video, caption and Reel settings, but does not send an AI-disclosure parameter from is_aigc. Checking the app’s flag does not establish native Instagram disclosure.
• Legacy Facebook Page Reels connections only: the current publisher sends the video, title and description, but does not send an AI-disclosure parameter from is_aigc. Checking the app’s flag does not establish native Facebook disclosure.
• TikTok: unavailable in SocialRoster. Legacy flag handling does not enable its connection, scheduling or publishing.

For existing legacy accounts, if Instagram or Facebook content requires a native disclosure, use the platform’s native publishing tools or another independently verified workflow that provides the required disclosure before publishing. Do not rely on a caption note or SocialRoster’s checkbox as a substitute for a required native control. Pause the affected post if you cannot verify a suitable route.

Review the content against each destination’s guidance

Review the finished video against the destination’s current disclosure guidance and record what was generated or altered.

Keep a record of what was generated or altered: imagery, speech, music, events and depictions of real people. Then consult each destination’s current guidance. One record can support that review, but one universal exemption list cannot replace the platform-specific decision.

YouTube’s current guidance calls for disclosure of realistic generated or meaningfully altered content, with examples including fabricated events or actions and AI-generated music. It distinguishes these from minor aesthetic edits and some production assistance, such as caption creation. These are YouTube examples, not blanket exemptions for every destination. See source 1.

Meta describes labels based on recognized industry signals or people’s disclosure of generated content. That does not mean every editing tool preserves those signals, or that SocialRoster’s current Instagram and Facebook payloads provide native disclosure. Check the applicable Meta guidance and available native controls for your content. See source 3.

A review-first scheduling checklist

Watch the final export, check the applicable guidance and review the saved disclosure choice before scheduling.

1. Watch the final export and record which elements were generated or meaningfully altered. Do not decide from a filename alone.
2. Check the requirements for each intended destination, including any requirements outside this general product guide.
3. For a YouTube upload that needs the supported disclosure, set SocialRoster’s AI-generated flag and review it on the saved post. A bulk setting is appropriate only when it accurately describes every selected item.
4. For Instagram or Facebook content needing native disclosure, choose a native or independently verified supported publishing route instead of assuming the SocialRoster flag is transmitted.
5. Review captions and any explanatory wording separately. Clear wording can provide context, but does not replace a required native disclosure.
6. After publishing, inspect the destination and its current settings. A queued job, successful upload or checked box is not proof of visible labeling or compliance.

If a disclosure or label looks wrong

Compare the intended disclosure, saved flag and actual YouTube result when a label appears wrong.

• Compare the intended disclosure, saved post flag and the actual destination. For Instagram and Facebook, remember the current SocialRoster publisher does not send that flag as a native disclosure.
• Consult the platform’s current help and available account controls before correcting a published item. Do not assume every label can be edited or removed, or that a comment is an adequate correction.
• Do not repeat the upload blindly: inspect the existing published result first and avoid creating duplicates.
• Do not infer that a label caused a change in reach. YouTube says disclosure alone does not limit audience or monetization eligibility; no cross-network performance guarantee follows from that statement.

Keep the publishing decision separate from the content decision

Review disclosure settings for each publishing decision even when the source video already has a provenance record.

An accurate provenance record helps you review reuse, but it does not automatically transfer platform settings to a new post. Recheck each destination and publishing route when reusing a video. If the required disclosure cannot be verified, hold that publication rather than treating a scheduler’s local flag as completion.

Questions

Does SocialRoster’s AI-generated flag guarantee a visible label everywhere?

No. SocialRoster currently sends YouTube’s status.containsSyntheticMedia field when is_aigc is true, but its Instagram and Facebook publishers do not send an AI-disclosure parameter. Check the destination and use a native or independently verified workflow wherever required disclosure is not supported.

Does ordinary AI-assisted editing always require disclosure?

Requirements depend on the destination and the nature of the change. YouTube distinguishes minor edits and some production assistance from realistic generated or meaningfully altered content. Check current platform guidance rather than applying a universal exemption.

Is a caption note enough on its own?

Do not treat a caption note as a substitute for a required native disclosure. Use the appropriate platform control or a verified publishing route and check the result.

Related guides

• Check your YouTube queue before publishing
• Schedule YouTube Shorts and verify their visibility
• A YouTube scheduler for faceless channels
• Your AI workflow. Your YouTube publishing queue.

Open the scheduler to put this into practice, or return to the resources hub.