How to Make Short Clips from Long Videos with AI
Learn how to submit one supported YouTube video, Twitch or Kick VOD or live-channel link, or a conditionally enabled account upload and review short-clip candidates when available.
When a job returns candidates, you review the source context and preview before deciding what is worth keeping.
Choose one supported source you can use
The public link workflow accepts an individual YouTube video link plus supported Twitch and Kick VOD or live-channel links. A separate approved-account video-upload path is conditional on its storage and safety checks being ready. A link or file identifies one source job; it does not grant permission to use the material.
Individual YouTube video
Use one standard watch, youtu.be share, or Shorts link. Channel pages and playlists are not accepted as one clipping request.
Twitch or Kick VOD
Use one Twitch or Kick VOD link to identify an archived broadcast you are authorized to process.
Twitch or Kick live channel
Use a supported live-channel link for a one-time capture job when that source is available. The selected capture window does not claim to observe the full broadcast.
Conditional approved-account upload
When approved-account upload support is enabled and its storage and safety checks are ready, an approved account can select an MP4, MOV, or WebM video. Browser validation is preliminary; media and safety checks can still reject the selection before processing.
How the AI clipping workflow works
1. Choose one source
Start with a supported source you have the rights and permission to process and publish.
2. Add the source
Submit a recognized link or, when enabled for your approved account, select a supported video file. A recognized link starts validation; an enabled upload starts browser validation before media and safety checks. Those checks decide whether the source can proceed.
3. Prepare candidates
When the job returns candidates, Klip Farm prepares candidate moments and short-form previews. Source audio, structure, availability, and editorial quality affect the result.
4. Read the context
When selection details are available, use them alongside the actual moment to review the opening, flow, value, and payoff.
5. Check the output
Review captions when included, chosen framing, context, and boundaries before making an editorial decision.
6. Keep only what fits
An approval credit is used only when you keep a clip. Rejected candidates and re-edits are not billable.
How to read a recorded score
When a score is recorded, it is a 0–100 review signal. Hook, flow, and value score details may be absent, and the score itself can also be unavailable. It is not a promise of views or performance. Use any available signal alongside the actual preview, context, captions, and framing.
What to review before you keep a clip
Review the actual moment rather than relying on one score. A useful candidate should preserve the source's meaning and work for the audience you intend to reach.
- The opening gives a viewer enough context to understand why the moment matters.
- The excerpt reaches a useful point or payoff without changing the source's meaning.
- The candidate starts and ends at boundaries that make sense on their own.
- When captions are present, the spoken words and names are correct.
- The chosen framing keeps the speaker or needed visual context in view.
- The clip still fits your audience, channel, and editorial judgment.
What happens after approval
Approving a clip uses one available approval credit. That approval queues a clean, watermark-free final render; it does not publish the clip.
Final output is asynchronous
The final render completes asynchronously. The approved clip can remain queued or rendering until that output is ready.
Confirmed failure returns the credit
If the final render fails, the approval credit is returned once the failure is confirmed, and the clip resets for review. Re-edits do not create a second approval charge.
Publishing stays separate
Publishing requires its own connected destination, permissions, and activation checks after the final output is complete.
Current workflow boundaries
These limits are part of the getting-started decision, not fine print after a job begins.
- Creating an account requests approval-gated beta access; approval is required before using the workflow.
- A recognized source can still be unavailable, and a source may produce no usable candidate.
- Candidate selection supports review; it does not replace your editorial decision.
- Adding a source does not publish it by itself. Publishing setup is a separate gated workflow.
- You must have the rights and permission needed to process and publish the source material.
- Processing time varies with the source, format, availability, and checks required for the job.
Continue with one real source.
Request beta access, then review any candidates returned and keep only the moments that pass your review.