# Figma Cache on Mac: Check Offline Work Before a Reset

> Use Figma's current cache reset, check unsynced edits first, and distinguish desktop data from FigmaAgent and app removal.

Published: 2026-07-13 | Updated: 2026-10-31

If Figma works in a browser but the desktop app keeps misbehaving, try Figma's own cache reset before reinstalling. First reconnect and verify that recent edits have saved, because local Figma storage can include offline changes, not just replaceable downloads.

## Decide What Needs Resetting

Use the same design and account to compare the browser and desktop app. Record the failing action so you can repeat it after one change.

| What you see | What to check | First action |
| --- | --- | --- |
| A problem only in the desktop app | Whether recent edits have saved | Consider the desktop reset |
| Missing local fonts in the browser | The font installer and its connection | Check FigmaAgent separately |
| Changes made without a connection | Whether they have synced | Reconnect before clearing anything |
| You no longer want the desktop app | Whether browser fonts are still needed | Plan an uninstall separately |

Figma recommends cache clearing for [technical problems limited to its desktop app](https://help.figma.com/hc/en-us/articles/22380853110551-Clear-the-Figma-desktop-app-cache). That is a troubleshooting step, not evidence that every slow design has a cache problem.

## Save Offline Work Before Signing Out

Figma's [offline-work guide](https://help.figma.com/hc/en-us/articles/360040328553-What-can-I-do-offline-in-Figma) warns that clearing local data can delete changes that have not synced. Reconnect, open affected files and confirm the saved changes before a reset.

Signing out is not a harmless substitute. The desktop app can offer a choice about offline changes, and choosing to discard them cannot be undone. Cancel if you cannot establish that the work has saved. Synchronization is not an independent backup.

## Use Figma's Reset Menu First

The current [cache instructions](https://help.figma.com/hc/en-us/articles/22380853110551-Clear-the-Figma-desktop-app-cache) name the English menu labels below. They are in the Mac's top application menu bar, not the menu inside a design.

1. Finish the save checks above.
2. Open **Help**, then **Troubleshooting**.
3. Choose **Reset Figma and Restart**.
4. Reopen the same design and repeat the failing action.

If it works, stop there. If the browser also has the problem, do not keep resetting the desktop app without new evidence.

## Locate the Data When the App Will Not Respond

Figma's current manual reset targets this entire local support folder:

```text
~/Library/Application Support/Figma
```

Its documented Terminal command is:

```sh
rm -rf "$HOME/Library/Application Support/Figma"
```

The [official sequence](https://help.figma.com/hc/en-us/articles/22380853110551-Clear-the-Figma-desktop-app-cache) is to force quit Figma, run that command, then launch it again. This is a broad local reset, not a cache-only child-folder deletion, and the command does not provide a Trash recovery step. Do not run it with unsynced work or without accepting the loss of that folder's contents.

For the general distinction between cache and retained app data, see [which Mac caches are safe to delete](https://mole.fit/blog/which-mac-caches-are-safe-to-delete). Do not expand this command to the parent Application Support folder.

## Check the Font Helper Separately

Figma's [font-installer troubleshooting](https://help.figma.com/hc/en-us/articles/32801027692183-Troubleshoot-the-Figma-Font-installer) identifies the background helper as FigmaAgent. It is included with the desktop app and can also be installed separately for browser use.

A browser font problem is a reason to check that helper's connection, not to erase desktop data repeatedly. Figma's [font guide](https://help.figma.com/hc/en-us/articles/360039956894-Add-a-font-to-Figma) says removing the font installer removes access to local and Adobe fonts in Figma. Keep the font files themselves.

## Check the Result Before Removing the App

After restarting, confirm account access, recent edits and the original failing action. Reloaded content requires an available source and access to it, so do not assume a reset can recreate unsynced work.

If the goal is removal rather than repair, use the [Figma uninstall guide](https://mole.fit/tested-apps/figma), which separates the app, local support data and helper. A helper that remains running is a different question from cache size, covered in [apps still running after uninstall](https://mole.fit/blog/app-still-running-after-uninstall-mac).

## Where Mole Fits

Mole Mac's **Clean** view has a **Design Tools** entry for `~/Library/Application Support/Figma/Cache` when that folder exists and is eligible. That exact child folder is narrower than Figma's full reset above. Use Figma's own reset for the documented troubleshooting procedure, and confirm offline work has saved before selecting local data for cleanup.

## FAQ

### Can Clearing Figma's Cache Lose Work?

Yes, unsynced offline changes can be lost when local data is cleared. Reconnect and verify them before resetting, rather than relying on being signed in.

### Is FigmaAgent the Cache?

No. It is the helper used for local-font access, and it can be installed for browser use separately. Diagnose its connection separately from desktop cache.

### Should I Sign Out or Reinstall First?

Neither is the first cache step. Save the work, try the documented reset once, then compare the result. Do not choose to discard offline changes just to get past a sign-out prompt.

---

Canonical HTML page: https://mole.fit/blog/figma-cache-mac
Blog index for agents: https://mole.fit/blog/llms.txt
Site index for agents: https://mole.fit/llms.txt