OpenCut: The Open-Source CapCut Alternative with 32K Stars

OpenCut is a free, open-source video editor that has quickly amassed over 32,000 GitHub stars by positioning itself as the leading privacy-respecting alternative to CapCut (ByteDance’s popular video editing app). Developed by OpenCut-app, the project offers a comprehensive video editing experience across web, desktop, and mobile platforms – all while ensuring user data never leaves the device.

The project was born from growing concerns about CapCut’s data collection practices and the lack of a capable open-source alternative with modern features. OpenCut addresses this gap with a feature-rich editor that supports multi-track timelines, transitions, effects, text overlays, chroma key, speed controls, and direct export to popular formats. With its modern tech stack combining Next.js for the frontend and Rust for performance-critical processing, OpenCut delivers desktop-class editing performance entirely in the browser.

What features does OpenCut offer?

How does OpenCut compare to CapCut?

What tech stack powers OpenCut?

OpenCut’s architecture is a showcase of modern web development best practices. The frontend is built with Next.js 14 and React, leveraging WebAssembly for video processing tasks. The rendering engine is written in Rust and compiled to WASM, enabling near-native performance for timeline scrubbing, effect rendering, and export encoding. Video decoding leverages FFmpeg compiled to WebAssembly, while the state management uses Zustand for predictable and performant reactivity across the editor’s complex state tree.

flowchart TD
    A[Browser/Electron] --> B[Next.js UI Layer]
    B --> C[React Components]
    C --> D[Zustand State Store]
    D --> E[Rust WASM Engine]
    E --> F[FFmpeg WASM Decoder]
    E --> G[WebGL Renderer]
    E --> H[WebCodecs API]
    F --> I[Video Frames]
    G --> I
    H --> I
    I --> J[Canvas Output]
    J --> K[MP4/WebM Export]

Is OpenCut truly privacy-focused?

Yes. OpenCut processes all video data entirely on the user’s device. There are no telemetry services, no analytics trackers, no cloud dependencies for core editing functionality, and no user accounts required. The web version runs completely in the browser sandbox – once the page loads, no network requests are made for editing features. The desktop version (built with Electron) extends this with local file system access while maintaining the same privacy guarantees. For AI features like background removal, OpenCut uses ONNX Runtime Web for on-device inference, ensuring no video frames are sent to external servers.

What is the current project status?

OpenCut is in active development with regular releases. The core editing pipeline is stable and production-ready. The beta phase focuses on AI features, performance optimizations, and mobile platform support. The project has received contributions from over 200 developers worldwide and maintains an active Discord community. The mobile version for iOS and Android is currently in private beta, with a public release expected in mid-2026.

sequenceDiagram
    participant User
    participant OpenCut
    participant RustEngine as Rust WASM Engine
    participant Device as Local Device

    User->>OpenCut: Import video file
    OpenCut->>RustEngine: Decode via FFmpeg WASM
    RustEngine->>Device: Process locally
    Device-->>RustEngine: Decoded frames
    OpenCut->>User: Display in timeline
    User->>OpenCut: Apply effects & edits
    OpenCut->>RustEngine: Render effects
    RustEngine->>Device: GPU accelerated (WebGL)
    User->>OpenCut: Export video
    OpenCut->>RustEngine: Encode to MP4
    RustEngine-->>OpenCut: Encoded file
    OpenCut-->>User: Download complete

How does OpenCut handle performance in the browser?

OpenCut leverages several modern browser APIs to achieve desktop-class performance. The WebCodecs API provides hardware-accelerated video decoding and encoding, while WebGL 2.0 handles GPU-accelerated effect rendering. For browsers that don’t support WebCodecs, OpenCut falls back to the FFmpeg WASM decoder with optimized SIMD instructions. The Rust WASM engine manages frame buffers efficiently, and the render pipeline uses a worker thread pool to prevent UI blocking during export operations.

Frequently Asked Questions

What is OpenCut? OpenCut is a free, open-source video editor that runs in the browser or as a desktop app, designed as a privacy-focused alternative to CapCut.

What features does it support? Multi-track timeline editing, transitions, effects, chroma key, audio editing, text overlays, animated titles, and 4K export. AI features like background removal are in beta.

What is the tech stack? Next.js 14 frontend, Rust compiled to WebAssembly for video processing, FFmpeg WASM for codec support, WebGL for GPU acceleration, and Zustand for state management.

How does it protect privacy? All video processing happens on-device. No data is sent to servers, no telemetry is collected, and no user account is required. AI features use on-device ONNX Runtime inference.

Is the project actively maintained? Yes, with over 32,000 GitHub stars, 200+ contributors, and regular releases. Mobile apps are in private beta with a public release expected in mid-2026.

Further Reading

• OpenCut GitHub Repository
• OpenCut Official Website
• Next.js Documentation
• ONNX Runtime Web
• FFmpeg WASM Project