LinkedIn Page video: 10 or 15 minutes, and is MOV allowed?

If you publish video to a LinkedIn Page, plan for the stricter of two numbers: MP4, 10 minutes or less. LinkedIn's own help pages disagree. The Pages specification says the duration range is 3 seconds to 10 minutes and that AVI, QuickTime and MOV are no longer accepted. The troubleshooting page, read on the same day, lists MOV as accepted and gives a 15-minute maximum. A third page, for Service Pages, allows MOV and under 30 minutes.

You cannot tell from outside which page matches the uploader you will hit, so build to the intersection. That means an MP4 file, 3 seconds to 10 minutes, 75 KB to 5 GB. This post shows the three pages side by side and the Sume calls that get a longer or odd-format source inside that window.

What the three pages say

All figures below are as printed on each page when read on 2026-10-08. They are the vendor's numbers, not Sume's. LinkedIn may fix the inconsistency at any time, so reread the page before a large batch.

Build to the intersection

Only one combination passes every row: an MP4 container, longer than 3 seconds, shorter than 10 minutes, under 5 GB, with a frame rate of 10 to 60 fps and a ratio between 1:2.4 and 2.4:1.

Start by reading what you have. Sume's video inspect returns a probe with container, duration_seconds, size_bytes, fps, width, height and the codecs, without re-encoding the clip. Send frames: false if you only want the probe. The clip must already be on media.sume.com, so import it first through POST /v1/media-imports.

• Container is not mp4: re-encode through video trim in exact mode, which writes an MP4 (libx264, yuv420p).
• Duration is over 600 seconds: cut it with video trim, using start and duration.
• Size is over 5 GB: cut shorter or split; Sume exposes no bitrate field.

Cutting to under 10 minutes

Video trim takes one start and one of end or duration, and the output can be 0.2 to 900 seconds. The source can be up to 1,800 seconds. So a 25-minute webinar recording (1,500 s) fits the source limit, and three 500-second cuts each sit under LinkedIn's 600-second line with room for a title card.

Exact precision is the default and re-encodes for a frame-accurate cut. Keyframe precision copies streams and can start up to a GOP early, so re-base against actual_start_seconds. A stream copy keeps the source container's codecs, so use exact whenever you are converting format.

curl -X POST https://api.sume.com/v1/video-trim \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: li-webinar-part-1" \
  -d '{
    "video_url": "https://media.sume.com/artifacts/artf_demo/webinar.mp4",
    "start": 0,
    "duration": 500,
    "precision": "exact"
  }'

What this does not settle

Sume does not call LinkedIn and cannot tell you which uploader your Page will meet. It does not publish to LinkedIn from these tools either. Treat the table as a pre-flight list: probe, cut, probe the result, then upload by hand or through your own LinkedIn integration. Each trim is a $0.02 job at the public rate, and GET /v1/catalog shows the live price.