How to uninstall Python or Anaconda on a Mac

Identify the Python you are removing

Several Python installations can coexist. Removing one does not necessarily remove the command another shell or editor uses. A version number alone is not enough: note the executable path and installer before changing anything.

These checks only report information and need no administrator password:

type -a python3
python3 -c 'import sys; print(sys.executable)'
brew list --formula
conda info --base
conda info --envs

Use the Homebrew and conda commands only if those tools are installed; “command not found” is not a reason to install them for cleanup. type can reveal a shell alias or multiple command locations. The Python command prints the selected interpreter. It does not enumerate every interpreter configured in your editor.

On the checked Mac, the selected Python belonged to a Homebrew installation and conda was unavailable. We did not uninstall anything. Paths below come from the distributors’ documentation, not a claim that those folders exist on your Mac.

Preserve projects and environments

Copy your source, notebooks, datasets and configuration to a backup outside the installation you plan to remove. A repository may omit large data files and local secrets. Confirm that the backup contains the actual working files, rather than just shortcuts or a remote URL.

For conda, export each environment you intend to recreate to a YAML file, as Anaconda documents. For example, if your environment is actually named research:

conda env export --name research > research-environment.yaml

This writes a new file in the current directory, so choose a safe location and do not overwrite an existing file you need. It does not back up notebooks or database contents. Also inspect the environment list for environments outside the base installation. Keep what you need before deciding whether to remove any of them.

Close editors, notebook servers and tools using the interpreter before removal. If work or school manages the environment, ask IT and stop: a package removal can break shared automation even if your own project is finished.

Uninstall Anaconda with its own script

Anaconda’s current instructions distinguish installations with an uninstall script from older manual installations. The script was introduced with Anaconda Distribution 2025.06. First run conda info --base and compare the result with the installation you intend to remove.

After deactivating the environment, the documented basic example is:

conda deactivate
~/anaconda3/uninstall.sh

That path is an example for a matching home-folder installation. If your confirmed base is /opt/anaconda3, Anaconda documents sudo -E /opt/anaconda3/uninstall.sh for its system installation; that requires the administrator password. Do not run either path merely because it appears here. Match the actual base and the vendor’s edition-specific instructions.

Avoid optional remove-user-data or remove-all-config arguments by default, particularly with multiple conda installations. The vendor warns that broader cleanup can affect shared configuration. If your older installation has no uninstall script, follow its separate manual guidance with the administrator for system locations; do not substitute a guessed recursive-delete command.

Review conda’s shell initialization

Conda can add an initialization block to shell profiles such as ~/.zshrc. Before removing an older manual installation, Anaconda documents reversing initialization with conda’s init command. Back up the profile, review the exact marked conda block and follow that procedure while conda still works.

Do not delete the whole profile. It may contain Homebrew, language tools and settings unrelated to Anaconda. After removal, close and reopen Terminal, check whether the base prompt returns and repeat the identification check. Restore the profile backup if an unrelated command stops working.

Remove a Homebrew Python through Homebrew

Use the exact installed formula name from brew list --formula, which may be versioned. Check its dependencies before removal:

brew uses --installed python@3.14

The example names a formula observed during research; use it only if that is the one you have. The read-only dependency listing helps you see whether other installed tools need it.

For a confirmed, unwanted formula, Homebrew’s documented removal form is brew uninstall python@3.14. It changes the installation; we did not run it. Do not add force or ignore-dependencies options to bypass a refusal. The Homebrew removal guide covers packages versus the entire package manager.

python.org and Apple’s Python are different

The Python documentation identifies its installer’s Applications folder, /Library/Frameworks/Python.framework and command symlinks in /usr/local/bin. These are identification locations, not permission to remove a shared framework wholesale. Multiple versions or other users can depend on them.

For a systemwide python.org installation, have the administrator follow the matching Python documentation and review version-specific components. Moving IDLE or Python Launcher alone does not remove the framework. Do not use a broad deletion command that matches every file beginning with python.

Python’s own documentation explicitly says never to modify or delete the Apple-controlled installation reached through /usr/bin/python3, which is provided for Xcode or Command Line Tools. Removing a separate Python is also different from removing Xcode.

Where Tend fits

Tend’s free Clean Up can list an eligible pip cache in Developer files; the checked scanner includes ~/.cache/pip. It is not an inventory of every Python installation or conda environment. Pro moves reviewed cleanup items to the Trash, and the cache guide explains what can be regenerated.

Use the distributor’s method for the interpreter. Tend’s Pro Uninstaller handles app bundles and support files in your own Library, not systemwide language frameworks or dependency-aware Homebrew removal.

Questions

Related guides

Sources

• Python Software Foundation, Using Python on macOS, including installation components and Apple-controlled Python.
• Anaconda, current uninstall procedure, environment export and shell initialization.
• Homebrew, list, uses and uninstall commands.
• Local read-only interpreter, Homebrew-list and tool-availability checks on 23 October 2026; no uninstall command was executed.

Sources checked 23 October 2026. Spotted something out of date? Tell us and we'll fix it.