Open-source browser-based video editing, honestly reviewed. No marketing fluff, just what you get when you try to escape CapCut’s paywall.

TL;DR

What it is: Open-source (MIT) browser-based video editor — CapCut’s UI model, but the code lives on GitHub and your videos never leave your device [1][2].
Who it’s for: Non-technical creators who want timeline-based video editing without CapCut’s growing paywalls, and privacy-conscious users who don’t want their footage uploaded to TikTok-affiliated servers.
Cost savings: CapCut Pro runs roughly $7.99/mo or $49.99/year. OpenCut is free — no subscriptions, no watermarks [README].
Key strength: Radical privacy. All editing happens in your browser, AI features run on-device, nothing is uploaded to any server [1][2]. Also MIT-licensed, so you can self-host it.
Key weakness: This is early-stage software. As of April 2026 it’s still in beta, features are limited compared to CapCut, and the project had a notable development setback in its first year [3]. Don’t migrate your production workflow here yet.

What is OpenCut

OpenCut is a browser-based video editor built as a direct response to CapCut’s shift toward paywalling features. The GitHub README is blunt about the motivation: “Privacy. Your videos stay on your device. Free features. Most basic CapCut features are now paywalled. Simple. People want editors that are easy to use — CapCut proved that.” [README]

The core proposition is straightforward: timeline-based editing with multi-track support and real-time preview, running entirely in your browser using a Next.js frontend. Nothing gets uploaded. Your project files are stored in your browser’s IndexedDB — locally, on your machine [2]. The MIT license means you can also pull the source and self-host it on your own server with Docker [README].

The project launched in mid-2025 and hit approximately 46,942 GitHub stars quickly — a number that reflects genuine interest from the CapCut-refugee market rather than an established, production-ready product [merged profile]. AlternativeTo tracks it at 48,029 stars and 5,047 forks as of April 2026, with the community actively tagging it as an alternative to CapCut, FreeCut, and a dozen other video editors [3].

The technical stack is TypeScript with Zustand for state management. Sponsors include Vercel (hosting) and fal.ai (AI inference) — both OSS program supporters rather than commercial investors in the project [README].

Why people choose it

The honest answer is that most people who star this project are choosing a direction more than a current product. The pull is straightforward: CapCut’s parent company is ByteDance, and CapCut has been systematically moving core features behind its Pro paywall [README]. For creators who don’t want their footage touching ByteDance servers, and don’t want to pay $8/month for features that were free a year ago, OpenCut is the most visible alternative in the browser-based category.

An AlternativeTo commenter who gave it five stars in August 2025 put it plainly: “Doesn’t have much features yet, but I feel like this is going to be a really cool alternative to CapCut when it has better functionality. I will definitely keep an eye on it.” [3] That’s the modal sentiment — interested, watching, not yet relying on it.

The privacy angle is real and clearly articulated. OpenCut’s terms of service explicitly state: “Your content never leaves your device. You retain all intellectual property rights to your content. We never see, store, or have access to your files.” [1] The privacy policy backs this up — no accounts, no individual tracking, AI features (auto captions) running in-browser on local models [2]. For a content creator nervous about uploading client work to a platform owned by a foreign conglomerate under US scrutiny, this is genuinely meaningful.

Richard Djarbeng’s blog covered OpenCut in June 2025 with the framing “A Free, Open-Source Alternative to CapCut” — one of the earlier mainstream write-ups acknowledging the gap it’s filling [5].

What’s harder to find is reviews from people who’ve used it for a full project and kept using it. At this stage, the honest answer is: most people are keeping an eye on it.

Features

Based on the README and what’s documented in the project:

Core editing:

Timeline-based editing interface [README]
Multi-track support [README]
Real-time preview [README]
No watermarks [README]
No subscription required [README]

Privacy and AI:

All editing runs locally in-browser — no server-side processing [1][2]
Auto captions powered by on-device AI models (no content uploaded) [2]
Projects stored in browser IndexedDB [2]

Self-hosting:

Docker Compose deployment (database + Redis + app) [README]
Full source available under MIT license [README]
Bun-based dev environment for contributors [README]

What it explicitly doesn’t have yet:

