OpenCut

Short explainers and product demonstrations

Use Classic to assemble a screen recording, trim supporting footage, add text and check a final export. Start with a small representative project before choosing it for a recurring production workflow. A useful trial includes the camera format, screen recording, soundtrack and final aspect ratio your team actually uses, rather than an empty timeline.

Accessible browser workflows

The hosted editor is the lowest-friction evaluation path. Browser execution avoids a large native installation, but local editing state and media still need explicit backup procedures. Test what survives a page reload and what happens when browser storage is cleared or the machine runs short of disk space.

Frontend and media engineering

The archived Classic code provides a substantial reference for timelines, rendering, masks, audio and export behavior. The rewrite is a separate opportunity to examine workspace design and the Rust core. Keep those architectures separate in a fork: a fix or deployment recipe for the Next.js Classic application may not apply to the TanStack and Vite rewrite.

Private or customized deployments

Developers can run the source locally and adapt it, but each code path has different operational requirements. Classic documents optional PostgreSQL and Redis services and Cloudflare deployment configuration. The rewrite has Cloudflare web and API workspaces. A self-hosted operator must inspect enabled services and keys before making claims about data residency or offline behavior.

Related creative tooling

OpenCut addresses hands-on editing. HyperFrames focuses on code-authored video compositions and rendering pipelines, while Doory centers on canvas design and collaboration. Those are related workflows rather than direct substitutes for every timeline feature. Choose based on the type of source, the required edits and the final output.

OpenCut is relevant when an open-source browser editor fits the job and the team accepts its current transition between codebases. Its main advantage for a technical audience is access to the implementation and the option to run or modify it. The maintenance status of Classic and the maturity of the rewrite are more useful decision factors than a popularity count.

Use Classic to evaluate the available editor, then record the exact revision used for a self-hosted build. Because that repository is archived, a long-lived deployment means owning dependency updates and fixes yourself. For a time-sensitive client delivery, validate the entire import-to-export path before making the editor a required part of the workflow.

The rewrite status lists a shared Rust core, an Editor API, first-class plugins, MCP, headless mode and an in-editor scripting tab. These are development goals. A folder named API or a working desktop window is not evidence that those integration contracts are complete. This listing therefore does not mark a supported public Editor API or finished native/mobile apps as available.

MIT covers the OpenCut application code. The repository separately records FFmpeg build information and library licensing. Teams redistributing an editor or shipping a fork should review those exact dependencies alongside their media permissions. The hosted site and beta remain useful for evaluation, while an organization must define its own support and upgrade policy for a private deployment.