LinkedIn video ads need under 30 fps: render at 24 or 25 on Sume
LinkedIn's spec says frame rate must be less than 30 fps. Sume Timeline and trim accept 24, 25, 30 or 60, so only 24 and 25 fit. How to set it and check it.

For a LinkedIn video ad, pick 24 or 25 fps in Sume. LinkedIn's help page lists frame rate as "Less than 30 FPS", which read literally excludes 30. Sume's Timeline output.fps and trim output.fps accept 24, 25, 30 and 60, so 24 and 25 are the two values that satisfy the rule. A 30 fps render is the common default, and it is the one to avoid here.
Spec and setting side by side
The LinkedIn column is from the vendor page. The Sume column is from the Timeline and trim docs.
| LinkedIn rule | LinkedIn value | Sume setting |
|---|---|---|
| Frame rate | Less than 30 FPS | output.fps 24 or 25 |
| Container and codec | MP4; H.264 or VP8 | Timeline returns MP4; trim exact uses libx264 yuv420p |
| Length | 3 seconds to 30 minutes | Timeline output 1 to 1800 s; trim output 0.2 to 900 s |
| File size | 75 KB to 500 MB | Not set or reported by Sume |
| Audio | AAC or MPEG4 | Trim exact remuxes kept audio as AAC |
Steps
- Read the source rate with
video_inspectandframes: false, which returns the probe without stills. - If you make a new clip from a longer one, send
output: {"fps": 24}withprecision: "exact"to trim. The docs sayoutputis exact only. - If you assemble several clips, set
output.fpsto 24 or 25 on the Timeline render. Without it, the render follows the sources, and a 30 fps source gives 30. - Read
warnings[]foroutput_fps_resamples_sources. It means some source was repeated or dropped frames to match, which can show as judder.
Pick 24 when the footage is cinematic or came from a video model at 24 fps. Pick 25 when you shot it in a 25 fps region. Converting from 30 to either one drops frames, so check a motion-heavy shot after you render.
Reading the rule carefully
LinkedIn's wording is "Less than 30 FPS". A plain reading says 29.97 passes and 30 does not, but Sume offers no fractional output rate, so the practical choices are 24 and 25. If your source is 30 fps, you can still use it: set the output to 24 or 25 and let the job drop frames, or pick a different master.
When you convert 30 to 25, one frame in six is dropped, which is usually less visible than converting to 24 on fast pans. For a talking-head clip it makes little difference. For a product turntable, look at the result before you commit a budget to the whole set.
If you generated the clip with a Sume video model, check the model's frame rate in the video router doc first. If it already comes at 24 fps, keep 24 and avoid any resample.
What Sume does not do
Sume does not validate a file against LinkedIn's rules or submit it to Campaign Manager. It also has no documented 29.97 or other fractional output option. Check the final file's frame rate, size and codecs before you upload.
Sources
Related posts
More in Media tools
- LinkedIn ratios 1:1, 4:5, 9:16: Sume video-filter crop fractions
LinkedIn lists 16:9, 1:1, 4:5 and 9:16 video. Centered crop fractions for a 16:9 or 9:16 source, plus a short Python function that prints the video-filter ops.
- Lyria prompt section markers: [0:00-0:30] Intro on Sume Music
Sume Music has no duration field. You shape a track with section markers like [0:00-0:30] Intro and a stated length in the prompt itself.
- MAI-Voice 24 kHz 160 kbps MP3 vs Sume TTS 44.1 kHz 128 kbps: mixing
Microsoft's MAI-Voice example saves 24 kHz 160 kbps mono MP3; Sume TTS defaults to 44.1 kHz 128 kbps MP3 or WAV. What the numbers mean for mixing and file size.
- Meta feed sound is optional but recommended: add a ducked music bed
Meta says captions and sound are optional but recommended on Facebook Feed video. Add a music bed under a voice with Sume Timeline soundtrack and duck_db.
Written by Sume