'pip' is not recognized as an internal or external command

Windows is telling you it searched everywhere it knows (the PATH) and found no program named pip. Two causes cover nearly every case: Python isn’t installed, or it’s installed but wasn’t added to PATH — the installer has a checkbox for that, and it’s unticked by default in the standard installer’s first screen, so most people click past it.

The fix, in order

  1. Try the Python launcher first: py -m pip --version. Most Windows installs of Python include the py launcher even when pip isn’t on PATH. If this answers with a version, you’re fine — use py -m pip install ... in place of pip install ... everywhere.
  2. If py is also not recognised, Python isn’t installed (or is badly broken). Download it from python.org and reinstall — and this time, on the installer’s first screen, tick “Add python.exe to PATH” before clicking Install.
  3. Already installed but want plain pip to work? Re-run the installer → Modify → Next → tick “Add Python to environment variables” → Install. No need to uninstall first.
  4. Close and reopen the terminal after any install. PATH changes only reach newly opened windows; the terminal you’ve been staring at keeps the old one.
  5. In VS Code, restart it too (it holds its own copy of the environment), and check the interpreter in the bottom bar points at your Python.

On Mac and Linux

The equivalent message (“command not found: pip”) usually means you need `pip3`, or to run it through the interpreter: `python3 -m pip install ...`. Many systems deliberately ship only the `python3` name. On recent Ubuntu/Debian, system Python also refuses outside-package installs by design (“externally managed environment”) — use a virtual environment: `python3 -m venv .venv`.

If it still happens

If installs from python.org keep failing to register, the Microsoft Store version of Python also works and sets up PATH automatically — but don’t keep both versions fighting; pick one, uninstall the other, and use `py -m pip` so you always know which Python pip belongs to.

Common questions

Is pip a separate download from Python? No — pip ships with Python 3.4 and later. “Not recognized” is a finding-it problem (PATH), not a missing-piece problem, which is why reinstalling with the checkbox ticked fixes it.

What’s the difference between pip and py -m pip? Same tool, addressed differently: pip asks Windows to find the program by name; py -m pip asks the Python launcher to run pip as part of a known Python. The second form also guarantees pip matches the Python you’ll run.

Related errors

ModuleNotFoundError: No module named · IndentationError: unexpected indent · Node: Cannot find module