How to Clean Figma Desktop Font, Canvas & GPU Cache

🟢 100% Safe to Delete Typical Space Reclaimed: 1.0 GB – 6.0 GB

Location & Quick Verdict

%AppData%\Figma\Cache and %AppData%\Figma\Code Cache

Figma's Electron desktop app caches high-DPI design canvases, vector assets, and WebGL textures locally on your drive.

Safety confirmation: 100% safe to delete because all Figma files live in the cloud. Clears local disk bloat and fixes canvas WebGL memory errors.

How Timeline Previews, Conform Audio & Render Scratch Fill Figma Desktop Font, Canvas & GPU Cache

Non-linear video editors (NLEs), streaming encoders, 3D DCC tools, and DAWs continuously write uncompressed audio conform files (.cfa), waveform peak indexes (.pek), proxy transcodes, and frame-accurate undo scratch into %AppData%\Figma\Cache and %AppData%\Figma\Code Cache. Even after you finish exporting and archiving a client project, gigabytes of intermediate timeline render caches remain permanently allocated on your scratch disk.

On 4K/8K timelines or multi-scene streaming setups, Figma Desktop Font, Canvas & GPU Cache routinely consumes 1.0 GB – 6.0 GB of high-speed SSD space. Safely pruning stale media caches reclaims scratch bandwidth immediately; if you ever reopen an older project file, the application simply regenerates audio waveforms and timeline previews in the background.

PowerShell Size Verification (Read-Only Check):
# Inspect current disk footprint of Figma Desktop Font, Canvas & GPU Cache (Read-Only)
$target = "$env:APPDATA\Figma\Cache"
Get-ChildItem -Path $target -Recurse -Force -ErrorAction SilentlyContinue |
  Measure-Object -Property Length -Sum |
  Select-Object Count, @{Name="SizeGB";Expression={[math]::Round($_.Sum / 1GB, 2)}}
🛡️ What Stays 100% Protected Project files (.prproj, .drp, .blend, .als), original camera footage, exported renders, LUTs, plugins, and scene collections are never touched.
⚡ What Gets Safely Removed Conformed audio (.cfa), waveform peaks (.pek), orphaned timeline render previews, browser-source CEF caches, and crash minidumps.

Manual Cleaning Instructions

  1. 1 Quit the Figma desktop app.
  2. 2 Press Windows Key + R, type %appdata%\Figma and press Enter.
  3. 3 Delete the 'Cache', 'Code Cache', and 'GPUCache' folders.

Note: If Windows alerts that a file is in use or locked by a background process, close the associated task in Task Manager before deleting, or use SWEEPR Cleaner to release locked handles safely.

Sub-Folders & Cache Locations Breakdown for Figma Desktop Font, Canvas & GPU Cache

Modern Windows applications and system services split their disk footprint across multiple sub-directories (`Cache_Data`, `Service Worker\CacheStorage`, `Code Cache`, `GPUCache`, and `Crashpad\reports`). Review which sub-folders inside Figma Desktop Font, Canvas & GPU Cache are safe to purge and which files remain protected:

Sub-Folder / Cache Location Storage Role Typical Footprint Deletion Safety
%AppData%\Figma\Cache Primary Media Cache, Proxy Scratch & Render Previews 1.0 GB – 6.0 GB 🟢 100% Safe (Re-renders on Demand)
%AppData%\Figma\Cache\Media Cache Files (*.cfa, *.pek) Conformed Audio Waveforms & Timeline Peak Files 2.0 GB – 25.0 GB 🟢 100% Safe
%AppData%\Figma\Cache\GPUCache & Code Cache Hardware-Accelerated Viewport & UI Plugin Cache 300 MB – 3.0 GB 🟢 100% Safe
%AppData%\Figma\Cache\logs & Crashpad\reports Render Session Logs & Crash Dump Archives (.dmp) 200 MB – 4.5 GB 🟢 100% Safe
Project Timelines (.prproj / .drp / .blend) & LUTs Source Footage, Edit Timelines, Presets & Exported Renders Protected 🔒 Protected — Never Touched

Frequently Asked Questions

Is it safe to delete Figma Desktop Font, Canvas & GPU Cache?

Yes, 100% safe. 100% safe to delete because all Figma files live in the cloud. Clears local disk bloat and fixes canvas WebGL memory errors.

How much storage space will cleaning Figma Desktop Font, Canvas & GPU Cache free up?

Users typically reclaim 1.0 GB – 6.0 GB on Windows 10 and Windows 11 systems depending on update frequency and active cache retention in %AppData%\Figma\Cache and %AppData%\Figma\Code Cache.

Will clearing Figma Desktop Font, Canvas & GPU Cache delete my video projects, drafts, or saved recordings?

No. Project timelines, source media clips, and exported videos are stored in your project folders—not in %AppData%\Figma\Cache and %AppData%\Figma\Code Cache. If you reopen an active project after cleaning, the software automatically rebuilds any needed waveform peaks or preview frames.

Where is Figma Desktop Font, Canvas & GPU Cache located on Windows 10 and Windows 11?

It is stored at %AppData%\Figma\Cache and %AppData%\Figma\Code Cache. You can paste that path directly into the Windows Run dialog (Win + R) or File Explorer address bar to inspect it.

Manual File Explorer vs. 1-Click SWEEPR Cleanup

Feature Manual Deletion SWEEPR Cleaner
Locked File Handling Fails on locked processes Safe background release
Accidental Deletion Risk Moderate (easy to delete wrong folder) Zero (strict rules & hashes)
Safety Undo Rollback None (Shift+Del is permanent) 7-Day Automatic Rollback
Time Required 10–20 minutes per app < 60 seconds across 40+ areas

Related Windows Cleanup Guides & Hidden Space Hogs

Clean Figma Desktop Font, Canvas & GPU Cache Automatically

SWEEPR Cleaner safely clears Figma Desktop Font, Canvas & GPU Cache along with 40+ other hidden app folders and leftover files in one click—covering up to 5 devices (Windows, Mac, Android & iOS) with a 7-day undo safety net.

🛡️ Windows 10/11 First-Launch Walkthrough: Because v0.1.0 is a freshly compiled 5 MB native Rust app, if Windows SmartScreen appears: Step 1: Click "More info" → Step 2: Click "Run anyway".