Filters, effects, transitions — the README’s contributing guide explicitly asks contributors to avoid working on “preview panel enhancements (fonts, stickers, effects)” for now because the team is rebuilding the rendering approach [README]
Export functionality is also in active refactoring with a new binary rendering approach [README]
No accounts, no cloud sync (by design, but also a limitation for cross-device workflows) [2]

The feature set is deliberately simple. The README contributing guidelines flag “timeline functionality, project management, performance, bug fixes, and UI improvements” as the current focus areas — which tells you something about how much core infrastructure is still being built [README].

Pricing: SaaS vs self-hosted math

OpenCut: Free. No tiers, no credits, no per-minute pricing.

CapCut for comparison:

Free tier: exists, but basic features are steadily moving behind the paywall [README]
CapCut Pro: approximately $7.99/month or $49.99/year (data from general market knowledge — specific current pricing not available in the provided sources)
CapCut is owned by ByteDance; your footage passes through their servers

Self-hosting OpenCut:

Software: $0 (MIT license) [README][1]
VPS: $5–10/month if you run it on your own server
Docker Compose setup: straightforward if you have Linux experience [README]
Your data never leaves your infrastructure [1][2]

The math: For a solo creator currently on CapCut Pro, switching to self-hosted OpenCut saves roughly $50–100/year. That’s not the dramatic Zapier-level savings story — CapCut isn’t that expensive. The real value isn’t the $8/month. It’s the combination of privacy (no ByteDance servers), no paywall creep, and owning your editing environment with MIT-licensed software you can modify.

For teams or agencies doing client video work, the privacy argument becomes more significant than the cost argument.

Deployment reality check

There are two ways to run OpenCut:

Option A — Use the hosted version at opencut.app. Still requires a beta waitlist as of this writing. No setup needed. Your projects stay in your browser’s local storage. The risk: if you clear your browser data, your projects are gone. OpenCut’s own terms acknowledge this: “Projects are stored in your browser and may be lost if you clear browser data.” [1] There’s no cloud backup option.

Option B — Self-host with Docker. The README provides a Docker Compose file that spins up the app, PostgreSQL, and Redis together. A working instance is available at localhost:3100 after docker compose up -d. You’ll need a domain and reverse proxy (Caddy or nginx) to expose it externally [README].

For a technical user: 30–60 minutes to a running self-hosted instance. For a non-technical founder: this probably isn’t the path yet — the Docker setup is functional but there’s no one-click installer or maintained deployment guide for non-developers.

The harder reality check: In December 2025, an AlternativeTo reviewer published a detailed post about a significant development setback. The developer’s own account (linked in the review): four months into development, after a month of work on a complete codebase overhaul done without version control, the developer’s PC got malware, was reset, and the work was lost. The developer restarted the refactor from scratch and was working locally before pushing [3]. This is an honest disclosure from the developer, not speculation — but it’s worth knowing if you’re evaluating project maturity. A month of lost work, working locally without pushing — these aren’t enterprise-grade development practices for a tool now at 46,000 stars.

The project is being rebuilt for scalability, and the current codebase is explicitly described as a work in progress. “The codebase will be entirely different. It’s actually gonna be scalable. A codebase you’d expect for a real video editor.” [3] Promising, but not there yet.

Pros and cons

Pros

Hard privacy guarantee. All processing in-browser, AI on-device, no server uploads, no account required. The privacy policy and terms are unusually clear and non-lawyerly [1][2]. For anyone processing client footage or sensitive content, this is a real differentiator.
MIT license. Fork it, self-host it, embed it in your own product. No usage restrictions, no “fair-code” asterisks [1][README].
No watermarks, no subscriptions. The free tier is genuinely free [README].
46,000+ stars and active community. 5,000+ forks means real developer interest in the codebase. This isn’t abandonware [3].
Clean development setup. Bun + Docker Compose + TypeScript is a modern, well-structured stack for contributors [README].
Honest terms. The ToS and privacy policy read like they were written by engineers, not lawyers trying to obscure data practices [1][2].

Cons

