Uninstall 优酷 on Mac

Check wanted offline videos and downloads in 优酷 before removing the client. An online membership and local cached media have different lifetimes. The September 20, 2026 record covers the app copied from the official package.

Quit and remove the app

Quit playback and all 优酷 processes, then move 优酷.app to Trash. Manage any subscription through the purchase channel rather than expecting app deletion to cancel it. The official page has more product information.

Review the app’s data

The cask lists ~/Library/Application Support/youku-app, exact com.youku.mac cache, container, scripts and preferences. youku-app is a product-specific but non-bundle name; review its contents before removal.

If you installed it with Homebrew

The Homebrew cask has its own --zap list. brew uninstall --cask youku removes the cask without that list; brew uninstall --cask --zap youku also acts on its listed data without consulting Mole’s checkboxes. Zap includes both youku-app and the container, which may hold offline state. Mole also suppresses zap if its list would cross an unchecked, shared, unknown, or unsupported path; selected remnants still follow Mole’s own deletion path.

brew uninstall --cask youku

Check the result

These commands inspect the running process and one relevant location. They do not remove anything:

pgrep -il "优酷"
ls -ld "$HOME/Library/Containers/com.youku.mac"

No pgrep match means no process with that name is running; a match needs identification before quitting anything. A listed path still exists, while an ls “No such file” error means only that exact path is absent. A permission error is inconclusive.

What Mole lists

Mole lists Application Support/youku-app as a review row, initially unchecked. Exact bundle-ID cache and preferences can be selected by default; a container move can still fail at the Trash sink.

What this test covered

The September 20, 2026 official-package test found a separate youku-app folder after the main removal, while the 108 MB container failed to move to Trash with error 513. The container may still be present. If the check above lists it, keep wanted offline files and inspect the permission error before deciding whether to remove it; complete local-data removal was not verified.