X Premium 125-minute Post video vs Sume 900-second trim output

Post video on X runs up to 125 minutes and 16 GB for Premium or verified accounts, against 20 minutes and 8 GB for everyone else. One Sume video-trim call outputs at most 900 seconds (15 minutes), so a trim reaches 15 of a default account's 20 minutes and never the Premium ceiling.

X entitlements are from its changelog and Media best practices page, read 2026-10-01; the page says limits follow the posting user, not your API plan. Sume caps are from Video trim.

Which runtimes fit where?

The table converts the 125-minute headline into planning rows. Runtimes in the first column are examples; the caps are as written by X and Sume.

How big can the file be?

Premium raises the Post video size cap from 8 GB to 16 GB, and POST /2/media/upload/initialize accepts total_bytes up to 16 GB. Sume's trim does not take a size or bitrate field, so for very long files check the byte size of the finished clip before you start an upload.

What is Sume's ceiling on length?

Trim reads one Sume-hosted source of up to 1800 seconds (30 minutes) and returns between 0.2 and 900 seconds as a new MP4. Even the longest accepted source is far below 125 minutes, so Sume trim is a tool for hooks and cutdowns rather than for feature-length Premium uploads.

What should I plan around?

Decide who posts first, since the cap belongs to that account. For a default account, cut to 900 seconds or less and you are inside X's limit with room to spare. For a Premium account with longer material, keep that file outside Sume trim. See the error-handling side in the 403 post.