CutVibe: Video Editor & Eraser

Opening CutVibe for the first time

Install the app, grant storage permissions, and pick a video from your gallery. The interface loads a timeline with a prominent "eraser" icon at the bottom. Tap it, and a brush tool appears. You circle a person walking through your shot, lift your finger, and the app processes for a few seconds. The person vanishes, replaced by a patch of background that looks acceptable at a glance. This is the core promise of CutVibe, and for many users, it works exactly as advertised. The eraser handles logos, text overlays, and even moving objects with surprising speed. Yet the moment you try to export that polished clip, the experience can shift dramatically.

Exporting a video is where the app's real behavior becomes visible. Some users report that the export button does nothing, or that the process stalls at 100% and never finishes. Others see a "no internet connection" error despite being online. These issues are not rare. They appear across multiple reviews and forum discussions, and they point to a fundamental instability in the app's rendering pipeline. The eraser may be clever, but the output stage is fragile. This tension between a powerful editing tool and a brittle export system defines the CutVibe experience more than any single feature.

The eraser and the enhancer: a workflow that fights itself

CutVibe includes two features that seem designed to work together: the AI object eraser and the video quality enhancer. In practice, using them in sequence reveals a clash. You erase a watermark from a low-resolution clip, then run the enhancer to sharpen the result. The enhancer sometimes amplifies the patchy artifacts left by the eraser, making the edited area look worse than the original. The eraser fills gaps with surrounding pixels, but the enhancer treats those filled pixels as real detail and tries to sharpen them, often creating a blocky or smeared effect. This is not a bug per se, but a consequence of two independent AI models operating on the same frame without coordination.

Users who stick with the app learn to work around this. They erase first, then apply a subtle blur to the edited area before running the enhancer. Or they export at a lower resolution to hide the imperfections. This is not documented anywhere in the app's description. It emerges from trial and error, and it suggests that the developers have not fully integrated these two features. The eraser and the enhancer are powerful individually, but together they create a workflow that requires manual intervention to avoid degrading the final output.

Real-world performance: ads, crashes, and the subscription wall

CutVibe is free to download, but it pushes users toward a subscription. The free version limits export quality and adds a watermark. The subscription removes these limits, but it does not fix the underlying stability problems. Users who pay still encounter the same export failures and permission errors. The app requests location and storage permissions, and some users report that even after granting them, the app continues to ask, as if it cannot verify the grant. This suggests a flaw in the permission-handling logic, possibly tied to the app's reliance on external libraries for video processing.

Crashes are common during the export phase. The app may close without warning, losing the user's edits. This is particularly frustrating because the editing process itself is smooth. Scrubbing through the timeline, applying filters, and adjusting speed all work without lag. The instability only surfaces when the app tries to render the final video. This pattern points to a memory or resource management issue during encoding. The app may be trying to apply too many effects at once, or it may not handle out-of-memory conditions gracefully. Whatever the cause, the result is the same: a video that looks great in preview but fails to save.

The audio editor and auto-subtitle features are more reliable. Adding background music, adjusting volume, and generating captions work as expected. These features do not seem to trigger the same crashes, possibly because they involve less intensive processing than the eraser or enhancer. This creates a curious split: the app is stable for basic edits but unstable for its headline features. Users who only trim and add music may never encounter a problem. Those who rely on the eraser are the ones who suffer.

Export settings and the missing changelog

CutVibe offers export resolutions up to 1080p, but the actual output quality varies. Some users report that even at 1080p, the video looks soft or pixelated. The app's enhancement feature can improve this, but as noted, it can also introduce artifacts. The optimal workflow appears to be: erase, export at 720p, then use a separate app for enhancement. This is not ideal, but it reflects the reality of using CutVibe today. The developer has not published a changelog for recent versions, so it is unclear if these issues are being addressed. The last update notes simply say "bug fixes and performance improvements," which is too vague to indicate any specific progress. Without detailed release notes, users have no way to know if a new version will fix their particular problem. The export failures and permission errors have been reported across multiple versions, suggesting that they are not trivial to resolve.