Trim pauses and reorder clips by API, like YouTube chat editing

YouTube's conversational editing trims pauses and reorders for pacing. By API: inspect the clip for free, trim ranges, then reorder slots in a Timeline spec.

4 min readSume
All posts

YouTube describes a conversational editor in Shorts and the YouTube Create app that can automatically trim pauses and reorder for better pacing. Sume has no chat editor for YouTube, but the same edit is three API calls: probe the clip with video_inspect, cut the keepers with video_trim, and reorder them as video[] slots in a Timeline spec.

Steps are from the Sume docs for Video inspect, Video trim and Timeline 1.0, read 2026-10-01.

What does each step do?

Three-step pause trim and reorder, from the Sume docs, read 2026-10-01.
StepEndpointBilling note
Look at the clipPOST /v1/video-inspectProbe and stills are unbilled
Cut each keeperPOST /v1/video-trimNew MP4 per range; precision exact or keyframe
Reorder and joinPOST /v1/timeline-1.0/renderBilled per output minute

How do I find the pauses?

Inspect returns probe facts, stills, and optional speech-to-text; it does not return typed scenes or pause marks. So you decide the ranges from the transcript and stills, or from your own analysis, and treat them as trim inputs. The worked version is remove filler words with inspect and trim.

How do I reorder segments?

Each trimmed MP4 goes into video[] with source_in 0. Order is set by start: video[0].start must be 0 and later starts must increase. A reorder means rewriting the starts so they stay increasing for the new order. If starts do not increase, or a slot overlaps past its transition, the render is refused with invalid_segment_timing or segment_overlap.

What about the audio?

Timeline needs an audio spine whose duration_seconds sets the output length, or audio.mode: "silence". Reordered speech therefore needs a spine that matches the new order, for example sliced parts in audio.parts[]. Check cost first with the unbilled plan call, then render.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume