Your Mac says “pip command not found,” and your package installation stops before it starts. That error means your shell cannot find the command; it does not prove pip is missing. Start by checking pip through Python, then use the fix that matches the result.
Run pip through Python first
This bypasses a missing pip executable or PATH entry when Python already has pip installed.
Open Terminal. Enter the commands there, not at Python’s >>> prompt.
Run python3 --version to check that Python is available.
Run python3 -m pip --version. A version response means pip is installed for that interpreter.
Install your package with python3 -m pip install PACKAGE, replacing PACKAGE with the package name. Keep using this form whenever instructions call for pip install PACKAGE.
For multiple Python installations, replace python3 with your intended interpreter’s absolute path, followed by -m pip. That selects the Python installation you want.
Try the pip3 command
Run pip3 --version in Terminal and check which Python installation it identifies.
If it identifies your intended Python, install your package with pip3 install PACKAGE.
Homebrew puts pip3 in its main bin directory, while the unversioned pip command lives elsewhere. If pip3 works, you have a usable command without changing your shell configuration.
Restore pip when Python reports a missing module
The error No module named pip means your selected Python installation lacks pip itself.
For a Python installation that includes ensurepip and permits bootstrapping, run python3 -m ensurepip --upgrade. This installs Python’s bundled pip without downloading it.
Check the result with python3 -m pip --version.
If pip is absent and you also want the bare pip command, use python3 -m ensurepip --upgrade --default-pip instead of the earlier bootstrap command. The extra option adds the unversioned script alongside the versioned scripts. It does not guarantee script repair when an equal or newer pip is already installed.
For an existing virtual environment, run .venv/bin/python -m ensurepip --upgrade to restore pip there. Replace .venv with your actual environment folder.
If you get externally-managed-environment, use the Homebrew repair or virtual environment method below. That error concerns installation restrictions, not command discovery.
Install Python if python3 is missing
The official macOS installer supplies Python when python3 is missing.
Open the Python Releases for macOS page.
Select a supported stable release.
Check that release’s macOS compatibility requirements.
Download its macOS installer.
Open the downloaded .pkg file.
Choose Continue to proceed through the installer.
Accept the license with Agree.
Click Install, keeping the standard installation options.
Authenticate as an administrator when requested.
Open /Applications/Python 3.14/Install Certificates.command, substituting your installed version’s folder. This completes certificate setup; it does not itself restore a missing pip command.
Reopen Terminal.
Run python3 -m pip --version to confirm pip works.
Leave Apple’s /usr/bin/python3 untouched. Do not modify or delete it when installing your own Python.
Repair Python through Homebrew
Use this method if you manage Python with Homebrew. Its Python formula supplies pip, so Homebrew handles the repair.
Run brew info python to inspect the formula. If you deliberately installed a versioned Python formula, use its matching formula name throughout these commands.
If Python is not installed through Homebrew, run brew install python.
For an existing installation with missing or broken pip, run brew reinstall python.
Confirm the repair with python3 -m pip --version.
If pip3 works but you need the bare pip command, run export PATH="$(brew --prefix python)/libexec/bin:$PATH". This exposes Homebrew’s unversioned commands in the current shell.
Test the command with pip --version.
To retain the change, add that export to the startup file your shell reads.
Changing PATH does not remove Homebrew’s externally managed installation restrictions. If you encounter that error when installing packages, use a virtual environment.
Create a separate environment for your packages
A virtual environment gives your project its own Python environment with pip included.
- 1.In Terminal, run
cd /path/to/project, replacing the example path with your project folder. - 2.Run
python3 -m venv .venv. Do not add--without-pip. - 3.Run
source .venv/bin/activatein zsh or bash. - 4.Check pip with
python -m pip --version. - 5.Install your package with
python -m pip install PACKAGE, replacingPACKAGEwith its name.
Restore a missing command path
If python3 -m pip works but pip does not, check the executable’s PATH setup. Use the route that matches your installation.
For a traditional python.org framework installation, open /Applications/Python 3.14/Update Shell Profile.command, replacing 3.14 with your installed version. This updater does not support the optional free-threaded installation.
Reopen Terminal after running the updater.
For pip installed using the user installation scheme, run python3 -m site --user-base to find the user directory.
Append /bin to the returned path. Do not assume every Mac uses ~/.local/bin.
Run export PATH="/actual/user-base/bin:$PATH", replacing /actual/user-base/bin with the directory you just determined.
Save that export in the startup file your shell reads.
Open a new Terminal session.
Run pip --version to test the change.
In zsh, run rehash to refresh command lookup after repairing PATH. This refreshes cached command locations; it does not install pip.
If the bare command still fails but python3 -m pip works, keep using the module form. If the module is missing and ensurepip is unavailable, use your Python distributor’s repair method or the official bootstrap below.
For an installation that permits bootstrapping, open pip’s Installation page.
Follow the get-pip.py download link to save the script.
In Terminal, run cd /path/to/download-folder, replacing the example path with the folder containing the script.
Run python3 get-pip.py.
Verify the installation with python3 -m pip --version.
If bootstrapping fails, repair Python through its distributor. For Homebrew, return to brew reinstall python; for a python.org installation, install a newer supported release from the Python Releases for macOS page. The default installer options make its python3 the one your shell uses.
Frequently Asked Questions
Should I use sudo easy_install pip from an older Mac tutorial?
No. Easy Install is deprecated. Use ensurepip, the official get-pip.py bootstrap, a virtual environment, or your Python distributor’s repair method. Instructions relying on Apple’s bundled Python 2 are also outdated: Apple removed Python 2.7 in macOS Monterey 12.3.
Will upgrading pip fix command not found?
An upgrade requires an already working pip module. It cannot bootstrap a missing module. In a virtual environment or writable installation that permits pip self-upgrades, run python3 -m pip install --upgrade pip. Do not use that route to maintain Homebrew’s externally managed base installation.
Why did pip stop working after I moved my project folder?
Virtual environments are not portable. Create a replacement at its final location with python3 -m venv .venv-new. If you have requirements.txt, restore packages with .venv-new/bin/python -m pip install -r requirements.txt. Switch your project to the replacement environment, then remove the obsolete environment after confirming the replacement works.
Can I fix pip on a work-managed Mac?
Use your administrator’s approved Python installation. If restrictions prevent installation or repair, ask the administrator to provide or repair that environment.
