OpenCut: The Open-Source CapCut Alternative (Read the Fine Print)
Ninety-three thousand stars for a free, open-source video editor positioned as the CapCut alternative — no watermarks, privacy-first, MIT licensed. That is the headline. The fine print is that the project is currently being rewritten from the ground up, which changes what you should actually download today. Honest review below.
What it is
OpenCut is a free and open-source video editor for web, desktop, and mobile. The pitch is straightforward: timeline editing, multi-track support, real-time preview, no watermarks, and local-first workflows — the core of what makes CapCut the default editor for short-form creators, without the account lock-in or the cloud dependency. It is MIT licensed, which (unlike the AGPL projects we often review) is permissive for commercial use.
The star count — 93,354 at the time of checking, created June 2025 — tells you how hungry creators are for this. CapCut's terms, pricing changes, and availability headaches have pushed a lot of people to look for an exit ramp, and OpenCut is the most-starred one.
The rewrite: what you need to know
Here is the part most coverage skips. The README states plainly: "OpenCut is being rewritten from the ground up." The new architecture promises an Editor API, first-class third-party plugins (via a plugin-first architecture), desktop/mobile/browser from one Rust core, an MCP server for AI agents, headless mode for automation and batch rendering, and a scripting tab inside the editor.
That roadmap is exciting — especially the MCP server and headless mode, which would make OpenCut scriptable inside agentic pipelines. But it means the main repository is a construction site right now. The project is explicit about what to use instead: the previous version lives at opencut-app/opencut-classic, and opencut.app still runs the classic version. The rewrite lives at new.opencut.app until it is ready to take over. The team also notes they are not set up to take outside contributions yet while the architecture is being designed.
Who should use it
- Creators wanting a CapCut exit ramp — try the classic version at opencut.app first; it is the stable one.
- Privacy-first editors — local-first workflows with no watermarks.
- Builders and automators — watch the rewrite: the Editor API, MCP server, and headless batch rendering are aimed directly at programmatic video production.
- Plugin developers — the plugin-first architecture is the long-term bet; early days, but worth tracking.
Getting started
For the classic (stable) version, head to opencut.app — it runs in the browser. For the rewrite, the repo documents a dev setup: install proto, then from the repo root:
proto use # installs the tools pinned in .prototools moon run web:dev # localhost:5173 moon run api:dev # localhost:8787 moon run desktop:dev # see apps/desktop/README.md
That is a developer setup, not an end-user install — another sign the rewrite is not yet the thing to hand to a non-technical editor.
Honest pros and cons
✅ Strengths
- MIT license — genuinely permissive, including commercial use
- Classic version is usable today in the browser
- The rewrite's roadmap (plugins, MCP, headless, scripting) is exactly what automated pipelines need
- 93k stars = massive community interest and visibility
- Sponsored by companies in the creator-tool space (e.g. fal.ai)
⚠️ Tradeoffs
- Main repo is mid-rewrite — do not expect a stable desktop/mobile editor from it today
- Classic vs rewrite split is confusing; pick deliberately
- No outside contributions accepted during the redesign
- Feature parity with CapCut (effects, templates, mobile polish) is a long road
- AI features will depend on the plugin ecosystem that does not fully exist yet
Verdict
OpenCut deserves its stars as a direction: an open, scriptable, watermark-free editing base is exactly what the creator economy needs underneath the AI generation layer. But go in with the right expectations — use the classic version for real work today, and treat the rewrite as a project to watch, not a tool to depend on. If the plugin architecture and MCP server land as described, OpenCut could become the editing layer inside agentic pipelines like the ones we build. We will revisit it when the rewrite ships.