YouTube Shorts Over 60 Seconds: Why a Music Claim Blocks the Video
A YouTube Short longer than one minute with an active copyright claim is blocked worldwide. What that means for music choices, with Sume's Music Router noted.
The short answer
YouTube's help page says a Short over one minute with an active copyright claim of any type, including manual claims, is blocked globally, is not playable or recommended, and is not eligible for monetization (read 2026-10-09). Under one minute, a claim does not trigger that global block. So if you want a Short between 60 seconds and 3 minutes, the music is the highest-risk part of it.
What the rule changes in a workflow
The practical result is a choice made at the edit, not at upload. For a 59-second Short a claimed track may still limit reach or revenue; for a 61-second Short the same claim blocks the video worldwide. Decide the length first, then decide how careful the audio source must be.
Sume's Music Router (POST /v1/music-router/generate, default sume/music-auto, with Lyria 3.5 as the engine today) makes a track from a prompt at a flat $0.125 per generation. Docs do not say that generated music can never receive a claim, and nothing in them promises a result either way. Treat any track, generated or licensed, as something to check before a long Short.
| Short length | Active copyright claim | Result per YouTube |
|---|---|---|
| Up to 60 seconds | Yes | The page's global block applies only to Shorts over one minute |
| Over 60 seconds | Yes, any type including manual | Blocked globally; not playable or recommended; no monetization |
| Over 60 seconds | No | Normal |
A safer assembly
Build the video in Timeline 1.0 with the music as the audio spine: audio.url is the track and audio.duration_seconds is the final length (1 to 1800). The render is $0.10 per started minute, so a 61-second Short bills as 2 minutes and a 60-second Short as 1. If you are right at the border, trim to 60 seconds and save the $0.10 as well as the risk.
Keep a record of where every audio element came from: generated with which prompt and job id, or licensed with which license. Upload with the same record at hand, in case a claim must be disputed.
This is a rule of one platform on one date. Read the page again before each campaign, because the thresholds are YouTube's to change. Nothing here is legal advice; if a claim lands, YouTube's own dispute flow is the place to resolve it, and your record of where the audio came from is what you bring to it. For work with clients, put the audio source in the delivery note so the person who uploads the Short knows what to defend.
- Docs say Music Router rejects a
durationfield; put the length in the prompt, such as "a 45-second track". - Voiceover has its own rights: only use a voice you are allowed to use.
- YouTube's page also covers Shorts up to 3 minutes and square or vertical shapes; read it before you plan a length.
Sources
Related posts
More in Use cases
- Silent captioned Reel: drop the audio first, burn with words
To burn captions on a Reel with no sound, run STT first, trim with audio drop, then send your own words: $0.02 + $0.01 + $0.20 = $0.23.
- Six Nano Banana 2.1 start frames, six Wan 3.0 clips: a 3-min Short
Six 9:16 Nano Banana 2.1 stills ($0.60 at 1K) feed six 30 s Wan 3.0 jobs as first frames: $23.40 at 720p for a 180-second Short, with Timeline.
- Six podcast ad-read variants at 500 characters: TTS cost and tags
Six 500-character ad reads cost $0.1425 on Sume TTS ($0.02375 each). Tag each take with the metadata field and one Idempotency-Key per variant.
- A 60-second Short as twenty 3-second Omni cuts: $7.50 at 720p
Twenty 3-second Omni Flash 1.1 clips at 720p cost $7.50 and at 1080p $11.25, the same as six 10 s clips. Twenty slots pass 12, so Timeline chunks the render.
Written by Sume