Pinterest video ads start at 4 seconds, Sume trim allows 0.2: gate it
Pinterest's standard video ad minimum is 4 seconds and 15 minutes max, but video trim accepts 0.2 to 900 seconds. Add a length gate before you upload.

Pinterest's standard video ad spec says a minimum of 4 seconds and a maximum of 15 minutes, and it recommends 6 to 15 seconds. Sume's video trim accepts durations from 0.2 to 900 seconds, which means it will happily make a 3-second file that Pinterest's spec does not allow. Put a length check between the trim and the upload, using duration_seconds from a video inspect probe.
The two ranges side by side
The 900 seconds on the Sume side is exactly 15 minutes, so the upper ends match.
| Item | Value |
|---|---|
| Pinterest standard video, minimum | 4 seconds |
| Pinterest standard video, maximum | 15 minutes (900 seconds) |
| Pinterest recommended | 6 to 15 seconds |
| Sume trim duration | 0.2 to 900 seconds |
| Sume trim source length | Up to 1,800 seconds |
| Pinterest max file size | 2 GB |
Where the mismatch shows up
A trim is exact to the frame when precision is exact, so a request for 3 seconds returns a file of about 3 seconds. The API does not know your target platform, so it does not reject it. The same applies to a timeline render, which outputs the length of its audio spine. A short render still bills a whole minute, so 3 seconds costs $0.10, the same as 60 seconds (Sume catalog, read 2026-10-08).
Below the minimum is the failure to watch for, but the long end has its own arithmetic. At 2 GB over 900 seconds the average bitrate ceiling is 16,000 megabits / 900 = 17.8 Mbps, so the file-size cap rarely binds on a 15-minute ad.
A gate that works
After each trim or render, call video inspect with frames false and read duration_seconds. Accept the file only if the value is at least 4 and at most 900, and prefer a value from 6 to 15 for ads that are meant to autoplay. The probe is billed by compute, not a fixed price, so run it once per output, not per frame.
If a clip is too short, do not stretch it. Pick a longer source range and trim again at $0.02, or join two scenes in a timeline render. If it is too long, trim to the recommended range and keep the long version for a different placement.
Keep the gate in code or in a spreadsheet column, whichever your team uses, but keep it separate from the trim step. A gate that lives in the trim step gets bypassed when someone cuts a file by hand. A gate on the file that is about to be uploaded catches both.
If you batch many clips, probe each output once and record duration_seconds next to the file name. A column of numbers is easier to review than a folder of files, and the 4-second floor and 900-second ceiling become a simple filter.
- Trim: $0.02 per job.
- Timeline: $0.10 per output minute, rounded up.
- Probe fields: duration_seconds, width, height, fps, video_codec, size_bytes.
Sources
Related posts
More in Media tools
- Podcast video episode over 30 minutes: Sume's 1800-second source limit
Sume video trim, audio detach and video inspect all cap a source clip at 1,800 seconds. A 45-minute podcast video must be split before you import it.
- Read probe width, height and rotation before 9:16 crop fractions
A 9:16 crop needs width = 9/16 x H / W: 0.3164 for 1920x1080 but 0.5625 for a square clip. Read the probe first, and swap W and H if it reports rotation.
- Reels ads ban edit lists and special boxes: check your MP4
Meta's Reels ad spec bars edit lists and special boxes and asks for H.264, fixed frame rate and stereo AAC. What a Sume probe can and cannot show.
- Reframe 16:9 to 9:16 before you burn captions, not after
Crop a 16:9 clip to 9:16 with video-filter (width 0.3164, x 0.3418), then caption. Order trim, crop, caption: $0.02 + $0.02 + $0.20 = $0.24.
Written by Sume