How to uninstall Postman on Windows
Check whether you are signed in to a Postman account before removing the app: collections and environments already synced to your account can be reopened after reinstalling, but anything you built while signed out lives only in this PC's local folder and is gone once that folder is deleted. This guide covers Postman installed per-user from the Postman.Postman winget package, which installs the same app as Postman's own download.
Check what is local-only before removing anything
Open Postman and look at whether you are signed in, top right. If you are not signed in, everything you built lives only on this PC; sign in and verify the wanted data in the web app before relying on account sync, or treat the local folder below as the only copy you have. Postman's guide to the offline API client explains what still works without an account or network connection.
Quit Postman first
Finish or cancel any running requests, then quit Postman from its window or tray icon. Postman runs several processes, one per window plus helpers, so check Task Manager (Ctrl+Shift+Esc) for any Postman.exe still listed before you uninstall.
Remove the app with its own uninstaller
Go to Settings › Apps › Installed apps, find Postman, and choose Uninstall, or run:
winget uninstall --id Postman.Postman
Where the data lives
| Location | What it holds | What to do |
|---|---|---|
%LOCALAPPDATA%\Postman |
Program files | Removed by the uninstaller |
%APPDATA%\Postman |
Local collections, environments, history, and anything you built while signed out | Back up local changes and anything not verified in the web app; signing in alone does not prove sync finished |
%USERPROFILE%\Postman |
Postman's default working folder, created empty on first launch | Check for files you saved there yourself |
| Desktop and Start Menu shortcuts | App shortcuts | Removed by the uninstaller |
Postman's own support article warns that if you use it locally without signing in, do not delete %APPDATA%\Postman outright: rename it first, reopen Postman to create a fresh one, and only delete the renamed copy once you have confirmed you do not need anything in it. How to remove local data
Check the result
Run these read-only commands after the uninstall finishes:
Get-Process Postman -ErrorAction SilentlyContinue
winget list --id Postman.Postman
Test-Path "$env:LOCALAPPDATA\Postman"
Test-Path "$env:APPDATA\Postman"
- No output from
Get-Processonly means this query observed no matching process; a suppressed error leaves the running state unknown. A listed process means a window or helper 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\Postman"returningTruemeans your local collections and history are still there, which is expected unless you removed them yourself.
If you installed it with winget
winget uninstall runs the same uninstaller Settings › Apps uses and removes the same program files; it does not touch %APPDATA%\Postman or %USERPROFILE%\Postman on its own.
Account and sync
Uninstalling does not delete your Postman account or content already synced there. Confirm the collections and environments you need are accessible in the web app before removing local data; unsaved or unsynced changes still need a separate copy.
What Mole lists
For Postman installed per-user from winget:
- The program folder and both the Desktop and Start Menu shortcuts are selected by default.
%APPDATA%\Postman, where your local collections and history live, is listed but not selected; the caches inside it are listed as their own rows and selected by default.%USERPROFILE%\Postmanis listed but not selected.- If a
postman://link registration still points at the removed program, Mole lists it too, after backing it up to a.regfile.
What this test covered
Tested with Postman 12.29.2 installed through winget, per-user scope. Every listed row was ticked and removed in this test. Not verified: removing an install with local-only (signed-out) data, and a signed-in account.
These observations come from a source-built Mole in a Windows test VM. The downloadable Mole package was not verified in this test.
