OpenCut: The Open-Source CapCut Alternative in the Middle of a Rewrite (What Actually Works Today)

Last updated: November 11, 2026 · 5-minute read

97,540 stars — and the editor they belong to is being thrown away. OpenCut, the open-source CapCut alternative, is mid-rewrite: the main repository no longer contains the editor people starred, and the version you can actually edit video with today lives in a separate, archived repo. Neither fact is hidden. Both are in the README, one screen below the logo.

This is the honest split, because the gap between "most-starred open-source editor" and "editor you can use this evening" is where readers waste their time. Here is what each half of the project really is, as of November 11, 2026.

What the Main Repo Is Now

The main OpenCut repository — 97,540 stars, 9,717 forks, MIT license, created in June 2025 — opens its Status section with a plain statement: OpenCut is being rewritten from the ground up. What is promised for the rewrite:

• An Editor API
• First-class third-party plugins, from a plugin-first architecture
• Desktop, mobile, and browser from one codebase, on a Rust core
• An MCP server, so AI agents can drive the editor
• Headless mode, for automation and batch rendering
• A scripting tab inside the editor

That is an ambitious list, and today it is a list — not a feature set. The development instructions in the same README are real (a moon-based toolchain, a web dev server on port 5173, an API server on port 8787), but they are instructions for following a build in progress, not for editing your video. The contributing section says the quiet part out loud: the project is not set up to take outside contributions yet, while the architecture is being designed.

The rewrite will live at new.opencut.app until it is ready to take over. Until then, the star count measures faith in a plan.

What Actually Works Today

The previous version — the editor that earned those stars — now lives at opencut-app/opencut-classic, and opencut.app still runs it. That is the one to reach for today, in the main repo's own words.

The classic is a real, complete editor codebase: 1,567 commits, a Next.js web app, a desktop app in progress, and a Rust core for the GPU compositor, effects, and masks. Its stated reasons for existing still hold — your videos stay on your device, and the basic features CapCut paywalled stay free. You can self-host it with Docker Compose, where it serves on port 3100, or run the hosted version at opencut.app and skip the setup entirely.

One word in the classic repo's header matters more than everything else on the page: archived. GitHub marks it a public archive, and its README says it in plain text — this is the original codebase, archived and no longer maintained. The editor works; it will not get better, and bugs you find there are yours to live with or fix yourself.

TL;DR

• OpenCut's main repo (97,540 stars) is a ground-up rewrite — Editor API, plugins, Rust core, MCP server, headless mode — none of it shipped as an editor yet
• The usable editor today is opencut-classic, still served at opencut.app, and it is archived and unmaintained
• The rewrite previews at new.opencut.app; the team is not taking outside contributions yet
• MIT license on both repos — forks are legal, which is the safety net if the rewrite stalls
• Need to edit today: use the classic. Want to follow the future: watch the main repo, not the classic

How to Choose Between Them

Where It Falls Short

The honest answer: OpenCut right now is two half-answers, and the project's own pages admit both halves.

• The classic is a dead end by design. Archived means no security fixes, no format updates, no bug fixes. Every month it ages, the gap between it and current browsers, codecs, and operating systems widens.
• The rewrite has no shipped editor. A Rust core, a plugin system, and an MCP server are exactly the parts teams underestimate. There is no release date in the README, and the main repo's four releases predate the rewrite direction — they belong to the old editor's history.
• The star count misleads newcomers. 97,540 stars describe the classic editor's reputation. They sit on the rewrite's page, and nothing but a Status paragraph separates a new visitor from cloning the wrong repo for the wrong job.
• CapCut is still the safer deadline tool. It is closed, increasingly paywalled, and it ships finished features on a schedule. If a client's video is due tomorrow, that trade may be worth it — open code you cannot run beats nothing only when it runs.
• This piece is repo reading, not editing time. I have not cut a real project in the classic editor for this analysis; the claims above trace to the two repos' own pages, which is also why the verdict stays narrow.

The Verdict

OpenCut is worth watching and, for browser-based editing today, worth using in its classic form — with your eyes open about what archived means. The rewrite's plan reads like the right one: one Rust core, plugins first, an MCP server for agents, headless rendering for automation. Plans are cheap in open source; shipped editors are not, and this project currently has one of each.

The practical rule: edit on the classic, build nothing on the rewrite, and re-check the main repo when new.opencut.app stops calling itself a preview. More tools in this exact mold — free, open, and honest about their limits — live in the SupoClip setup guide and across the projects page and the blog archive.

---

Not affiliated with OpenCut or CapCut. Sources: OpenCut GitHub repository, OpenCut Classic repository, opencut.app.