Skip to content
CutSpool

Use case

Get short clips out of the recordings you already have.

Customer calls, sessions and product walkthroughs are already in the archive. Upload one and it comes back as vertical clips with captions burned in and post copy attached.

Start clipping
Source

Start with a recording you already have.

MP4, MOV or WebM, within your plan's size and length ceilings. Nothing has to be re-recorded or cut down first, and the browser sends the file straight to storage without routing it through the API.

The upload panel, with a source file staged and the run settings on the right.
Transcript

The recording is transcribed before anything is cut.

Word-level and segment-level timings are produced for the whole file. They decide where a cut can land and they time the captions in the finished clip.

The same workspace while a run is still cutting.
Candidates

Clips arrive with the copy attached.

Each candidate carries a title, a description written in the speaker's tone, three to eight hashtags and a score from 0 to 10, ordered highest first. That is what goes out with the post.

One finished clip as it appears in the list.
Output

Branded, vertical, ready to download.

Clips render vertical at 9:16, 1080 x 1920 or 720 x 1280, H.264 video and AAC audio. A logo image and a handle line can be burned into every clip in the run, and the caption preset and every field behind it are set before it starts.

The clips workspace, rendered by the app's own components with a sample run.

Sample run

What one internal review returned.

A 54-minute roadmap review, run once with the team's own framing and caption preset. Three clips came back with their titles, descriptions and hashtags already written. These are that run's figures.

Source file
q3-roadmap-review.mp4
Length
54:28
Credits charged
55
Clips returned
3
Ranges cut
4 across 3 clips
Highest score
8.5
That clip's title
We shipped the smaller version and the bigger one stopped mattering
Start clipping
The clips workspace, rendered by the app's own components with a sample run.

The parts that matter here.

AI clipping
Read
Captions
Read
Export
Read

What a run costs.

Budgeting is per recording: round its running time up to the whole minute and that is the credit cost, whatever the run returns. The 54:28 review above came to 55 credits, and a run that fails hands them straight back.

See pricing

Other recordings this works on.

Podcasts

Turn a 60-minute episode into a queue of reviewable vertical cuts.

View podcast workflow

Interviews

Find the compact answer without replaying the full recording.

View interview workflow

Webinars

Pull reusable teaching moments out of a long session.

View webinar workflow

Creator content

Get a week of short posts out of one long upload.

View creator workflow

Questions from marketing teams.

Yes, on the plans that include branding. A logo image and a handle line can be burned into every clip in a run. The logo sits above centre and the handle below the captions, in the same place on each clip.

Each clip comes back with a title, a one to three sentence description in the speaker's tone, and three to eight hashtags. You copy them out of the clip list. Nothing is scheduled or posted for you.

No. An account belongs to one person, and there are no shared workspaces and no team seats. What does carry between people is the run itself: framing, caption preset and branding are all set before a run, so two recordings put through the same settings come back matching.

For the window your plan sets, after which the file and its transcript are deleted on a sweep. Clips already rendered stay downloadable in the clip list, but can no longer be edited or re-rendered. You can delete a recording yourself at any time, but a window cannot be extended.

No. The guides are preview-only overlays for checking where each platform may cover the picture with its interface. They are never burned into the rendered clip.

Ready when the recording is

The archive is already full of clips.

Start free