Figma
Figma Desktop stores Chromium disk cache entries in Cache/Cache_Data for web assets, API responses, fonts, images, and embedded editor resources, and on Windows it also keeps a GPUCache with compiled shader data and other accelerated rendering artifacts. These files help the Electron-based app load design files and interface elements faster, but they can become stale after app updates, account changes, or graphics driver changes. Kudu removes only Figma’s disposable disk cache and GPU cache so the app can rebuild fresh copies without touching drafts, team files, plugins, settings, or sign-in data.
Why clean Figma?
- Outdated Chromium cache entries can leave the desktop app showing old UI assets or partial editor loads after a Figma update, with missing icons, blank sidebars, or panels that never finish rendering
- Corrupted cached API responses can make recent files, comments, or team thumbnails appear stuck or incomplete until the local cache is rebuilt from the server
- A bloated Cache_Data folder slows Figma startup and workspace switching because the app spends longer scanning and validating old web resources before fetching fresh ones
- On Windows, stale GPUCache shader data from a previous graphics driver version can cause canvas flicker, black regions, or stuttering zoom and pan until the accelerated cache is regenerated
- Cached font and image resources can get out of sync with current documents, leading to wrong previews, delayed thumbnail loading, or assets that only appear after a hard refresh
- Repeated editor updates can leave behind invalidated Electron cache files that waste disk space while contributing to one-time slow launches and longer file open times as Figma falls back to rebuilding them
Cache paths Kudu targets
Windows
%AppData%/Figma/Cache/Cache_Data |
%AppData%/Figma/GPUCache |
macOS
~/Library/Application Support/Figma/Cache/Cache_Data |
Common questions about Figma
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.