# How to Clear Figma Cache on Mac and Windows

> Check Figma cache sizes and paths with MangoDisk, confirm your edits have synced, and learn how clearing selected caches differs from resetting the desktop app.

**You can clear known Figma cache folders, but check that your design changes have synced first.** Caches used to load pages and render graphics are different from locally stored, unsynced edits. Do not treat Figma's entire data folder as disposable cache.

If you want to free disk space, [MangoDisk](/) can scan locally and show supported cache paths and sizes before you choose what to remove. If the desktop app will not open or pages fail to load, Figma's reset option may be more relevant. These operations affect different sets of data.

## Separate caches from design data

Figma stores offline changes locally until they can sync. Clearing the relevant local data before that happens can lose those edits. Having a file in the cloud does not mean every recent change is already there. [Figma's offline guidance](https://help.figma.com/hc/en-us/articles/360040328553-What-can-I-do-offline-in-Figma)

MangoDisk's Deep Cleanup uses specific path rules rather than selecting the entire Figma data folder. In **v1.1.7**, the published rules cover these locations:

<table>
<thead>
  <tr>
    <th>
      System
    </th>
    
    <th>
      Item in MangoDisk
    </th>
    
    <th>
      Matching locations
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      macOS
    </td>
    
    <td>
      Figma cache
    </td>
    
    <td>
      <code>
        ~/Library/Caches/com.figma.Desktop
      </code>
      
      , plus <code>
        Cache
      </code>
      
      , <code>
        Code Cache
      </code>
      
       and <code>
        GPUCache
      </code>
      
       directly under <code>
        ~/Library/Application Support/Figma/
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      Windows
    </td>
    
    <td>
      Desktop app cache
    </td>
    
    <td>
      Specified subfolders under <code>
        %APPDATA%\Figma
      </code>
      
       and <code>
        %LOCALAPPDATA%\Figma
      </code>
      
      , including <code>
        Cache
      </code>
      
      , <code>
        Code Cache
      </code>
      
       and <code>
        GPUCache
      </code>
      
      ; the rule also includes certain log and crash-report folders
    </td>
  </tr>
</tbody>
</table>

These rules do not target account data, settings, `Local Storage`, `IndexedDB` or design files you have exported. **Desktop app cache** on Windows also covers other apps, so expand the results and select only the Figma paths you intend to clean. You can inspect the [macOS rule](https://github.com/harry0703/MangoDisk/blob/v1.1.7/src-tauri/crates/mangodisk-core/rules/filesystem/macos/application/app.figma-cache.toml) and [Windows rule](https://github.com/harry0703/MangoDisk/blob/v1.1.7/src-tauri/crates/mangodisk-core/rules/filesystem/windows/application/app.electron-cache.toml).

Smart recommendation can already have selected eligible results from these rules after scanning. Choose **Select none** before selecting the Figma caches you intend to clean.

Figma's folder layout can vary by version. This table describes MangoDisk's matching rules, not every cache location that every Figma version might use. A folder with the same name elsewhere is not automatically covered by the same cleanup guidance.

## Sync your changes before quitting Figma

Connect to the internet and open files you have recently edited. If Figma reports unsynced changes, follow the prompt to open the affected files and wait for saving to finish. If you cannot confirm that the changes have synced, keep the local data and postpone cleanup or reset.

Once saving is complete, quit the Figma desktop app before scanning. Avoid editing a file while its app data is being cleaned.

## Review cache usage with MangoDisk

Open **Deep Cleanup**, run a **Standard Scan**, and check **Application caches**.

![MangoDisk Deep Cleanup in English on macOS, showing cache categories and cleanup selections](https://assets.mangodisk.app/images/screenshots/en/light-01-deep-cleanup.jpg)

*This is a macOS interface example, not a Figma scan or cleanup result. The displayed sizes do not show how much space Figma can free.*

After scanning:

1. Choose **Select none** to clear existing selections and avoid cleaning other apps along with Figma.
2. On Mac, expand **Figma cache**. On Windows, expand **Desktop app cache** and find the paths belonging to Figma.
3. Check each path and its size, then select the caches you want to remove. You can leave logs and crash reports unselected if you only want to clear caches.
4. Review the selected items and total size. If MangoDisk lists related apps that are still running, save your work and quit them before confirming cleanup.

A scan alone does not delete files. Cleaning the caches covered here **permanently deletes the selected contents**, bypassing the Trash or Recycle Bin. Do not use deletion as a trial you expect to undo. See the [Deep Cleanup documentation](/docs/features/deep-clean) and [safety guide](/docs/safety) before proceeding.

Caches can grow again as you use the app. Decide whether to clear them based on their actual size rather than trying to keep them empty. Scanned sizes are not proof of space recovered; check the cleanup result for that.

## Use Figma's reset option for app problems

For desktop loading problems, Figma provides **Reset Figma and Restart**. Its current instructions give these menu paths:

- **macOS:** open **Help → Troubleshooting → Reset Figma and Restart** in the system menu bar.
- **Windows:** open the drop-down arrow at the top right of the app toolbar, then choose **Help → Troubleshooting → Reset Figma and Restart**.

An app reset is different from removing just the cache folders listed above. Figma's manual steps for an unresponsive app also affect a broader set of local data, so do not delete the whole data folder merely to reclaim disk space. Check that your edits have synced before resetting, too. Follow [Figma's desktop cache instructions](https://help.figma.com/hc/en-us/articles/22380853110551-Clear-the-Figma-desktop-app-cache) for the full procedure.

If the problem remains, continue with [Figma's troubleshooting checklist](https://help.figma.com/hc/en-us/articles/360040523973-Troubleshooting-checklist) rather than repeatedly deleting folders whose purpose you have not confirmed.

## If no cache appears or disk space is still low

An empty result can mean the matching paths do not exist, your Figma version uses a different layout, or the scan could not read a location. **No matching cache result does not mean Figma has no local data.** Do not expand the cleanup to the entire `Application Support/Figma` or Figma folder in AppData, or to `DesktopProfile`.

If Figma's caches are small, resetting the app may do little for your available space. Use [Disk Space Analysis](/docs/features/disk-analysis) to compare other folders, then review large exports, recordings or old files you recognize.

For a broader investigation, see [what takes up System Data on Mac](/blog/mac-system-data-too-large) or [how to review large AppData folders on Windows](/blog/windows-11-appdata-too-large). Those locations also need inspection rather than wholesale deletion.

MangoDisk is a free, open-source disk cleanup and space analysis tool for macOS, Windows and Linux. The Figma desktop steps here cover Mac and Windows. [Download MangoDisk](/), or inspect its source and cleanup rules on [GitHub](https://github.com/harry0703/MangoDisk), to review disk usage before deciding what to remove.