Use Classic for a small edit; skip the rewrite for delivery work
Our OpenCut rewrite build failed at linking, while independent Classic users report completing straightforward browser edits. Use Classic if you want to assemble occasional family footage or a short social post and can check the exported file before relying on it. Skip the rewrite if you need a finished editor for a deadline: its own README sends you to Classic. The distinction matters more than the project's CapCut-alternative description. Current project README
The October 26 sandbox run installed dependencies successfully, then stopped on a missing native library during both build and tests. A separate November 19 deployment attempt stopped at a Compose-file safety check. Neither result cancels somebody else's successful Classic session. They describe different code paths and different tasks. Classic editing reports and rewrite development results answer different questions.
What people use OpenCut for
Patrick Hearn at XDA reports using OpenCut for family videos and social posts, including importing footage, trimming it, adjusting audio and adding basic effects. That is a useful starting point for deciding whether Classic covers your work. It puts a recognisable job ahead of promises about plugins or agents. His account also says background caption work affected performance, so the praise belongs to an occasional editing workflow. Patrick Hearn's XDA review
| Who used it | What they did | What the report supports |
|---|---|---|
| Patrick Hearn, XDA | Edited everyday footage and social posts with trimming, audio changes and basic effects | A simpler workflow suited his occasional editing needs. XDA |
| company_url_finder, r/BestGitHubRepos | Tried a couple of short clips | The workflow felt familiar to a CapCut or DaVinci Resolve user, with advanced effects and AI features missing. Reddit report |
| Creator of the Real Edit Test video | Combined tea-corner footage, a menu clip, music and styled text | The creator reports completing and exporting a promotional montage. Real Edit Test |
| Creator of the Legit or Sh*t video | Edited synthetic footage while watching outside requests | The observed session requested an analytics script; the creator reported no other outside request while editing. Network observation |
The tea-corner example is especially useful because the creator describes actual assembly: placing the menu after the opening shot, putting music on a separate track, cutting the excess, and changing the text's font and colour. That is enough to judge whether the workflow resembles your small promotional job. It is a third-party demonstration, not an export benchmark from our lab.
What happened when we ran it
Our November 19 hands-on attempt failed its safety step because the checkout had no Compose file. The lab runner required one of compose.yaml, compose.yml, docker-compose.yaml or docker-compose.yml. Its word "unsafe" describes that runner rule, not a finding of malicious code.
The run-summary record says the project was deployed with its own Docker Compose and ports bound to 127.0.0.1, but the detailed step records a stop before that deployment. We treat the detailed failure as the observed outcome and the summary as contradictory metadata. Teardown was recorded as successful. There is no completed editing task attached to this attempt.
The earlier source run used commit e668010 on October 26, 2026, with 3 CPUs, 12 GB RAM and the configured image label lab-rust:1. Our install succeeded in 17 seconds with 649 dependencies recorded. The build failed with exit 101 after 243 seconds; the test command failed with exit 101 after 9 seconds.
| Recorded step | Outcome | Meaning for the reader |
|---|---|---|
| November 19 deployment safety | Failed: no recognised Compose file | This deployment route stopped before an editor session. |
| November 19 teardown | OK | The runner recorded cleanup, not a successful product task. |
| October 26 install | Succeeded in 17 seconds; 649 dependencies | Dependency installation completed in this sandbox. |
| October 26 build | Failed in 243 seconds, exit 101 | The desktop binary stopped at native linking. |
| October 26 tests | Failed in 9 seconds, exit 101 | The desktop test target stopped at the same linking requirement. |
Both failing log tails say rust-lld: error: unable to find library -lxkbcommon-x11. The build identifies the target as opencut-desktop. The test tail identifies its test target, then reports that compilation failed. There is no passing-test count to extract from that failure. The finding is narrower and more useful: in this sandbox, the linker could not find the named library, so these commands never supplied a usable desktop editor or a passing test result.
The checkout scan recorded 130 files, about 8,597 source lines and 0.7 MB, alongside two CI workflow files, no Dockerfile and no tests directory. Those scan results describe the measured checkout. They do not mean Rust has no inline tests. Nor does the image label identify the actual Rust or operating-system version; those require the raw toolchain logs. Failed setup here is not proof that Classic editing is broken.
Where people get stuck: match the error to the version
Classic issue reports include browser crashes, UUID errors and database authentication failures; the rewrite adds a separate native development path. A workaround for the old Next.js app belongs with that app. Applying it to the rewrite because both repositories carry the OpenCut name can send you in the wrong direction.
| Report | What the thread says | Resolution recorded there |
|---|---|---|
| #628, out of memory | Users describe opening video and crashing, including Windows Chrome and Ubuntu Firefox reports | A commenter proposes removing frame-cache code. The maintainer asks whether a broader architecture change resolved this particular failure; the thread supplies no confirmation. |
| #205, crypto.randomUUID | A self-hosted Classic session crashes because crypto.randomUUID is unavailable | Commenters suggest HTTPS or localhost and a fallback. Initial success is followed by a recurrence and an unspecified code workaround. The issue is open in the supplied record. |
| #92, Docker prerender error | Classic container builds hit an invalid Html-import error | A commenter reports a successful clean-cache build using production NODE_ENV. The issue is closed. |
| #316, database migration | PostgreSQL rejects the configured user's password | Ni-zav reports success using the actual local PostgreSQL credentials and creating the opencut database. The issue is closed. |
| #228, waitlist feedback | Users cannot tell whether submitting an email worked | A Better Auth URL PR addresses one error; commenters still ask for visible success or failure feedback. The issue is open in the record. |
The UUID thread illustrates why "fixed" can be too broad. Two people initially say the change works. The original reporter then returns with the same error and eventually describes using code that is absent from the discussion. HTTPS or localhost is a concrete suggestion to investigate on a matching Classic deployment; a guaranteed upstream repair would overstate that thread.
For the database error, read which PostgreSQL instance actually rejected the login. The successful report uses that instance's real account and creates the expected database. Copying a sample connection string cannot establish that your local server has the corresponding user. Keep this troubleshooting attached to Classic's optional service-backed configuration, rather than treating a database as a prerequisite for every browser edit.
The rewrite has development commands, not a finished desktop editor
The current desktop README describes an early GPUI application that only opens a window. Its Linux requirements name Vulkan drivers, Wayland and X11 development libraries, including libxkbcommon-x11-dev on Debian or Ubuntu. That documentation gives developers a platform checklist, while our log gives the narrower observation that linking could not find xkbcommon-x11. We have not rerun the build after changing system packages. Desktop README
The root README documents proto for the pinned tools, followed by proto use and separate Moon commands for web, API and desktop development. Classic instead documents Bun, a Next.js web app and optional Docker services for a local database and Redis. These are separate setup routes. An editor wanting to try the available product should start with the hosted Classic site, rather than follow a rewrite development command and expect the same interface. Rewrite README, Classic README
Issue #811 lists an Editor API, plugins, an MCP server, headless rendering and scripting as rewrite work. It gives no release date. For an integration decision, the operative distinction is between an existing manual timeline and an interface the maintainers are still designing. A future MCP server is a reason to follow development, not a present way to hand Classic your agent's editing instructions. Rewrite tracker
Attention is large; Classic maintenance is a separate decision
The GitHub API snapshot on November 19 lists 98,870 stars and a last push on September 24, 2026. Those figures measure repository attention and recorded code activity. They say nothing about how many people finish videos with it. The current Classic README explicitly calls that codebase archived and no longer maintained, which is a much more direct consideration for someone planning a recurring editing workflow. Repository facts, Classic status
In the Reddit thread, MacroMorel calls the project six months without an update; voicedrew corrects that to six months since a release. The difference matters. Release dates, pushes and unresolved issue reports answer different questions. The memory thread contains a maintainer response about architecture work, while the rewrite tracker contains unfinished milestones. Neither the star count nor an old release tag turns those observations into a support commitment. Release-versus-update discussion
Privacy claims need the caption path and browser storage in view
OpenCut's official terms say projects live in browser storage and can disappear when that storage is cleared. The service says it cannot recover them and recommends exporting important finished videos. An output video preserves the finished result; it should not be confused with an editable project you can reopen with every cut and layer intact. Keep original footage separately and decide how much unfinished work you can afford to leave in a browser. Official terms
Local media work also leaves a separate network question. The creator of Legit or Sh*t reports an external analytics-script request on every page, with no other outside request during the observed editing session. Johnny Chen's technical article names Databuddy analytics. That challenges a blanket assurance of no tracking. It is not evidence that the editor uploaded the creator's footage. The observation concerns a script request in that session. Network observation, technical account
Caption descriptions conflict. The terms describe on-device automatic captions, Chen describes Whisper transcription deployed on Modal, and iTechGuides describes importing transcript files. These sources cannot be combined into one confident account of a particular hosted build. If sensitive speech is involved, select the exact caption workflow before bringing that material into the editor. Terms, Chen, iTechGuides
English docs exist; Chinese localization is an open request
OpenCut's root and desktop READMEs are in English, while issue #601 requests Chinese localization. The rewrite discussion also includes offers to translate into Italian and Simplified Chinese. Those are requests and offers, not a list of shipped editor languages. For an English-speaking developer, the setup documentation provides an entry point. For a team needing another interface language, the relevant evidence is the localization thread rather than the breadth of promotional coverage. Localization request, translation discussion
A commenter in #601 suggests ComeCut for multilingual use and lists Simplified Chinese, Traditional Chinese, English, Korean and Japanese. That is a community recommendation to investigate, not a language test of OpenCut or an endorsement from our lab. Bilibili search results also show Chinese-language OpenCut tutorials, including one specifically distinguishing Classic from the rewrite. Tutorial language and interface language are different facts. ComeCut suggestion, Bilibili results
OpenCut vs CapCut, Premiere Pro and NemoVideo
Reported Classic use supports simple manual editing, while the CapCut-parity claim runs ahead of the evidence. The Reddit short-clip report explicitly says advanced effects and AI features are missing. Patrick Hearn's Premiere comparison makes a different case: a simpler free editor suited his occasional work, while he still identifies Premiere with finer control and advanced tasks. Neither account is a controlled comparison of output quality. Reddit comparison, Hearn's comparison
| Alternative | What the supplied comparison says | When I would choose that route |
|---|---|---|
| CapCut | company_url_finder finds Classic familiar but short of advanced effects and AI features | Keep CapCut when your current workflow relies on those features. Short-clip report |
| Adobe Premiere Pro | Hearn prefers OpenCut for occasional work and reserves Premiere for advanced audio, elaborate effects and finer control | Keep Premiere for the advanced work Hearn describes. XDA |
| NemoVideo | Its vendor comparison describes conversational drafts and social variants, versus OpenCut's manual timeline | Consider it when you want to review an automated draft, accepting that this is the vendor's workflow description. Vendor comparison |
NemoVideo's author explicitly says there was no controlled speed test. Its proposed workflow of making a master in OpenCut and variants elsewhere is an editorial suggestion, not a completed customer project. I would choose between these tools by the decisions I want to make manually: placing each cut, or reviewing an agent's first assembly. There is no measured time-saving claim here.
What the other reviews get wrong
Filmora's review describes OpenCut as unreleased and waitlist-only, while the official README directs people to the public Classic editor. That waitlist description gives the wrong answer to someone trying to edit today. It also obscures the more useful question: whether to use the archived Classic codebase or follow the separate rewrite. Filmora review, official README
OpenApps illustrates an independent filmmaker editing offline in a Classic desktop build. The current desktop README describes only an early window, and the supplied profile identifies Classic as the available browser workflow. OpenApps also describes migrations as protection against data loss. The official terms explicitly warn that clearing browser data can destroy projects. Neither an illustrative filmmaker nor migration code supplies a general preservation guarantee. OpenApps, project profile, terms
EmbroideryHoop's OpenCut embroidery tutorial concerns a different use of the name. This review covers OpenCut-app/OpenCut, the video editor. The floomhq repository is another separate project, a Remotion-based production engine, and sir-buckyball/opencut generates CNC instructions. An OpenCutList query is outside the identity of this reviewed repository. Start from the exact GitHub owner and name, rather than assuming similar search results describe the same software. Embroidery tutorial, Remotion project, CNC project
The X promotion by KanikaBK says OpenCut does everything CapCut Pro does. The short-clip Reddit report contradicts that with named feature gaps. XDA's quoted About-page assurance of no activity tracking also needs the analytics observation alongside it. Praise becomes useful only when it preserves the build, task and outcome behind it. X promotion, Reddit, XDA, network observation
Questions people ask
OpenCut is an open-source video editor whose official repository is OpenCut-app/OpenCut; the README directs current editing work to Classic. That answers the broad OpenCut app and OpenCut GitHub searches before choosing a platform or installation route. Official repository
What is OpenCut, and where is its official GitHub repository?
The OpenCut video editor reviewed here belongs to the OpenCut-app organization, at OpenCut-app/OpenCut. The repository describes a rewrite, while opencut.app runs Classic. Follow those links from the official README to avoid borrowing capabilities from similarly named projects.
Is there an official OpenCut Android APK to download from GitHub?
The supplied records give no completed official Android APK release. OpenCut APK, OpenCut APK download and OpenCut GitHub APK searches should start at the official repository, where mobile is listed under rewrite work. The native-mobile request is still open in the pack. A search result using the name is insufficient evidence of an official app. Mobile request, rewrite tracker
How do I install and start using OpenCut?
For available editing, use Classic at opencut.app, as the current README recommends. For local Classic development, its README documents Bun and optional database and Redis services. For rewrite development, use the separate proto and Moon instructions. Our failed desktop linking result belongs to that source evaluation, rather than a requirement to try the hosted browser editor. Rewrite instructions, Classic instructions
How does OpenCut compare with CapCut for everyday editing?
The OpenCut vs CapCut short-clip report finds a familiar workflow and usable straightforward editing, while explicitly naming missing advanced effects and AI features. Choose Classic for a small manual job you can check through export. Keep your existing CapCut workflow if those missing features are part of the job. company_url_finder's report
How does OpenCut compare with Concat?
The OpenCut vs Concat search intent appears in the pack, but its only Concat description is a directory listing, not a substantive comparison. There is no basis here to rank editing quality or reliability between them. The useful next comparison would use the same source clips and required output in both editors. Directory listing
Does OpenCut have AI features today?
OpenCut AI searches bring together conflicting caption descriptions and future agent interfaces. The rewrite tracker places MCP and headless automation under upcoming work; iTechGuides describes Classic captions from imported transcripts. Treat those as distinct capabilities instead of promising an available agent-operated editor. Rewrite tracker, Classic caption description
Is OpenCut safe to use, and which website is official?
The official README points to opencut.app for Classic and new.opencut.app for the rewrite. That establishes project identity, not a security certification. The observed analytics request and the terms' browser-storage warning are relevant to deciding what material to bring into a session. Start with expendable footage if either affects your work. Official README, network observation, storage terms
What is the difference between OpenCut Classic and the rewrite?
Classic is the original, archived codebase and the version the official README recommends for editing today. The active repository is rebuilding the application around a Rust core with planned interfaces and platform support. A feature demonstrated in Classic and a milestone listed for the rewrite are different kinds of evidence. Classic README, rewrite README
Can OpenCut edit files from the filesystem rather than only a device's photo collection?
The Real Edit Test creator describes importing video clips and a music track, supporting a file-import workflow in that session. The Reddit question about filesystem access gets no detailed answer in its thread. Neither record supplies a device-by-device account of file-picker behaviour or access to every storage provider. Import demonstration, original question
Can I connect OpenCut to Claude as I can with Blender?
The rewrite tracker lists an MCP server for AI agents as future work. That is the relevant answer to the Reddit Claude-integration question, rather than an instruction to connect Classic to an already available endpoint. The supplied record provides no completed Claude editing session. Integration question, MCP roadmap
Does OpenCut offer transitions and advanced features beyond cutting?
Classic's documented release capabilities include masks, keyframe curves, speed and volume controls. The rewrite tracker separately lists transitions and filters as coming work. A Reddit reply says transitions exist, but that reply lacks a build-specific demonstration. Use the documented capability set for your selected version when deciding whether an effect is available. Classic profile, rewrite tracker, Reddit reply
Are OpenCut's desktop apps native or based on Electron?
The current desktop README names GPUI, and the rewrite issue also identifies GPUI in response to the Electron question. The same README says the application currently only opens a window. That describes the implementation and its early state without turning it into an available finished desktop editor. Desktop README, maintainer reply
What we have not tested yet
Our lab evidence covers a failed source build and a deployment attempt stopped by the runner's Compose requirement; we did not complete an editing or export session. The contradictory deployment summary needs reconciliation against raw run logs. No screenshots or known-answer editing questions accompany that attempt. The actual toolchain and operating-system versions also need those logs, and the linker failure has no follow-up run after a package change.
We have not tested memory growth against the footage in #628, long timelines, codec combinations, export resolution limits, audio synchronization, browser differences or GPU performance. The video transcripts contain third-party export reports, but they do not supply our own reproducible export matrix. No export timing in this review should be inferred from the source-build durations.
Caption accuracy, the enabled hosted transcription path and its network traffic remain untested by us. The analytics-script observation cannot settle what telemetry was collected. Editable-project backup and restore, device transfer and migration to the rewrite also need a completed recovery exercise. Claims about automatic preservation should wait for that result.
We have no completed mobile release evaluation, broad language inventory, localization contribution test, plugin compatibility test, headless render or Claude integration run. The separate naming-dispute issue contains conflicting assertions and no legal determination; it cannot decide ownership of similarly named sites for us. Naming thread
For a first decision, take a disposable clip through Classic and inspect the output before moving important work. Keep the source footage and a finished export outside browser storage. A successful short edit is a reason to consider that workflow; it is not a migration guarantee for the rewrite.


