[verdict][curated prompt][source: subclip.app]
Can I vibecode Subclip?
// the value is the network, the data or the infrastructure
Subclip is not a realistic vibe-coded replacement. A narrow transcript cutter is buildable, but the product is a multi-surface post-production system: ONNX models running locally in the browser, client-side and server-side Remotion rendering, cloud AI and media jobs, native macOS and iOS experiences, plus an MCP server and developer APIs. Reproducing and operating those surfaces is a platform project, not a one-shot build.
confidence: high
what it is: AI platform for clipping, transcript editing, captions, dubbing, rendering, and publishing
Buildability index · an editorial game
- Price 14 $/month weight: plus 2
- Time closest consolation build: multi-day weight: minus 1
- Category audio and video no weight
- Moat infrastructure scale · integrations · execution quality weight: minus 4
- Confidence high weight: plus 1
- What you lose 5 items weight: minus 2
- Site subclip.app (si apre in una nuova scheda) no weight
The moat outweighs the price: rebuilding this is a project, not an evening.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Build only the closest consolation: import a video, transcribe it locally, cut by editing the transcript or removing silence, style subtitles, and export an MP4 and SRT.
what you need
- Python 3.12
- FFmpeg
- faster-whisper
- desktop with enough storage for source media and renders
- GPU optional
The verdict covers Subclip's full current platform surface, not only its visible transcript editor. Creator pricing checked against the official site on 2026-08-04.
The prompt
The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.
Build me the closest honest personal substitute for Subclip, not a platform clone. Requirements:
- Use Python 3.12 + FastAPI for a localhost web app, with a plain JavaScript frontend,
FFmpeg for media work, and faster-whisper for word-level transcription.
- I can import MP4, MOV, WebM, MP3, or WAV files, see a synced transcript beside the
video preview, and click any word to seek to its timestamp.
- Deleting transcript ranges creates an undoable cut list. Detect silences longer than
500 ms and let me accept or reject each suggested cut before rendering.
- Let me edit subtitle text and timing, import or export SRT, and apply one ASS style
file with font, colors, outline, position, and words-per-line controls.
- Export MP4 in 16:9, 9:16, or 1:1 with center-crop or blur-pad. Never overwrite the
source, and show FFmpeg progress plus a useful failure message.
- Store projects as JSON under ~/SubclipDIY/projects and renders under
~/SubclipDIY/exports, with a recent-projects page and a delete-project action.
- Bind to localhost only. No accounts, uploads, telemetry, or network calls after the
faster-whisper model has been downloaded.
- Deliberately exclude ONNX models in the browser, Remotion client or server rendering,
native apps, cloud dubbing, render queues, publishing, an MCP server, and public APIs.
- Add unit tests for cut-list merging and subtitle grouping, plus one smoke test that
imports a short fixture and produces a playable MP4.
- Include a README with setup for Python and FFmpeg, model-size guidance, data paths,
supported formats, and an honest warning about CPU transcription and render speed. Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.
What you lose
- ONNX model packaging and hardware-accelerated in-browser inference
- coordinated client-side and server-side Remotion rendering
- native macOS and iOS apps and their release pipelines
- production dubbing, voice cloning, storage, and render queues
- MCP server, developer APIs, NLE exports, and publishing integrations
Why people still pay
Creators and developers pay for one maintained system that coordinates local ONNX inference, browser and server rendering, cloud dubbing and media jobs, native apps, API and MCP automation, and publishing integrations without making them operate each layer themselves.
moat: Infrastructure scale Integrations Execution quality what a moat is
hybrid local and cloud media architecture, native apps, and developer surfaces
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Lightweight Video Editor (opens in a new tab) — Open-source Electron editor with local Whisper transcription, word-level caption editing, clipping, and FFmpeg export.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.