# Build brief — a focused alternative to CapCut

> **Verdict:** Partly, if you narrow it · **Buildability:** 45/100 · **Category:** Audio Video
> **Source:** https://www.canitbevibecoded.com/capcut
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from CapCut. Verify current pricing and capabilities before acting.

## Context

**CapCut** — Consumer video editor with templates, captions, effects, and AI tools. It currently costs $19.99/mo.

A captioner/trimmer/exporter is buildable, but CapCut's value is mobile editing polish, effects/templates, asset library, TikTok workflow, and real-time rendering.

This brief describes a focused, single-operator replacement for the part of CapCut that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Upload video, auto-caption, cut/trim, add simple templates/effects, and export social aspect ratios.

- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Ffmpeg.
- Speech-to-text.
- Video rendering queue.
- Client editor.
- Storage.

### Data and integrations

- Optional image/video AI APIs.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a video captioning and clipping tool to replace CapCut Pro.
Requirements:

- A CLI: Python + ffmpeg + faster-whisper. clip input.mp4 transcribes and
  burns captions; --cut 0:12-0:58 trims first; a folder as input batches
  every video in it.
- Captions from word-level timestamps, grouped 3-5 words per line, rendered
  as ASS subtitles: bold font, white fill, black outline, centered in the
  lower third, burned in with ffmpeg.
- style.json controls the look in one place: font, size, colors, margin.
- Aspect exports: --format 9x16 (blur-pad or center-crop, chosen by flag),
  1x1, and 16x9, with bitrate defaults sane for phone playback.
- --srt writes the plain subtitle file next to the video so I can fix
  typos, then --from-srt re-burns without re-transcribing.
- Output is <name>-<format>.mp4 beside the input; never overwrite a source
  file.
- Fully local and offline after the model download: no accounts, no uploads,
  no telemetry. Use the GPU when present, CPU still works.
- Out of scope: a timeline editor, effects and templates, and a music
  library; CapCut's editor polish is the product. This is for talking-head
  clips.
- README: installing ffmpeg and choosing a whisper model size.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Mobile app quality.
- Effects/templates.
- Asset library.
- Timeline editor.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
- Licensed content and distribution rights are not reproducible with an LLM.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: medium. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Shotcut](https://github.com/mltframework/shotcut) — Open-source video editor; powerful prior art but not mobile/template-first like CapCut

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/capcut