OpenCut

OpenCut is an open-source video editor for timeline-based work. The browser beta uses Classic while the team builds a new Rust-based editor.

Prepare a timestamped cut list for OpenCut

Turn a transcript or clip inventory into an editing plan with in and out points and a short playback checklist.

Include source filenames, timestamps, target duration, and intended audience.

Copy the request into a new Floatboat conversation and provide the required material.

Download Floatboat

Your request for Floatboat

Preview and copy the request. It is not sent automatically from this page.

Reference: OpenCut
https://github.com/OpenCut-app/OpenCut

Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding.

My task:
Use the OpenCut README to distinguish Classic from rewrite plans. From my timecoded customer interview transcript, draft a 45-second cut list with source ranges, continuity checks and a review question for each cut. Mark uncertain timestamps and leave media editing for my approval.

Expected deliverable:
A cut list, review checkpoints, and a target export specification for a manual timeline edit.

OpenCut Classic and the Rust rewrite

OpenCut is a timeline editor positioned as an open-source alternative to CapCut. Its public browser beta runs the original Classic codebase. The team archives that code separately while building the next version in the main repository.

The rewrite is intended to share a Rust core across platforms and make room for plugins, an editor API and headless operation. Upstream also lists MCP among the planned capabilities. Keep an edit plan independent of those interfaces until the one you need is available and tested.

For a Floatboat workflow, prepare clip names, timecodes, a target duration and export checks. Use the browser editor to assemble and review the result by hand, and keep the source media and cut decisions available for a later revision.

What to inspect in OpenCut

Classic provides a browser editor for hands-on trials. The main repository tracks the replacement, so use the appropriate source when checking an editor behavior or following development.

  • Timeline assembly

    Arrange source clips and remove unwanted intervals to evaluate how the editor handles a short sequence.

  • Browser beta

    Start with the official early beta and verify that it accepts your media and can produce the output your workflow needs.

  • Rust editor architecture

    Follow the main repository for work on a shared core and plugin-oriented interfaces. Check the documented release status before designing around any new API.

OpenCut use cases

Plan one short cut with a delivery target, then compare the exported file with the timeline. Check whether the intended trims, caption timing and playback survived the export.

Cut an interview highlight from a transcript

Mark a candidate opening, the main quote and a clean closing in the transcript with timecodes. Assemble the selected intervals in the browser editor and verify that transitions preserve the meaning of each answer.

Create a focused product walkthrough

Order source recordings around one user task, then remove waiting time and repeated navigation. Review the short version against a checklist for visible labels and continuity before sharing the export.

Hand off a revised cut to a reviewer

Record the source filenames, in and out points and the reason for each replacement. Give the reviewer the new video and a change list so they can compare the intended edits with the actual playback.

Evaluate a browser editor before adopting it

Use representative clips and a small test project. Record how the beta handles import, timeline edits and export on the browser and device you actually use, then judge whether it covers the delivery requirements.

What you need for a browser editing trial

Use a copy of a short source clip for the first trial. Verify import, preview and export in your own browser before moving a long or deadline-sensitive edit.

  • Browser and authorized media

    Open the official early beta with a short set of clips you may edit and share.

  • Export criteria

    Write down the intended duration, framing and playback checks before committing to the editor for a deliverable.

Related Software Projects

Compare the workflows, operating requirements, and source licenses of these projects.

OpenCut FAQ

Which OpenCut version runs on the official site?
The main repository points users to the Classic-based browser beta at opencut.app while the replacement is being built.
Why is OpenCut Classic archived?
It is the original codebase. The team directs ongoing rewrite work to the main OpenCut repository, and the archived repository is read-only.
Can I use OpenCut as an MCP tool today?
The main repository lists an MCP server in its rewrite plans. Verify a documented release and the actual tool surface before using it in an agent workflow.
Can I depend on automated batch exports?
Headless operation and batch rendering are listed as rewrite goals. Verify manual export on the browser beta with a sample before planning delivery.
Where do I check self-hosting instructions?
The archived Classic README documents its Bun and Docker setup. The main repository has a different development setup for the Rust rewrite.
How is OpenCut licensed?
The main OpenCut repository is MIT-licensed. Source code licensing and rights to the clips or audio you use are separate.