Skip to main content
Mole
Features Tested apps Testimonials Pricing FAQ Blog
EnglishEN 简体中文中 繁體中文繁 日本語日 한국어한 FrançaisFR DeutschDE ItalianoIT EspañolES PortuguêsPT
Buy nowBuy Download

    Help, documentation, releases, and articles.

    Home/Apps tested with Mole

    Uninstall Postman on Mac

    Check whether you are signed in to a Postman account before removing the app: signed-in collections and environments sync to your account and can be reopened after reinstalling, but anything you built while signed out (in the offline API client, or the older Scratch Pad it replaced) exists only in this Mac's local folder and is gone once that folder is deleted. These steps cover the official download and the Homebrew cask postman, which install the same app.

    Check what is local-only before removing anything

    Open Postman and look at whether you are signed in (top-right corner). If you are not signed in, everything you built lives only on this Mac; sign in first if you want it saved to your account, 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; this offline mode replaced the older feature Postman called Scratch Pad, whose local-only data works the same way.

    Quit Postman and remove the app

    Finish or cancel any running requests, quit Postman from its app menu, then move Postman from Applications to the Trash. Postman registers no login item, so nothing needs to be turned off first (check System Settings › General › Login Items & Extensions only if you want to confirm).

    Where Postman keeps its files

    Location What it holds What to do
    ~/Library/Application Support/Postman Local collections, environments, history, and the offline API client's data (Partitions, Storage) Back this up if you are signed out, or if you rely on local-only data; otherwise your account is the copy of record
    ~/Library/Application Support/com.postmanlabs.mac.ShipIt, ~/Library/Caches/com.postmanlabs.mac.ShipIt Postman's update helper state Safe to remove
    ~/Library/Caches/com.postmanlabs.mac, ~/Library/Caches/Postman Regenerable cache Safe to remove
    ~/Library/Preferences/com.postmanlabs.mac.plist, ~/Library/Preferences/ByHost/com.postmanlabs.mac.ShipIt.*.plist App preferences and updater state Safe to remove
    ~/Library/Saved Application State/com.postmanlabs.mac.savedState Saved window state Safe to remove

    Postman's own support article on removing local data warns explicitly: if you use Postman locally without signing in, do not delete this folder outright, because that deletes all of it; rename the folder instead (for example to "Postman old"), 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 in Terminal:

    pgrep -il postman
    launchctl list | grep -i postmanlabs
    ls ~/Library/Application\ Support/Postman
    

    No output from pgrep means Postman has quit. No output from launchctl list means no Postman job is currently loaded in your session; a listed com.postmanlabs.mac.ShipIt entry with no matching file is a harmless leftover record of a job that already finished, not a running process. The ls command lists what remains in the local data folder; No such file or directory means it is gone.

    If you installed it with Homebrew

    The next Mole update will skip --zap when its list reaches unchecked or shared data, or cannot be fully checked. Mole will still clean the leftovers you selected. Preview 290 does not include this protection.

    The postman cask quits Postman for you during removal. In Preview 290, Mole removes a Homebrew-installed Postman with brew uninstall --cask --zap postman, and the zap list covers ~/Library/Application Support/Postman along with the ShipIt updater folders, caches, preferences, and saved window state above, all removed whatever you select in Mole. If you use Postman signed out, back up or rename ~/Library/Application Support/Postman first, or skip zap to keep everything but the app:

    brew uninstall --cask postman
    

    Homebrew Postman cask

    What Mole lists

    This describes Mole 1.15 (currently in Preview):

    • ~/Library/Application Support/Postman is listed but not selected by default: Mole treats an app's exact-name Application Support folder as user data and leaves it for you to review yourself, whether or not you were signed in when you created the data inside it. Back it up or tick it yourself if you want it removed. The ShipIt updater folders, caches, preferences, and saved window state are separate rows and are selected by default.
    • A Postman login item ghost may remain in System Settings after uninstall even though nothing registered one during normal use; that is a historical System Settings record, not a running process, and Mole does not delete it.

    What this test covered

    Postman was installed from Homebrew and removed with a development build of Mole on September 17, 2026, as part of an 8-app cluster. The completion screen for that cluster reported 8 items removed, 1 retained (unrelated to Postman); Postman's own row showed its Application Support, Caches, and ShipIt paths all removed with no failures. A login item ghost for com.postmanlabs.mac.ShipIt remained afterward with no backing file, the same harmless BTM record other removed apps leave behind. This test did not have any local-only (signed-out) data on the Mac, so the "do not delete while signed out" warning above was not exercised, and the official direct download was not uninstalled in this test.

    Mole clears caches and app leftovers. Users have freed over 100 GB in a single cleanup.

    Try Mole

    Mole · 鼴

    Cleanup, software, and status for your Mac.

    v1.15.0 (291) · Release notes

    Product

    Mac Cleaner App Uninstaller Mac Optimizer Disk Analyzer System Monitor

    Support

    Help Documentation Releases Blog

    Legal

    Terms of Service Privacy Policy Refund Policy

    Resources

    CLI Tool Affiliate Program

    Connect

    Twitter hi@mole.fit

    Mole’s only official website mole.fit · Avoid installers from unknown sources

    The CLI stays free for terminal workflows.