OpenCut: The Open-Source CapCut Alternative
OpenCut-app/OpenCut
OpenCut is a from-scratch rewrite of its own video editor, and right now it's a roadmap, not an app — the README lists an Editor API, a Rust core, and an MCP server as things still coming. Reach for opencut-classic if you need a working free video editor today; reach for this repository only if you want to track the plugin-first architecture before it ships.
Introducing OpenCut
OpenCut is a free, open-source video editor project GitHub describes as the open-source CapCut alternative, aimed at web, desktop, and mobile. The code in this repository is currently being rewritten from scratch around a Rust core, so the working editor most people mean by OpenCut still lives in the separate opencut-classic repo.
Key Features Planned for OpenCut
- ✓An Editor API for programmatic control over the editing pipeline.
- ✓A plugin-first architecture meant to support first-class third-party plugins.
- ✓One codebase — built on a Rust core — targeting desktop, mobile, and browser.
- ✓An MCP server so AI agents can drive the editor.
- ✓A headless mode for automation and batch rendering without a UI.
- ✓A scripting tab built directly into the editor interface.
Developer Setup for OpenCut
Development against this repo starts with installing proto (https://moonrepo.dev/proto): on Linux, macOS, or WSL run `bash <(curl -fsSL https://moonrepo.dev/install/proto.sh)`; on Windows PowerShell run `irm https://moonrepo.dev/install/proto.ps1 | iex` (if shims fail, run `Set-ExecutionPolicy -Scope CurrentUser RemoteSigned` first). From the repo root, `proto use` installs the tool versions pinned in .prototools. Then `moon run web:dev` starts the web app on localhost:5173, `moon run api:dev` starts the API on localhost:8787, and `moon run desktop:dev` covers the desktop build (see apps/desktop/README.md). The README is explicit that outside contributions aren't accepted yet while the architecture is still being designed, so this setup is for following along, not shipping a PR.
Strengths
- ✓MIT-licensed, so the code — and eventually the plugin API — can be reused or embedded without copyleft strings attached.
- ✓The architecture is genuinely different from most editors: an Editor API, headless rendering, and an MCP server are being designed in from the start rather than bolted on later.
- ✓The team isn't abandoning the working app while they rebuild — opencut-classic stays available and is what opencut.app serves.
- ✓A sponsor (fal.ai) is already listed for generative image, video, and audio models, so the plugin ecosystem has at least one committed integration target.
Understanding OpenCut's Development Phase
- △The repository is a rewrite in progress — the feature list in the README is a roadmap, not shipped functionality, so there's no working editor to evaluate here yet.
- △Outside contributions aren't accepted yet; the README says the architecture is still being designed, so pull requests aren't the way in — Discord and issues are.
- △The actual usable video editor (opencut-classic) lives in a separate repository, which splits documentation, issues, and history across two projects.
- △No release version, timeline, or changelog is given for when the Editor API, MCP server, or plugin system will land.
Exploring Open-Source Video Editors
Common Questions About OpenCut
OpenCut is being rewritten from the ground up, per the project's own README. The current repository has no finished editor; an Editor API, a Rust core, and an MCP server are listed as coming, not shipped.
OpenCut aims to support desktop, mobile, and browser from a single codebase built on a Rust core, according to the roadmap listed in the repository's README.
Not yet. The OpenCut README says the project isn't set up to take outside contributions while the architecture is being designed; you can join the Discord or open an issue to follow along.
OpenCut is released under the MIT license, so the code can be used, modified, and redistributed with minimal restrictions.
GitHub describes OpenCut as the open-source CapCut alternative, but the repository under active rewrite has no working editor yet, so there's no shipped feature set to compare against CapCut directly right now.
OpenCut's roadmap includes an MCP server for AI agents and a headless mode for automation and batch rendering, per the README, though these are planned rather than shipped features.
The problem it solves
Most open-source video editors bolt automation onto a GUI built for humans. OpenCut's rewrite starts from the opposite direction: an Editor API, a headless mode, and an MCP server designed so AI agents and scripts can drive editing and batch rendering without a UI in the loop at all.
Best use cases
- •Automating render pipelines — batch-rendering many clips without a UI, using the planned headless mode.
- •Building third-party plugins once the plugin-first architecture and Editor API ship.
- •Wiring AI agents into an editing workflow through the planned MCP server.
- •Editing on desktop, mobile, or in the browser from a single Rust-core codebase, once the rewrite lands.
Who should try it — and who should skip
Try this repository if you want to watch a video editor being redesigned around an Editor API, plugins, and AI-agent access from day one — join the Discord, read the code, maybe build against the API once it exists. Skip it if you need a video editor that works today: open opencut-classic (or opencut.app) instead, since this rewrite has nothing to edit with yet.