Clipchamp free captions and silence removal vs a scripted cut list

If one person edits one video by hand, Clipchamp's free plan is the cheaper answer; a scripted Sume cut list wins only when the same edit repeats from a queue. Clipchamp's pricing page (read 2026-10-03) lists 1080p export, AI subtitles and silence removal in the free plan, and 4K as a premium feature through Microsoft 365. The page did not state per-job prices, an API or a length limit in the text read, so this post does not compare those.

Reels now run to 3 minutes, as Metricool reported (read 2026-10-03), and Instagram's First Draft is reported to cut pauses from clips automatically. Free in-editor pause removal is the same idea inside a desktop-style editor. What changes with Sume is where the cut decision lives: in a file you control.

What the Clipchamp page says

The pricing page lists a free plan with 1080p export, a premium tier that adds 4K export through Microsoft 365, and editor features including AI subtitles and silence removal. It did not state an API, a maximum video length or per-export prices in what was read, so none of those are claimed here.

What a scripted cut list costs on Sume

The Sume side is a pipeline of small, priced jobs. Video inspect returns sentence segments and silence-split seconds with the transcript adding $0.01 per audio minute on top of the probe's Modal compute, for a source up to 1800 seconds. Your code picks the ranges to keep. Each range is a video trim at $0.02, and a Timeline 1.0 render at $0.10 per output minute, rounded up, joins the trimmed clips.

The calculator below prices the trim-and-join route. The numbers are the repo's fixed prices, not measured timings.

def sume_cost(output_minutes, silent_cuts=1):
    """Each kept range is a trim at $0.02; Timeline joins at $0.10 per output minute."""
    import math
    return round(silent_cuts * 0.02 + 0.10 * math.ceil(output_minutes), 2)

for out_min, cuts in ((1, 8), (3, 20), (5, 30)):
    print(f"{out_min} min output, {cuts} kept ranges: ${sume_cost(out_min, cuts):.2f}")

Worked examples

Take a 10-minute talk you want as a 3-minute Reel. Inspect's transcript is $0.10 for 10 audio minutes, plus a small compute charge. If your code keeps 20 ranges, that is 20 trims at $0.02, which is $0.40, plus a join at $0.30. The total is about $0.80 before that compute charge. The same task in Clipchamp's free plan is a manual pass in the editor with the silence tool and costs nothing in dollars, but it costs your time and cannot run from a queue.

Now a team that publishes 40 of these a month. The Sume route is about $32 and runs unattended once the cut logic is written. The editor route is 40 sessions. If 5 minutes of review is the floor for each, that is over three hours, and the honest comparison is $32 against that time.

A third case is where a pause is not the cut you want. Silence removal removes gaps; it does not know that a sentence repeats or that an aside is off-topic. With inspect segments you can drop a segment by its text, which a threshold tool cannot do. That is the case for scripting even at low volume.

What Sume does and does not do here

• Sume does not offer a timeline editor or preview; you inspect results by reading the returned artifacts.
• Sume does not remove silence with one switch. You choose the ranges from inspect output and cut them.
• Sume does give you silence-split seconds and sentence segments from one inspect job, so the cut list is evidence-based.
• Sume bills per job and the free /check routes validate a request without charge.

What to do

If you edit a few videos a week, open Clipchamp and use its free silence removal. If you have a queue, run inspect on one sample, write the keep/drop rule against its segments, and price the batch with the calculator before you submit anything.

Start small: run one real video through the free editor, time yourself, and then price the same video with the calculator. The gap between the two is the number you are really deciding on.