LinkedIn video 10 to 60 fps: conform a 120 fps phone clip

LinkedIn Page video must run between 10 and 60 frames per second. Phone slow motion at 120 or 240 fps is over the line, and an 8 fps timelapse is under it. The fix with Sume is to read fps from video inspect, then send video trim in exact mode with output.fps set to 24, 25, 30 or 60. Those four values are the only ones the field accepts, so the conform target is always one of them.

The rule and the arithmetic

Both LinkedIn pages read on 2026-10-08, the Pages specification and the troubleshooting page, give the same frame rate range: 10 to 60 fps. The ratios to a legal rate are plain division, shown below.

Probe, then conform

Video inspect with frames: false returns fps as a number or null. If it is above 60 or below 10, queue a trim that covers the whole clip. The output object is exact-only and the docs show it with width, height and fps together, so send all three: width and height between 256 and 2160, and the frame rate from the allowed list. Use the probed width and height if you want the frame size unchanged, and scale the longer side down if it is above 2160.

{
  "video_url": "https://media.sume.com/artifacts/artf_demo/slowmo-120.mp4",
  "start": 0,
  "duration": 12,
  "precision": "exact",
  "output": { "width": 1080, "height": 1920, "fps": 60 }
}

What the conform does to motion

The conform keeps the duration of the clip. A 120 fps clip written as 60 fps therefore plays at the same speed with half the frames, which is the "keep 1 in 2" row in the table. It does not slow the footage down or speed it up. If you shot at 120 fps to slow the clip in an editor, do that edit first and export at a legal frame rate, because Sume has no slow-motion option. Probe the result and look at stills from video frames before you publish.

Mixed clips in a Timeline

If you assemble several clips, Timeline's output.fps takes 24, 25, 30 or 60, and omitting it makes the render follow the longest video source. When a source differs from the output rate, the job repeats or drops a frame every few frames and reports output_fps_resamples_sources. That is the same operation as the conform above, applied once to the whole master, and the warning is how you find out it happened. Set output.fps explicitly to a value from the table above and the warning tells you which sources were resampled.

Limits

The trim source can be up to 1,800 seconds and the output up to 900, and each trim is $0.02 at the public rate. Sume does not publish to LinkedIn. After the conform, probe the new file once more and confirm fps is inside 10 to 60 before you upload.