Content ID on a Short over one minute blocks it globally: keep a cut
YouTube says a video over one minute with an active Content ID claim is blocked globally. Keep a 59-second video-trim cut of every long Short as a fallback.

The three-minute Short has a sharp edge: length decides how a claim hits it. YouTube's page says a video exceeding one minute with an active Content ID claim is blocked globally, not playable or recommended, and not eligible for monetization (read 2026-10-07). So for any Short over a minute, keep a sub-minute cut ready, which Sume's video-trim makes for $0.02.
The page's wording is "exceeding one minute". I cut to 59 seconds rather than 60 so a rounding quirk never lands on the wrong side, and I check the probe afterward.
What the page says
From YouTube's three-minute Shorts page. For Shorts under one minute it says there are no changes in limitations.
| Video length | Active Content ID claim result on the page |
|---|---|
| Exceeds one minute | blocked globally; not playable or recommended; not eligible for monetization |
| Under one minute | page says no changes in limitations |
Cut the fallback
A start: 0, duration: 59 trim keeps the opening, where the hook and the point usually sit. If your 3-minute Short's strongest minute is elsewhere, change start. The default precision: exact re-encodes with libx264 and keeps audio, so the music stays. The source can be up to 1800 s and the output up to 900 s.
curl -X POST https://api.sume.com/v1/video-trim \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: short-59s-001" \
-d '{
"video_url": "https://media.sume.com/artifacts/artf_demo/short-180s.mp4",
"start": 0,
"duration": 59
}'Confirm the length
The job result returns duration_seconds and actual_start_seconds. Use video inspect on the new artifact to confirm the probe's duration_seconds is under 60 and width is not greater than height. A trim of a vertical file stays vertical.
If the fallback does carry a claim, only the owner of the music can resolve it; the trim removes seconds, not rights.
Policy for a series
Render each long Short and its 59-second twin together, tag both artifacts, and upload only the long one first. That costs $0.02 more per episode and gives you something to swap in, if you decide to, without re-rendering anything.
When the fallback is not worth it
If a Short only works at 2 minutes, a 59-second slice is not the same video, and posting both can split your audience. The fallback earns its $0.02 where the opening minute is a complete idea.
For everything else, the better defense is upstream: know where each audio element came from before you render. The page tells you the cost of getting it wrong at length; it does not tell you how likely that is, and I have no figure to offer.
Sources
Related posts
More in Media tools
- Crop a 16:10 MacBook screen recording to 9:16: width 0.3516
A 16:10 recording needs crop width 0.3515625 for 9:16: 900x1600 at 2560x1600, but 674x1200 at 1920x1200 because 675 is odd. The request and the rounding.
- Crop a 2:1 landscape phone recording to 9:16: width 0.28125
A 2:1 (18:9) landscape clip needs width 0.28125 for 9:16: exact at 1920x960 (540x960), 606 px at 2160x1080. The offset, the rounding and the full request.
- Crop a 5:4 monitor clip to 9:16: width 0.45 and the exact sizes
A 5:4 clip crops to 9:16 with width 0.45 and x 0.275. At 1280x1024 that is 576x1024, at 1600x1280 it is 720x1280. Two sizes, one body, and why it is exact.
- Crop 16:9 to 9:16 with video filter: the fractions to send
For a 16:9 source, a centred 9:16 crop is x 0.3418, y 0, width 0.3164, height 1. One $0.02 video-filter job, checked free first. Examples for 1920x1080.
Written by Sume