OpenCut is a free, open-source video editor that runs in the browser, pitched as a CapCut alternative. It went viral on the simplest of value propositions: a privacy-respecting editor that processes video locally, with no watermark and no account wall. That promise is why it sits above 55k stars. The honest framing, though, is that OpenCut is in the middle of a ground-up rewrite, so what you get today and what the roadmap promises are two different things. This page keeps those separate.
What works today, and what is coming
The classic build at opencut.app is the usable editor: a multi-track timeline, text layers, local export without a watermark, and subtitle generation. The new build (developed at new.opencut.app) is a full rewrite intended to replace it, and its roadmap is ambitious: a Rust core shared across web, desktop, and mobile; a plugin-first architecture; an editor API; an MCP server for AI-agent integration; and a headless mode for batch rendering. Read the roadmap as intent, not as shipped features. The version numbers (v0.1 through v0.3 as of 2026) are honest about the maturity.
Tech stack and running it locally
The web app is React 19 on Vite (not Next.js), with TanStack Router, Tailwind 4, and a Turbo plus Bun monorepo, deployed on Cloudflare Workers.
bun install
bun run dev:web # web app on the Vite dev server
bun run buildMost users will just open opencut.app. Self-hosting is not the primary path; this is a web app first, with desktop in the rewrite’s plans.
The honest maturity check
This is what a README-beating page owes you. OpenCut is exciting and early. The open issues show real, current limitations:
- Text layers could fail to update live on the canvas, freezing as the default text while the input changed (#818).
- A carousel component leaked memory by not removing listeners on unmount (#821).
- Exporting large videos could be killed by the OS on Linux from memory pressure (#812).
- CJK fonts are not supported out of the box (#817), and the web export resolution was reported fixed at 160x160 with no setting (#816).
None of these are surprising for a v0.x editor mid-rewrite, but they tell you the truth: OpenCut is a promising project and a daily-driver-in-progress, not yet a finished CapCut replacement. The project also notes it is not accepting external PRs during the rewrite, so you cannot easily patch around these yet.
When it fits, and when it does not
It fits quick browser-based edits where privacy and “no watermark” matter, and anyone who wants to follow or contribute to an open video editor’s evolution. It does not fit professional or deadline work that needs CJK text, high-resolution export, and rock-solid stability today: a mature tool is the safer call until the rewrite lands.
How it compares
| Project | Shape | Note |
|---|---|---|
| OpenCut-app/OpenCut | Browser editor, CapCut UX | Local processing, mid-rewrite |
| remotion-dev/remotion | React components to video | Programmatic, mature, licensing terms |
| redotvideo/revideo | Animation-driven video library | Code-first, smaller |
| Shotcut | Desktop editor (FFmpeg, C++) | Mature, not browser-based |
Remotion and revideo are code-first (you write video as code); OpenCut is a GUI editor for people who want CapCut’s interface, not a programming model. Shotcut is the mature desktop option if you do not need the browser. OpenCut’s bet is UX familiarity plus local privacy.
Background worth knowing
OpenCut is sponsored by fal.ai and has an active community around the rewrite. The decision to rewrite from scratch (rather than iterate the classic build) is the defining product call: it trades short-term polish for a cross-platform Rust core and a plugin architecture. Whether that pays off is the open question that makes this repo worth watching.
FAQ
Is OpenCut free? Yes. OpenCut is MIT-licensed and open-source, runs in the browser, and exports without a watermark or an account.
Is OpenCut a good CapCut alternative? It is the leading open-source one in spirit, but as of 2026-06 it is a v0.x project mid-rewrite, with open bugs in text rendering, memory, and large exports. Promising, not yet a finished replacement.
Does OpenCut work offline and process video locally? Yes, local processing is the core promise: editing and export happen client-side, which is the privacy angle that drove its popularity, and the rewrite plans a Rust core shared across web, desktop, and mobile.
Does OpenCut support Chinese or CJK fonts? Not out of the box yet (#817), and web export resolution was reported fixed at a low value (#816). If you need CJK text or high-resolution export today, wait for the rewrite.
Related reading
For programmatic, agent-oriented video generation see heygen-com/hyperframes, which takes the opposite approach: write HTML, render video, built for agents rather than for a timeline UI.