How to uninstall FilmCraft on Mac

This guide covers the FilmCraft Mac DMG from the ArtCraft website. Save projects, source media and exported videos first. Copy wanted files outside the app-data directory and open the copies before quitting. Separately installed command-line tools are outside this desktop uninstall’s scope.

Remove the desktop app

Press Command + Q in FilmCraft, wait for saving to finish, then move FilmCraft.app from Applications to Trash. Keep Trash available until you have confirmed that your wanted files still open.

Review local data

These locations appeared during this installation and first launch; they are not a vendor-published inventory. Inspect them individually with Shift + Command + G in Finder and trash only data you no longer need. Keep projects and original assets wherever you saved them.

Path	Observed contents or role
`~/Library/Application Support/FilmCraft`	App data and settings

Check the result

if [ -e "/Applications/FilmCraft.app" ]; then
  printf '%s\n' 'App bundle still exists'
else
  printf '%s\n' 'App bundle not found at this path'
fi
ls -ld "$HOME/Library/Application Support/FilmCraft"

The first check reports whether the app remains at that exact location. An ls listing means that path remains; No such file means it is absent, while Permission denied leaves its state unknown. An absent app bundle does not establish removal of projects, other app copies or a separate CLI.

What Mole lists

Mole lists the app and the system temporary cache observed in this test. The cache is selected by default.

With app-data selection off, ~/Library/Application Support/FilmCraft is listed but not selected. Select it only after reviewing its contents; opting into app-data selection also selects eligible app data.

What this test covered

On October 8, 2026, FilmCraft 0.2.1 was installed from the official Universal DMG. The test opened the built-in demo and displayed its timeline, then removed the app and selected test data with Mole. Status grouped it into one app row, and no corresponding persistent background job was observed after quitting. The update scan did not identify an update channel; that does not establish that no newer release exists. No personal files were imported, and full editing workflows, cloud sync and independent CLIs were not tested.