Still early-stage. Limited feature set. Effects, filters, transitions, and export are all in active development or refactoring [README].
Development maturity concerns. The codebase has gone through a major unversioned rebuild after a data loss incident. The project is recovering, not cruising [3].
AlternativeTo rating: 3.3/5. Only 3 reviews, but not a strong signal from early adopters [3].
Browser storage = fragile projects. Projects live in IndexedDB. Clear your browser cache and they’re gone. There’s no export-to-project-file or cloud backup [1][2].
No account system. Can’t sync across devices, can’t recover work from another machine, can’t collaborate [2].
Beta waitlist for hosted version. You can’t just go to opencut.app and start editing today without getting through the waitlist.
Still no core CapCut features. The stickers, effects, transitions, and AI filters that CapCut users rely on aren’t there yet [README][3].

Who should use this / who shouldn’t

Use OpenCut if:

Privacy is non-negotiable — you’re editing client footage, sensitive content, or anything you refuse to upload to ByteDance servers.
You want to self-host an MIT-licensed editor on your own infrastructure and have Docker experience.
You’re a developer interested in contributing to the project — the TypeScript stack is clean and the contributing guide is clear [README].
You need basic timeline editing for simple cuts and don’t depend on effects/filters.

Skip it for now (check back in 6 months) if:

You’re a regular creator who needs effects, transitions, stickers, templates, or reliable export.
You’re doing production work that can’t afford to hit a bug in beta software.
You want a tool you can hand to a non-technical team member without setup friction.

Skip it (use DaVinci Resolve) if:

You need professional-grade color grading, audio mixing, or multi-camera editing.
Performance on large projects matters — browser-based editing has hard limits that desktop software doesn’t.

Skip it (use Kdenlive or Shotcut) if:

You want a mature, feature-complete open-source editor today — both Kdenlive and Shotcut are desktop apps with years of development behind them.

Stay on CapCut (for now) if:

You rely on CapCut’s AI features, text animations, effects library, or mobile app.
You’re not processing sensitive footage and the price is acceptable.

Alternatives worth considering

DaVinci Resolve — Free tier covers most use cases, professional-grade, desktop-only, closed source. The power user’s choice.
Kdenlive — Mature open-source desktop editor, Linux/Mac/Windows, GPL. Feature-complete today, less polished UI than CapCut.
Shotcut — Another mature open-source desktop editor, cross-platform. Less intuitive than Kdenlive but stable.
Clapper — Open-source, privacy-focused, browser-based alternative also in development.
CapCut (free tier) — If you don’t care about privacy or ByteDance ownership, the free tier still covers basic editing.
Descript — If you specifically need AI-powered transcription-based editing; not open source, not free.

The realistic comparison for someone leaving CapCut is OpenCut vs Kdenlive/Shotcut. If you want a browser-based workflow with strong privacy guarantees and you’re willing to wait for the feature set to mature, OpenCut is the direction to watch. If you need a working tool today with full features, Kdenlive or Shotcut are there now.

Bottom line

OpenCut is a genuine open-source CapCut alternative with an unusually honest privacy story and a clean technical foundation. The 46,000 GitHub stars reflect real market frustration with CapCut’s paywall creep and ByteDance data concerns — not manufactured hype. But the product is early, the codebase has been through a significant setback, and the current feature set doesn’t yet replace what CapCut users actually use. The right way to think about OpenCut in April 2026 is: a project worth watching closely, not one ready for your main video editing workflow. If you’re a developer, it’s worth contributing to. If you’re a creator, bookmark it and check back in six months. If privacy is your primary concern and your editing needs are simple (cuts, basic timeline, no effects), it might work today — just don’t clear your browser cache and keep your exports as your backup.

Sources

Terms of Service — OpenCut (last updated March 15, 2026). https://opencut.app/terms
Privacy Policy — OpenCut (last updated March 15, 2026). https://opencut.app/privacy
AlternativeTo — OpenCut listing (48,029 GitHub stars, 3 reviews, rating 3.3/5, updated Apr 14, 2026). https://alternativeto.net/software/opencut/about/
FOSS Privacy & Security Part1 — AlternativeTo list (OpenCut featured). https://alternativeto.net/lists/42260/foss-privacy-and-security/
Richard Djarbeng — OpenCut: A Free, Open-Source Alternative to CapCut (rdjarbeng.com, 2025). https://rdjarbeng.com/authors/richard/