# OpenReel Video: a browser-based, client-side video editor built on WebCodecs and WebGPU > OpenReel Video is an MIT-licensed React and TypeScript editor that runs entirely in the browser, with a pnpm monorepo you can self-host. This review covers what it does, how to run it locally, and where the client-side design breaks down. **Augani/openreel-video** — OpenReel Video - Professional browser-based video editor. Open source CapCut alternative. 100% browser-based, no installation, no cloud uploads, no watermarks. - Repository: https://github.com/Augani/openreel-video - Stars: 5,229 · Forks: 758 - Language: TypeScript - License: MIT - Published: 2026-09-23 · Updated: 2026-09-23 · Language: en - Canonical page: https://hysenlabs.com/projects/augani-openreel-video ## The problem OpenReel Video targets: editing without an upload or an installer Most browser video tools are thin front ends. You drag a clip in, it goes to a server, and the render comes back as a download link. OpenReel Video takes the opposite position. The README states that it is "100% Client-Side" and that "Your videos never leave your device. No uploads, no cloud processing, complete privacy." The editing session, the decoded frames, the audio graph and the export all stay inside the tab. That constraint defines the audience. It suits someone cutting a short video on a laptop who does not want a 4 GB install, a subscription, or a watermark on the output. It also suits privacy-sensitive work where the footage cannot leave the machine at all. The README frames the project as "The open source CapCut alternative," and the licence is MIT, so there is no per-seat cost and no export watermark. The trade-off is that the browser becomes the runtime. Anything the browser cannot decode, the editor cannot edit. Anything the machine cannot hold in memory, the editor cannot comfortably scrub. ## How the client-side engine is put together The repository is a pnpm monorepo with two main parts. The README describes apps/web as the React frontend at roughly 66k lines, holding components, Zustand stores, services for auto-save and screen recording, and bridges that coordinate the engines. packages/core holds the engines at roughly 59k lines, split into video, audio, graphics, text, export and storage modules. The data flow follows that split. UI actions land in a Zustand store; the README states the design principle that "Every edit is an undoable action" over immutable state. Bridges pass the resulting state to the core engines, which render through WebGPU, process audio through the Web Audio API, and encode through WebCodecs. Storage goes to IndexedDB, which is also what powers auto-save. The dependency list is short and telling: @ffmpeg/core and @ffmpeg/core-mt at 0.12.6, plus mediabunny for media processing. The build script runs build:wasm before the web build, which implies the FFmpeg cores are compiled to WebAssembly and shipped with the app rather than fetched from a server at edit time. The README lists a frame cache using an LRU strategy and Web Workers for background processing. Both are memory-versus-responsiveness choices, and both matter more here than in a native editor, because the tab has a hard memory ceiling that a desktop application does not. ## Running OpenReel Video locally with pnpm The README gives a Quick Start for running the editor on your own machine. It requires Node.js 18 or newer, and package.json declares pnpm 11.7.0 as the package manager with a minimum of pnpm 8. The clone, install and dev commands are: ```bash git clone https://github.com/Augani/openreel-video.git cd openreel-video pnpm install pnpm dev ``` After pnpm dev, the README says to open http://localhost:5173. That is the Vite development server port, and you should see the editor shell with the timeline and preview panels. For a production bundle, the README gives a two-step build. The root build script compiles the WebAssembly core first, then builds the web app, so the first run is slower than a plain frontend build: ```bash pnpm build pnpm preview ``` If you would rather not install anything, the README points to https://openreel.video as a hosted instance you can open directly. Browser support is documented as Chrome 94+, Edge 94+, Firefox 130+ and Safari 16.4+, with a recommendation of 8 GB of RAM and a dedicated GPU for 4K work. The repository also ships a start.sh at the top level, though the README does not document what it does. ## Where the browser-only design becomes the wrong tool The README's own status badge reads "Beta," and the most recent release is v1.0.0-alpha.17 from 2026-08-29. The last push to the default branch was on 2026-08-29. An alpha release number is a fair signal about API and project-format stability, and the README does not document a migration path between project file versions. Memory is the harder limit. All decoding, compositing and encoding happen in one tab, and the README's own performance notes lean on an LRU frame cache and Web Workers to keep playback smooth. A long timeline with 4K source material will hit the tab's memory ceiling before a native editor does. The README does not state a maximum project size or a tested clip count. Codec support is inherited from the browser. The README claims full support across Chrome, Edge, Firefox and Safari, but the editor still depends on what each engine can decode and encode through WebCodecs. A format your browser cannot open is a format OpenReel cannot edit, regardless of what the feature list says. Finally, there is no server component. If your workflow needs unattended batch rendering, a shared project library across a team, or a render farm, this architecture is the wrong shape. The README does not document a headless or CLI export path. ## How OpenReel Video differs from Shotcut and Kdenlive The obvious alternative for an editor who wants no subscription and no watermark is a native open source NLE such as Shotcut or Kdenlive. Both are desktop applications built on MLT and FFmpeg, and both run the decode, composite and encode pipeline as native processes with direct file system access. The difference in approach is where the work happens. Shotcut and Kdenlive spawn native threads and can address far more memory than a browser tab, and they read and write files directly rather than through IndexedDB. They also install locally, which is exactly what OpenReel avoids. OpenReel's counter-argument is deployment and reach. Because it is a React app served over HTTP, a self-hosted instance is reachable from any supported browser without installing anything, and the README's privacy claim holds by construction: there is no upload step to disable. The FFmpeg WebAssembly cores are bundled rather than invoked as a system binary, so there is no FFmpeg install to manage. Pick the native editor when you need long timelines, exotic codecs, or scripted batch exports. Pick OpenReel when the constraint is that the footage must not leave the machine and the install must not exist. ## Maintenance, packaging and the MIT licence The repository is not archived, and the last push was on 2026-08-29. The release history shows a steady cadence through 2026: v0.4.0 on 2026-05-14, v0.5.0 on 2026-05-30, and v1.0.0-alpha.17 on 2026-08-29. The version field in the root package.json is 0.1.2, which does not match the release tags, so treat the tags as the real version signal. The licence is MIT, declared in package.json and in the LICENSE file at the repository root. For most adopters that means you can use, modify and redistribute the code, including in commercial settings, provided the copyright notice and permission notice travel with it. This is a general description of the licence text, not legal advice; if you plan to redistribute a modified build, read LICENSE yourself. Upgrade cost is the part the README does not cover. It documents no project file format version, no migration command, and no rollback procedure. Since projects live in IndexedDB under the browser's origin, clearing site data for the origin would remove them, and the README does not document an export-and-restore path beyond the general "Project sharing" feature. Before you rely on it, test that export and import round-trip on a throwaway project. ## Conclusion Adopt OpenReel Video if you edit short-form footage on a recent Chrome or Edge machine and want the timeline to stay on your own disk. Skip it if you need a headless render farm, a stable 1.0, or a browser without WebCodecs. Before committing, open a real project, verify that IndexedDB autosave survives a tab close, and confirm your target export preset finishes at the resolution you need. ## FAQ ### What does OpenReel Video do? It is a browser-based video editor that runs entirely client-side, with a multi-track timeline, effects, color grading and export to MP4, WebM and ProRes. The README states that videos never leave your device, with no uploads and no cloud processing. ### Is OpenReel Video a good open source alternative to CapCut? The README positions it as "The open source CapCut alternative" and it is MIT licensed with no watermarks and no subscription. It is still labelled Beta, with the latest release being v1.0.0-alpha.17, so expect alpha-level stability. ### Is OpenReel Video one of the best online open source video editors? That depends on your constraints. It is fully client-side and self-hostable under MIT, but it runs in a browser tab, so it is bounded by browser codec support and tab memory in a way native editors are not. ### What is the best app for making video reels? The README targets short-form editing in the browser, with text animations, karaoke-style subtitles, beat detection and export presets up to 4K at 60fps. Whether it is the best for you depends on whether your browser can decode your footage and your machine has the memory for it. ## Sources - [Augani/openreel-video on GitHub](https://github.com/Augani/openreel-video) - [Issues](https://github.com/Augani/openreel-video/issues) - [License: MIT](https://github.com/Augani/openreel-video/blob/main/LICENSE) - [README](https://github.com/Augani/openreel-video/blob/main/README.md) - [Releases](https://github.com/Augani/openreel-video/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/augani-openreel-video