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
Before quitting, open Settings › Manage data › File storage location and click the displayed path to open the actual data folder, then record its full location. The current official source implements this entry. If your version does not offer it or you cannot establish the workspace location, keep the suspected workspace and do not run zap.
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.
The developer documentation describes relative flowy or data storage names, not an absolute workspace path for this Mac. After quitting, copy the entire confirmed workspace and the existing owned container below to an independent private backup outside all removal folders, then verify the copies. In Finder, press Shift + Command + G to inspect these cask-listed paths and move only confirmed exclusive, unwanted AppFlowy items to the Trash; do not infer that the container is the only workspace copy:
~/Library/Application Scripts/com.appflowy.macos~/Library/Containers/com.appflowy.macos
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 skips --zap when its list reaches unchecked or shared data, or a removal scope it cannot verify; selected remnants still follow Mole's own removal 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.