How to uninstall Figma on Windows
Open your recently edited designs in Figma on the web and confirm that changes have synced before you uninstall the desktop app; removing it never deletes files in your Figma account or cancels a paid plan, those are managed on the web. This guide covers Figma installed per-user from the Figma.Figma winget package.
Quit Figma and Figma Agent
Figma installs a helper called Figma Agent, which is how Figma reaches the fonts installed on this PC. Quit Figma, then check Task Manager (Ctrl+Shift+Esc) for Figma.exe and figma_agent.exe. Figma Agent also runs at sign-in as its own startup entry (Settings › Apps › Startup); uninstalling the app removes that entry too.
Remove the app with its own uninstaller
Go to Settings › Apps › Installed apps, find Figma, and choose Uninstall, or run:
winget uninstall --id Figma.Figma
Where the data lives
| Location | What it holds | What to do |
|---|---|---|
%APPDATA%\Figma |
Desktop app settings and local storage | Back this up first; the uninstaller does not remove it |
%LOCALAPPDATA%\FigmaAgent |
The Figma Agent helper and its own cache | Safe to remove once you no longer need local fonts in Figma |
Local exports, images and font files you saved yourself are not part of either folder; they stay wherever you put them.
Check the result
Run these read-only commands after the uninstall finishes:
Get-Process Figma, figma_agent -ErrorAction SilentlyContinue
winget list --id Figma.Figma
Test-Path "$env:LOCALAPPDATA\Figma"
Test-Path "$env:APPDATA\Figma"
Test-Path "$env:LOCALAPPDATA\FigmaAgent"
- No output from
Get-Processonly means this query observed no matching process; a suppressed error leaves the running state unknown. A listed process means one is still open. - A completed
winget listquery with no match means the package record is gone; a matching row means the uninstall did not finish. - The first
Test-PathreturningFalsemeans the program folder is gone;Truemeans files remain there. Test-Path "$env:APPDATA\Figma"returningTruemeans your settings and local storage are still there, which is expected unless you removed them yourself.Test-Path "$env:LOCALAPPDATA\FigmaAgent"returningTruemeans the font helper's own folder is still there; remove it yourself if you want a clean start.
Finally, confirm your web designs still open and local exports remain usable. If recent edits are missing on the web, look into sync and account access before clearing local data.
If you installed it with winget
winget uninstall runs the same Squirrel uninstaller (Update.exe --uninstall -s) Settings › Apps uses and removes the same program files; it does not touch %APPDATA%\Figma or %LOCALAPPDATA%\FigmaAgent on its own.
What Mole lists
For Figma installed per-user from winget:
- The program folder and the Start Menu shortcut are selected by default.
%APPDATA%\Figmais listed but not selected, since it holds your settings and local storage.%LOCALAPPDATA%\FigmaAgentis listed but not selected; in this test the uninstaller had already removed it before Mole's own step ran.- If a
figma://link registration still points at the removed program, Mole lists it too and backs it up to a.regfile before removing it. - File type registrations for
.deckand.jamare left alone, since other apps can share them.
What this test covered
Tested with Figma installed through winget, per-user scope, using its Squirrel uninstaller. Status showed one row of seven Figma.exe processes plus a separate Figma Agent row. The uninstaller removed the Figma Agent startup entry on its own. Every listed row was ticked and removed in this test. Not verified: a signed-in account or a local font used through Figma Agent.
