How to uninstall 必剪 on Mac
Before removing 必剪, preserve editable drafts and their linked source video, audio and image files. An exported video is not an editable project. Use any draft-location control actually offered by your installed version to record its location, and COPY the complete editable drafts and linked materials to an independent location outside sync and all removal folders and verify the copies before cleanup. The official download page does not establish a Mac draft menu or default path; if the location cannot be established, keep the suspected workspace and do not run zap. The recorded test declined the terms, so it did not create a normal draft or verify Bilibili cloud uploads.
The recorded test used the official Mac package; the Homebrew route below is separate.
Remove the app
Quit BCUT and move BCUT.app from Applications to Trash. Leave your Movies folder and exported videos alone. If a Bilibili account has uploaded a video, inspect that account separately; removing the desktop app does not retract a publication.
Review local data
The path below was observed in the recorded test. In Finder, use Go › Go to Folder to inspect it. Do not remove its parent directory or another product’s data.
| Location | Decision |
|---|---|
~/Library/Containers/com.bilibili.bcutcreator |
A 156 KB container was observed in the official-package test; the removal hit a Trash permission error, so do not count it as removed. |
After quitting all BCUT copies, COPY the whole existing ~/Library/Containers/com.bilibili.bcutcreator container to an independent private backup outside all removal folders and verify it as well. Use Finder to remove only confirmed exclusive, unwanted BCUT items after backup; if macOS refuses, keep the failed path as remaining rather than claiming removal. Keep ~/Library/Group Containers/746845GC96.com.bilibili.bcutcreator while another installed owner uses it or ownership cannot be confirmed; it needs its own backup and individual decision. For a cask installation using cn.bilibili.bcut, inspect these exact cask paths separately and back up wanted state before trashing any confirmed own items; the differing identifier alone does not assign them to the tested package:
~/Library/Application Support/bcut~/Library/Caches/cn.bilibili.bcut~/Library/HTTPStorages/cn.bilibili.bcut~/Library/Logs/bcut~/Library/Preferences/cn.bilibili.bcut.plist~/Library/Saved Application State/cn.bilibili.bcut.savedState
The tested package uses bundle ID com.bilibili.bcutcreator. Review only files that actually appear on this Mac. A missing path needs no cleanup.
Vendor documentation · Additional vendor instructions
Check what remains
Run these read-only commands after quitting the app:
pgrep -il 'BCUT|必剪'
ls -d "$HOME/Library/Containers/com.bilibili.bcutcreator"
No process output means this process-name pattern did not match; also inspect Activity Monitor for confirmed app processes, and do not treat it as proof every helper is gone. A listed process needs its owner checked. If ls prints the path, that item remains and needs review. “No such file or directory” means this path is absent; a permission error means its state was not established.
If you installed it with Homebrew
The current bcut cask has a zap list covering a bcut support folder plus caches, HTTP storage, logs, preferences and saved state for the cask’s cn.bilibili.bcut identity. A direct brew command with --zap applies the cask list without consulting Mole’s checkboxes. After backing up, use this command without --zap:
brew uninstall --cask bcut
Mole checks each zap path against your selections, other installed apps, and protected locations. An unchecked, shared, or unverifiable path suppresses --zap; selected remnants can still use Mole’s own removal flow. This cask was not the recorded installation channel.
What Mole lists
Mole lists the official-package container when found and selects the exact-ID row by default; the 746845GC96.com.bilibili.bcutcreator app group requires individual review and is retained if another installed app claims it or the ownership check cannot confirm exclusive use. The Homebrew cask uses a different identifier, so review its zap paths as a separate channel.
What this test covered
On September 20, 2026, the official BCUT 3.11.24 app was opened and the terms were declined, then review rows were selected for uninstall. The 156 KB container was not moved because Trash returned error 513. No draft, source-media folder, upload or signed-in account was tested.