Blog
Long-form behind the videos.No filler, real projects.
Build notes, coding lessons, and honest reviews from the projects behind each video.
Blog
Build notes, coding lessons, and honest reviews from the projects behind each video.
A free, MIT-licensed video editor with nearly 70,000 GitHub stars is aiming directly at CapCut, with ambitions that go beyond matching features to rethinking how video editing tools should work.
A free, MIT-licensed video editor with nearly 70,000 GitHub stars is aiming directly at CapCut, with ambitions that go beyond matching features to rethinking how video editing tools should work.
OpenCut is an open-source video editor that positions itself as the CapCut alternative. It is licensed under MIT, which means you can use, modify, distribute, and self-host it freely. The project targets web, desktop, and mobile from a shared Rust core, and it has attracted approximately 69,600 stars, 7,200 forks, and over 1,500 commits on GitHub as of mid-July 2026.
The project is currently in transition. OpenCut Classic is the version you can use today, offering a web-based editor experience. However, Classic is archived and no longer maintained. The main repository is being rewritten from the ground up with a new architecture built around a Rust core, an Editor API, a plugin system, an MCP server for AI agents, headless mode, and in-editor scripting.
The current Classic version runs in the browser and provides a usable editing experience. The rewrite, which is the active development focus, centers on a Rust core that feeds browser, desktop, and mobile canvases. The roadmap includes an Editor API for programmatic control, a plugin system for extensibility, and an MCP server that would allow AI agents to drive the editor directly.
The automation vision is where OpenCut gets interesting. Headless mode would enable rendering without a UI. Batch rendering could produce multiple video variants from a single project. A scripting tab inside the editor would let users write automation logic directly. Combined with MCP, an AI agent could request cuts, apply effects, and export videos programmatically.
It is important to note: the MCP server and AI agent capabilities are on the roadmap, not in the current release. The repository search found no released generative AI editor feature in the rewrite. These are stated directions, not shipped functionality.
The main repository is being rewritten from scratch and is not yet accepting external contributions while the architecture is being finalized. If you want to use OpenCut today, Classic works but is archived and unmaintained.
Free and open-source does not mean every future cloud service or integrated AI model will also be free. The current MIT-licensed, local-first promise is strong, but the project's evolution could introduce services with their own costs.
The project is not a feature-for-feature clone of CapCut. It is an open-source editor with its own architecture and roadmap. Comparing feature checklists today will show gaps; the question is whether the roadmap closes them over time.
OpenCut is worth trying if you want a free, open-source video editor that respects your data and runs on your terms. It is also worth following if you are interested in the long-term vision of automated, scriptable, AI-agent-driven video editing. If you need a polished, fully-featured editor today with every CapCut feature intact, you may need to wait.
The takeaway: OpenCut is free, open, and has a future architecture that could make it fundamentally different from CapCut rather than just a free copy. The near-70K star count shows the demand for an open video editor is real.