Can an AI-made Short be Creative Commons on YouTube?

Yes, but only if the video is yours to license and carries no Content ID claim. In the YouTube Data API the choice is one field, status.license, with two valid values: youtube (the Standard YouTube License) or creativeCommon (Creative Commons Attribution). YouTube's help page says that if there is a Content ID claim on your video, you cannot add a Creative Commons Attribution license to it.

That second rule is the one that bites a Short built with a music bed. This post walks through what the field does, what YouTube says can and cannot carry CC BY, and where Sume fits. Sume does not upload to YouTube and its docs describe no YouTube upload endpoint, so you set the field yourself when you call videos.insert. Everything about YouTube here comes from the Videos resource, the videos.insert page and the license help page, all read on 2026-10-03.

What does status.license accept?

The Videos resource lists the valid values as creativeCommon or youtube. The videos.insert page lists status.license among the fields you can set in the request body, next to status.embeddable, status.privacyStatus, status.publicStatsViewable, status.publishAt, status.selfDeclaredMadeForKids and status.containsSyntheticMedia.

The help page calls the Standard YouTube License the default for all uploads. The pages I read do not state a default for the API field, so a pipeline that cares should send status.license on every upload rather than rely on one. In Studio the setting sits under Details, then Show more, then the License dropdown, and you can change it during upload or later by editing the video.

Which videos can be licensed CC BY?

The help page limits CC BY to three kinds of material: content you originally created, content already released under a CC BY license, and public domain material. A Short assembled from your own footage, your own script and a Sume-rendered voice track fits the first category. A Short that borrows someone else's clip does not, unless that clip was itself released under CC BY or is in the public domain.

The Content ID rule is the practical risk. If a claim lands on the video, the help page says you cannot add the license. The pages I read do not say what happens to a license you already set when a claim arrives later, so check the video in Studio after the first claim window instead of assuming it holds. Shorts Content ID claims in September 2026 covers the claim side.

What does the upload body look like?

Here is the status block of a videos.insert body that sets the license explicitly, plus the other fields the insert page lets you set. Send it as the JSON part of the upload request.

{
  "snippet": {
    "title": "Episode 4: the cold open",
    "description": "Made by us. Licensed CC BY."
  },
  "status": {
    "privacyStatus": "private",
    "license": "creativeCommon",
    "selfDeclaredMadeForKids": false,
    "containsSyntheticMedia": true
  }
}

What does Sume do here?

Sume prepares the file; YouTube holds the license. A cut from Video trim returns a new MP4 on media.sume.com and leaves the source untouched. You download that artifact and upload it to YouTube with your own OAuth credentials. Sume has no say in which license you pick, and this post does not cover Sume's terms for the files it generates.

If the video shows realistic synthetic content, set status.containsSyntheticMedia in the same call, as covered in the synthetic media field on videos.insert. Because unverified API projects are limited to private uploads, see unverified API project uploads before you plan a public CC BY batch.

Checklist before setting creativeCommon

• Every clip, image and sound in the Short is yours, CC BY or public domain.
• No music from a library that can raise a Content ID claim.
• You are comfortable with others reusing the video with credit, since the help page describes reuse with title, author, source URL and license information.
• You send status.license explicitly in the request, not by default.
• You re-check the video in Studio after upload.