Is it safe to delete ~/Library/Caches/pip?
- Yes. It’s pip’s download cache plus wheels it built, kept so the next install is faster. Packages you’ve installed, in your Python or in virtual environments, are separate copies.
- What it costs you: packages download again, and any pip had to build from source get built again.
- Does it come back? Yes, with each
pip install. - SiftMac’s verdict: Rebuilds
1. What pip caches
pip keeps two caches in one folder. Its documentation describes them like this:
- An HTTP cache that works like a web browser’s: responses from package indexes, including the package files pip downloaded.
- A wheel cache of wheels pip built on your Mac from source distributions, so it doesn’t compile the same package twice.
By default, every pip you run as your user shares this one folder, whichever Python or virtual environment it belongs to. pip treats the layout inside as an implementation detail that can change between versions, which is one more reason to clear it with pip’s own command rather than by picking through it.
2. Where it is
~/Library/Caches/pip
That’s the default on macOS; pip also respects XDG_CACHE_HOME if you’ve set it. To be sure, ask the pip you actually use:
python3 -m pip cache dir
3. How big it gets
It grows with every package and version you install, across all projects and environments, and packages that ship large wheels add the most. pip can describe its own cache:
python3 -m pip cache info
du -sh ~/Library/Caches/pip
pip cache info reports the HTTP and wheel parts separately, and pip cache list names the wheels it built.
4. How to clear it
With no pip install running:
python3 -m pip cache purge
That clears all files from both the wheel and the HTTP cache. To remove only one package’s wheels instead, for example one you suspect was built wrong, use remove with its name:
python3 -m pip cache remove numpy
Running pip as python3 -m pip makes sure you reach the pip of the Python you mean. Deleting the folder’s contents in Finder works too; empty the Trash afterwards to get the space back.
5. What happens after
- Nothing you’ve installed changes. Packages live in each environment’s
site-packages, not in the cache. - The next install of each package downloads it again from PyPI or your own index.
- Packages without a ready-made wheel for your Mac are built from source again, which needs the same compilers as before and is the slow part of reinstalling them.
- pip starts filling the cache again straight away.
--no-cache-dirinstalls without it, but pip’s docs only recommend that when something else does the caching, such as layered container builds.
6. Python’s other big folders
Python leaves other large folders behind, each with its own answer: virtual environments in old projects, uv’s cache if you use uv, conda’s packages and environments, and models downloaded by AI libraries, covered in the AI files guide.
Questions
Does pip cache purge uninstall my packages?
No. It only empties the cache. Installed packages stay in your Python and your virtual environments, and keep working.
Is ~/Library/Caches/pip shared by every Python on my Mac?
By default, yes. The cache belongs to your user account, so the pip in each virtual environment and each Python version reads and writes the same folder unless one is configured otherwise.
Can I clear pip’s cache while my code is running?
Yes. Running Python code never reads the cache; only pip install does. Just don’t clear it in the middle of an install.
Can I delete the old http folder inside pip’s cache?
Yes. pip 23.3 moved its HTTP cache to a new folder, and pip’s docs say you may delete the old http one once you no longer use older pip versions.
How SiftMac handles it. Its App caches category lists ~/Library/Caches/pip as Python packages (pip) with a Rebuilds verdict, ticked by default with the other caches, and clears what’s inside while keeping the folder. Old projects’ virtual environments are listed separately, under Developer files.
Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works