File
SMF·CAPCUT
Received on
30.07.2026
Reviewed on
28.09.2026
Exhibits annexed
3
Questions
4

SMF·CAPCUT

Can a prompt replace CapCut?

Audio & video editing — short-form video editor

Almost Verdict recorded on 28.09.2026 · Verified on 30.07.2026
Price
$19.99/moSource: www.capcut.com · Checked on July 30, 2026
Per year
$239.88
Build time
A week
Votes
0 votes
YesAlmost (checked)Not yet

Exhibit tracking slip

Exhibit A The prompt
Exhibit B What you lose
Exhibit C Why people still pay: media pipeline/templates/platform ecosystem
Exhibit Q Questions

Verdict

A captioning-and-clipping CLI — transcribe, burn captions, trim, export for social formats — is a real one-sitting build on open-source tools, running fully offline after the model downloads once. What doesn't come with it is CapCut's actual product: a full mobile timeline editor, its effects and template library, and the polish that makes editing fast on a phone.

Exhibit B — What you lose

Exhibit A — The prompt

Received on30.07.2026
Build a command-line video captioning and clipping tool. Given a video file, transcribe it locally (faster-whisper or whisper.cpp — no cloud API needed) and burn in styled captions grouped a few words per line, with a config file controlling font, size, color, and position. Support trimming to a time range and exporting at common social aspect ratios (vertical, square, widescreen) with sensible default bitrates for phone playback. Write the plain subtitle file alongside the video so typos can be fixed by hand, then re-burn from the corrected file without re-transcribing. Never overwrite the source file — always write a new output file next to it. Support batch mode: point it at a folder and process every video inside.

Do not build a timeline editor, an effects or template library, or a music library — CapCut's editing polish and asset library are the actual product, and this tool is scoped to one specific job: captioned, trimmed, correctly-sized clips from a single source video, not general editing.

Opening prefills the prompt — press enter to run it.

Exhibit B — What you lose

  • B.1 the mobile timeline editor itself
  • B.2 the effects and template library
  • B.3 a growing asset library
  • B.4 platform-specific export presets and integrations
  • B.5 real-time rendering performance

Prior art

Exhibit C — Why people still pay: media pipeline/templates/platform ecosystem

Short-form editing on a phone needs to be fast, and a library of reusable effects and trends is most of what makes a clip feel current — neither is something a captioning script replicates.

Questions

Can I import my existing CapCut projects?

No — CapCut's project format is proprietary and doesn't export to anything this tool can read. You'd start from the exported video file, not the editable project.

Will it work on my phone?

No — this is a command-line tool meant to run on a computer with real processing power for transcription. CapCut's mobile-first editing is exactly the part this doesn't replace.

What does it cost to run?

Nothing — it runs fully offline on your own machine after the one-time transcription model download, with no hosting and no API key.

What's the one thing that doesn't survive the rebuild?

The editor itself. This tool captions and trims a single clip; it has no timeline, no drag-and-drop effects, and no library of trending templates — for anything beyond captions and a trim, you're back to a real video editor.

Receipt

Already built this yourself?