Instagram Reels speed control 0.5x to 3x: what Sume can't retime

Instagram's Reels camera offers speed control from 0.5x slow motion to 2x or 3x fast forward, applied in the app while you record or edit. Sume does not change clip speed: video trim only cuts a range, and video filter's allowlist leaves out trim and setpts, the ffmpeg filters used to retime. If you need a speed change, do it in the Instagram app, Edits or your own editor, then bring the file back for cutting and checking.

The speed options are listed in Instagram's Reels guide, read on 2026-10-02. The Sume side is video trim and video filter.

What can Sume do with a clip's timing?

The table is a map of what the docs allow around timing, so you can see where retiming is and is not available.

Why is video filter not the answer?

Video filter accepts an allowlisted filtergraph: tone, blur, geometry, fade and internal compositing. The docs state that trim and setpts are not on the list and send range work to video trim. So a filtergraph that tries to speed up a clip is refused with invalid_filtergraph.

Changing the output frame rate on an exact trim is not a speed change either. Timeline's notes describe a frame rate that differs from the source as repeating or dropping frames, and the clip still plays at the original speed.

What can I do instead?

Pick whichever matches where the speed change is needed, in order of effort.

If the whole point is a short, fast clip, generating it at the right length is sometimes simpler than retiming. The video router takes 3 to 10 second clips at 9:16, as covered in the AI video models post.

• Apply the speed in Instagram: set it in the camera or editor, then export or post as normal.
• Apply it in Edits or another editor, export an MP4, then use Sume only to cut, check and assemble.
• Cut to the moment instead: an exact trim of 2 seconds from a long take gives you the fast beat without retiming.
• Regenerate the clip at the length you want with a video model, rather than speeding one up.

How do I check the result?

After retiming elsewhere, run a probe-only video inspect: duration_seconds should match what you expect (a 10-second clip at 2x is 5 seconds), and fps should still be inside the 23 to 60 range the Reels API accepts. A clip that ends up under 3 seconds fails the API minimum.

Sume does not retime audio either. After a speed change elsewhere, listen to the audio before you cut.

Will this change?

Nothing in the repo docs says a speed tool is planned, and this post states only what the docs list today. If you build a pipeline that needs retiming, keep that step outside Sume and treat Sume as the cut-and-check stage. Re-read the video filter allowlist when you upgrade, since it is the page that would name any new filter.

Slow motion has one more catch for Reels. A clip slowed to 0.5x has half as many frames per second of screen time unless the editor interpolates, so a 30 fps clip can fall to an effective 15 fps. Meta's API accepts 23 to 60 fps in the container, but the container rate and the look can differ, so judge the result by eye. Sume's probe reports the container fps, not how the motion looks.