Uninstall Figma on Mac

Open your recently edited designs in Figma on the web and confirm that changes have synced. Save unsynced work and local exports, then quit Figma and move it from Applications to the Trash. These steps cover the official download and the Homebrew cask. Removing the desktop app does not delete files in your Figma account or cancel a paid plan; plans are managed in your Figma account.

Quit Figma and FigmaAgent

Figma installs a helper called FigmaAgent (com.figma.agent) at ~/Library/Application Support/Figma/FigmaAgent.app, which is how Figma reaches the fonts installed on this Mac. Quit Figma, then check Activity Monitor for figma_agent and quit it too. The helper is not inside Figma.app, so moving the app to the Trash leaves it in place; it goes away only when ~/Library/Application Support/Figma is removed. The Homebrew cask also quits com.figma.agent when it uninstalls. A FigmaAgent entry can remain in System Settings › General › Login Items & Extensions after the app is gone; switch it off there.

If you still use Figma in a browser with local fonts, open a design that uses one and check its rendering after removing the desktop app. Figma font help

Where Figma keeps local data

Keep local exports, images and font files; they are not app leftovers. In Finder, press Shift + Command + G and open each location that exists.

These paths come from the Homebrew Figma cask's cleanup list. Not every Mac has every entry.

Check the result

Run these read-only commands in Terminal:

pgrep -ilf "Figma"
launchctl list | grep -i figma
ls -d "$HOME/Library/Application Support/Figma"

No output from pgrep means neither Figma nor FigmaAgent is running; a line with a process ID means one is still open. No output from launchctl list means no Figma job is loaded for your account. A remaining line means a job is still registered; if the app is already gone, switch off its login item and restart. For ls, "No such file or directory" means the folder is gone; a listed path still exists.

Finally, confirm that web designs still open and local exports remain usable. If recent edits are missing on the web, investigate sync and account access before clearing local support data.

If you installed it with Homebrew

Mole skips --zap when its list reaches unchecked or shared data, or cannot be fully checked, and still cleans the leftovers you selected.

Running brew uninstall --cask --zap figma yourself runs the cask's zap list on its own, whatever you selected in Mole. It includes ~/Library/Application Support/Figma, ~/Library/Application Support/figma-desktop, both caches and the preferences. It does not touch designs in your account or exports in your own folders. Homebrew Figma cask

To keep the support folders:

brew uninstall --cask figma

What Mole lists

~/Library/Application Support/Figma, which also holds FigmaAgent.app, is listed but not selected. The cache, preferences and window state named com.figma.Desktop, and the FigmaAgent cache and HTTP storage, are selected by default. If you tick ~/Library/Application Support/Figma, Mole also stops the figma_agent still running from it after moving the folder to the Trash.

What this test covered

The recorded uninstall used the Homebrew cask on September 17, 2026, so Homebrew's zap list removed the files. Afterwards the FigmaAgent login entry was still registered with macOS, pointing at the removed app. Account files and paid plans were not part of the test.

On September 26, 2026, Figma was installed again from the official package, opened once, and uninstalled with a development build of Mole with every listed row ticked. Status showed one Figma row of ten processes at about 272 MB. Thirteen items went to the Trash, ~/Library/Application Support/Figma with FigmaAgent.app among them, and nothing from the list was left; the FigmaAgent login item was gone afterwards. That build did not yet stop figma_agent, which kept running from the Trash until logout.