How to uninstall Compositor on Mac

Compositor is a free, open-source image editor for Apple silicon Macs on macOS 26 or later, by Robbie Tilton, from robbietilton.com/compositor and its GitHub project. Its bundle ID is com.wonderassembly.compositor. Your work is in the project files you saved, and per the project's notes a .comp project is a folder of PNG layers and a manifest in a place you chose. Removing the app does not touch them, but check where you saved each one, because the app is sandboxed and a project saved into its own container goes with it. This guide covers the disk image from the project's GitHub release and the Homebrew cask robbietilton-compositor.

Check your projects, quit and remove the app

  1. Find your saved projects. In Finder, search for .comp, or look in the folders you normally save to. Anything that sits inside ~/Library/Containers/com.wonderassembly.compositor should be copied out first, and use Export As in the app for images you want as PNG, JPEG or PDF.
  2. Quit Compositor with Command + Q.
  3. Open Finder, go to Applications and drag Compositor to the Trash.

The app registered no login item or launch agent in the test.

Where the data lives

Press Shift + Command + G in Finder to open each path. Skip any path that is not on your Mac.

Location What it holds What to do
~/Library/Containers/com.wonderassembly.compositor The app's sandboxed files, such as its network cache and preferences; empty of your projects unless you saved into it Check it for projects, then remove. Mole selects it by default, and moving it needs Full Disk Access.
~/Library/Application Scripts/com.wonderassembly.compositor A folder macOS creates for sandboxed apps; empty in the test Remove. Selected by default.
The folder getconf DARWIN_USER_CACHE_DIR prints, plus com.wonderassembly.compositor Mole's temporary cache row, 90 KB in the test Remove. Selected by default.
~/Library/Application Support/Compositor Named in the Homebrew cask; Mole did not list it in the test Remove if it exists.
Your .comp projects and exports Your work Keep.

Volumetric Light downloads a depth model the first time you open it, per the README. Per its source (DepthModel.swift), the model goes into a Compositor/Depth Model folder under the app's Application Support; Compositor is sandboxed, so that folder sits inside ~/Library/Containers/com.wonderassembly.compositor and leaves with the container. The test did not use it.

Check the result

pgrep -il compositor
ls -d "$HOME/Library/Containers/com.wonderassembly.compositor" "$HOME/Library/Application Scripts/com.wonderassembly.compositor" "$HOME/Library/Application Support/Compositor"
ls -d "$(getconf DARWIN_USER_CACHE_DIR)com.wonderassembly.compositor"
  • No output from pgrep means Compositor is not running. A printed line is a process still alive; quit it.
  • A path printed by ls still exists. No such file or directory means that path is gone. The container is the one most likely to survive, see the test record below.

If the container survives, quit the app first. In Finder press Shift + Command + G, open ~/Library/Containers, and drag the folder to the Trash. macOS can refuse to move sandboxed data; if it does, give Mole Full Disk Access in System Settings › Privacy & Security › Full Disk Access and let it move the row, or remove the folder yourself later.

If you installed it with Homebrew

brew uninstall --cask robbietilton-compositor

The cask quits the app and removes it. Its zap list deletes the Application Scripts folder, ~/Library/Application Support/Compositor, the container, the Recent Items file and ~/Library/Preferences/com.robbietilton.Compositor.plist. Running brew uninstall --cask --zap robbietilton-compositor therefore deletes the container with whatever you saved in it and does not read Mole's checkboxes. Every zap path is inside ~/Library, but Mole adds --zap only when its whole removal scope passes its zap gate; a path the scan never listed, an unchecked row or a path another installed app claims keeps it off, and Mole then removes the rows you selected itself.

Account and subscription

Compositor needs no account and has no subscription (README).

What Mole lists

Mole selects the app, the Application Scripts folder, the container and the temporary cache row. Before removing, Mole asks the app to quit. Moving the container needs Full Disk Access; without it, Mole's report names Full Disk Access and offers a retry. It does not look inside the container for your projects, so check it yourself first.

What this test covered

On November 9, 2026, the test downloaded the Compositor 1.6.6 disk image (Apple silicon) from the project's GitHub release, whose checksum matched the Homebrew cask, copied the app to Applications without running brew install, launched it once, quit it and removed it with a source-built Mole with every review row ticked. No project was created. Mole moved the app, the Application Scripts folder and the temporary cache row to the Trash. The container stayed because the test build ran without Full Disk Access; macOS refused the move. The Recent Items file was left in place. Status showed one Compositor row with 4 processes, and Mole detected a Sparkle feed for the app; no update was run. Saving projects, Volumetric Light, the Homebrew uninstall and Mole's notarized release build were not tested.