How to Uninstall AppFlowy on Mac

AppFlowy can hold a local workspace even without signing in. Before removing the app, find the data folder used by this installation, using the app's settings if available, then copy it to a safe location and verify the copy rather than assuming cloud sync. The recorded test used a direct download, not a Homebrew installation.

Remove the app and inspect its data

Quit AppFlowy and move AppFlowy.app from Applications to Trash. The downloaded archive in the test was named AppFlowy-arm64.app and copied as AppFlowy.app; do not confuse the package name with the data folder. The cask zap names a macOS container and scripts, while AppFlowy's user-data documentation describes local storage. Check the actual folder used by this installation before any broader cleanup.

Check the result

ls -ld ~/Library/Containers/com.appflowy.macos ~/Library/'Application Scripts'/com.appflowy.macos

Run this read-only check after quitting the app. A printed path still exists; “No such file or directory” means that path is absent, while a permission error needs its own investigation.

If you installed it with Homebrew

The Homebrew cask has a zap list that includes the cask-listed macOS scripts and container; that list does not establish the location of this installation’s user workspace. Run the command below without --zap if you want to keep those files and inspect them separately. A manual --zap follows the whole cask list regardless of Mole’s checkboxes. Mole uses zap only when its targets are selected, owned and within the checked boundary; otherwise it removes selected remnants through its own flow.

brew uninstall --cask appflowy

What Mole lists

Exact installed bundle-ID rows are normally selected. A separate com.appflowy.macos container or app data folder needs ownership and user-data review; do not assume that a different bundle ID proves ownership or safe removal.

What this test covered

The official arm64 archive was copied as AppFlowy.app and removed on September 20, 2026. No account, populated local workspace, sync or restore was tested.