explaingit

opencut-app/opencut

🔥 Hot51,340TypeScriptAudience · vibe coderComplexity · 4/5ActiveLicenseSetup · moderate

TLDR

Free, open-source video editor that runs in your browser with no cloud uploads. Edit videos locally on your device as a privacy-friendly alternative to CapCut.

Mindmap

mindmap
  root((OpenCut))
    What it does
      Trim and cut clips
      Add text overlays
      Combine footage
      Apply visual effects
    How it works
      Web browser app
      Desktop app coming
      Rust core for speed
      WASM for processing
    Tech stack
      TypeScript frontend
      Next.js framework
      Rust backend
      Bun runtime
    Use cases
      Content creation
      Social media clips
      Quick edits
      Privacy-first editing
    Key features
      No paywall
      Local processing
      Files stay private
      Open source

Things people build with this

USE CASE 1

Trim, cut, and combine video clips without uploading to the cloud.

USE CASE 2

Add text overlays and visual effects to social media videos locally.

USE CASE 3

Edit short-form content for TikTok, Instagram, or YouTube without paying subscription fees.

USE CASE 4

Create videos while keeping all footage private on your own device.

Tech stack

TypeScriptNext.jsReactRustWebAssemblyBunGPUIDocker

Getting it running

Difficulty · moderate Time to first run · 30min

Requires Rust/WebAssembly compilation and Bun runtime; Docker available but not required for local dev.

Use freely for any purpose including commercial, as long as you keep the copyright notice.

In plain English

OpenCut is a free, open-source video editor that runs in a web browser, with a desktop app in development. It is positioned as an open-source alternative to CapCut, a popular mobile and web video editing app that has moved many of its basic features behind a paywall. OpenCut aims to provide simple, accessible video editing tools that keep your files private, all processing happens on your own device, so your videos never leave your machine. The project is organized as a monorepo containing a web application, a desktop application (currently in progress), and a Rust-based core. The web app is built with Next.js, a React framework. The desktop app uses GPUI, a native UI toolkit. The Rust layer handles performance-critical work like GPU-based video compositing, visual effects, and masks, and it is compiled to WASM (WebAssembly) so that the web app can use it directly in the browser without needing a server. The project is actively migrating processing logic from TypeScript into this Rust/WASM core for better performance across all platforms. You would use OpenCut if you want a no-cost, privacy-respecting video editor for simple tasks like trimming clips, adding text, combining footage, or applying effects, the kinds of things CapCut originally made easy. It is especially relevant for content creators who do not want to pay for CapCut's features or share footage with third-party cloud services. The tech stack is TypeScript for the web frontend, Next.js as the framework, Bun as the JavaScript runtime and package manager, Rust for the core processing layer compiled to WASM, and Docker for local development dependencies including a PostgreSQL database and Redis.

Copy-paste prompts

Prompt 1
How do I set up OpenCut locally for development? Walk me through the monorepo structure and getting the web app running with Bun.
Prompt 2
Show me how to add a new video effect to OpenCut. Where would I write the Rust code and how does it get compiled to WASM?
Prompt 3
I want to contribute a UI feature to the web editor. What's the Next.js component structure and how do I hook it up to the Rust core?
Prompt 4
Explain the architecture: how does the TypeScript frontend communicate with the Rust/WASM layer for video processing?
Prompt 5
What's the roadmap for the desktop app? How is GPUI being used and what features are planned?
Open on GitHub → Explain another repo

Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.