How to Uninstall Anaconda on Mac Completely

To uninstall Anaconda on a Mac, first export the conda environments you want to keep, then run Anaconda Distribution's own uninstall.sh script from the active base installation. If the script is missing, the install may predate Anaconda Distribution 2025.06 and needs the documented manual path instead.

I would not begin by deleting every file named conda or anaconda. Environments can live outside the main installation, and files such as .condarc may be shared with another conda setup. Find out what should survive while the tools still work.

Quick Answer: Preserve First, Then Remove Anaconda

1. List all conda environments with conda info --envs.
2. Export every environment you want to recreate later.
3. Find the active installation with conda info --base.
4. Check that folder for uninstall.sh.
5. Deactivate conda, then run the script from that base path.
6. Review optional caches, configuration, user data, and external environments separately.
7. Close and reopen Terminal to verify that (base) no longer appears.

Anaconda's current Distribution uninstall guide makes the script the normal route for modern macOS installations. Apple gives the same general advice: when third-party software provides an uninstaller, use it instead of only trashing an app.

Step 1: Separate Distribution from Related Tools

One Mac can hold several Python and conda tools that arrived through different installers. Before removing anything, identify the product and installation you intend to retire.

• Anaconda Distribution is the full local Python and conda distribution covered by this guide.
• Anaconda Navigator is a graphical app that can be managed separately. Removing only Navigator does not necessarily remove the Distribution or your environments.
• Miniconda has its own official uninstall page and may use a miniconda3 base folder.
• Homebrew Python, pyenv, Miniforge, and Apple's system tools are separate installations. A broad filename search can catch files they still need.

Open Terminal and run:

conda info --base
conda info --envs

The first command shows which base installation answers the current shell. The second shows registered environments and their paths. Save both outputs somewhere outside the Anaconda base folder before continuing.

Tip: If conda is not found, do not guess an installation path. Search Finder for the Anaconda-Navigator app and inspect your shell profiles or installation records before deleting a folder.

Step 2: Back Up Environments and Project Files

An environment export is a recipe, not a backup of your whole project. Export wanted environments while conda still works:

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

Repeat that command with each real environment name you want to preserve. Anaconda currently recommends this YAML export before uninstalling. Conda's newer documentation also supports conda export, but the traditional conda env export command remains supported and matches Anaconda's uninstall instructions.

I keep the resulting YAML files outside the base installation and outside any environment directory I plan to remove. Also back up these items separately when they matter:

• notebooks, source repositories, datasets, and model files;
• environment variables or credentials stored outside the export;
• Jupyter configuration and kernels you customized;
• a .condarc containing private channels, proxies, or solver settings;
• external environments shown by conda info --envs.

A YAML file usually records packages and channels. It does not automatically gather arbitrary notebooks, datasets, secrets, or files created by your code. There is one important exception: conda says variables saved with conda env config vars are retained by conda env export. Inspect the YAML for credentials or tokens, store it securely, and do not commit or share it until sensitive values have been removed. Preserve any secrets that the export did not capture through your normal secret-management workflow.

Anaconda's current uninstall guide also calls out environments containing packages from the conda-pypi channel. After you have backed up one of those environments, Anaconda says to remove it before uninstalling the Distribution. Activate each environment and inspect the Channel column:

conda activate my-environment
conda list

If conda-pypi appears, deactivate the environment and remove it by name or by its recorded prefix:

conda deactivate
conda remove --name my-environment --all
# Or, for an environment identified by path:
conda remove --prefix "/path/to/environment" --all

Both removal commands delete the chosen environment. Use only the form that matches the environment you inspected, and keep its export outside that directory.

Step 3: Match the Uninstall Command to the Base Path

Use the path returned by conda info --base; do not assume every Mac uses ~/anaconda3. Two current macOS layouts are common:

Check whether the script exists in your exact base folder:

ls "$(conda info --base)/uninstall.sh"

If Terminal shows the file, continue to Step 4. If it reports that the file does not exist, skip to Step 6. Anaconda says the script was introduced in Anaconda Distribution 2025.06, so an older installation can legitimately lack it.

Tip: Seeing /opt/anaconda3 is not permission to substitute a similar-looking /opt path. Copy the exact output of conda info --base and verify the script before using sudo.

Step 4: Use Anaconda's Modern Uninstall Script

Deactivate the current environment before starting. Run:

conda deactivate

If the prompt still shows another named environment, deactivate again until no conda environment is active. Then use the command that matches the verified base path.

For a home-directory installation:

~/anaconda3/uninstall.sh

For a system installation at /opt/anaconda3:

sudo -E /opt/anaconda3/uninstall.sh

The screenshot above is a privacy-safe local capture of Anaconda's current first-party documentation on September 2, 2026. Read the script's prompts before confirming. Do not run both commands, and do not change the path to one you have not verified.

Step 5: Choose Advanced Cleanup Flags Deliberately

The basic script is the conservative default. Anaconda also documents optional flags:

Anaconda explicitly says these options are not recommended when you have multiple conda installations. If you have only one verified installation and genuinely want its user data removed, the documented home-directory example is:

~/anaconda3/uninstall.sh --remove-caches --remove-config-files user --remove-user-data

Treat that as an advanced reset, not a more correct version of the basic uninstall. Back up configuration first and inspect conda info --envs for environments outside anaconda3.

Step 6: Use the Legacy Path Only When uninstall.sh Is Missing

A missing script changes the procedure. While the old conda installation still runs, reverse the shell initialization it added:

conda activate
conda init --reverse --all

Now rerun conda info --base and write down the exact result. Anaconda's manual guide removes the whole verified installation directory. For the two standard Anaconda Distribution locations, it documents:

# Choose only the command matching the exact base path you verified.
rm -rf ~/anaconda3
sudo rm -rf /opt/anaconda3

These commands bypass Trash and cannot be undone. Never run both, never use a shortened /opt or home-directory target, and never replace the path with a wildcard. If the base path is custom or you are uncertain, stop and use Anaconda support or an administrator who can inspect the installation.

I would also avoid the older habit of manually deleting blocks from .zshrc before trying conda init --reverse --all. The conda command knows which initialization markers it manages. After it runs, review the shell file rather than improvising a second cleanup.

Step 7: Decide Which External Data Should Remain

Not everything left behind is accidental. The base uninstaller and an external environment have different ownership.

Return to the conda info --envs output you saved in Step 1. An environment located outside anaconda3 may remain after the base install is gone. Keep it if another compatible conda installation will manage it, or remove it before uninstalling with the name or prefix command shown in Step 2. Do not delete it merely because it appears in the old registry.

Likewise, inspect these paths individually before removing anything:

~/.condarc
~/.conda
~/.continuum

Keep .condarc when you plan to reinstall and want its channel or solver configuration. Keep ~/.conda until you understand whether another conda installation or external environment uses it. A few kilobytes of configuration are rarely worth breaking a working replacement setup.

Tip: If your goal is disk space rather than a clean reset, measure the verified base directory and external environment directories first. Configuration files are not where Anaconda's large package footprint usually lives.

Step 8: Verify Anaconda Is Gone

Open a new Terminal window for a clean test. Then check:

1. (base) no longer appears automatically in the prompt.
2. command -v conda returns nothing, or points to a different conda installation you intentionally kept.
3. The exact old base path no longer exists.
4. Wanted project folders, YAML exports, notebooks, and datasets still open.
5. External environments you chose to keep still exist at their recorded paths.
6. Anaconda-Navigator is gone only if removing that app was part of your goal.

The conda command remaining is not automatically a failed uninstall. Miniconda, Miniforge, Homebrew, or another installation may own it. Run type -a conda and inspect every returned path before removing anything else.

If the old base still activates in new shells, review the shell files that conda init --reverse --all reported. The startup-programs guide can help separate a shell initialization issue from an ordinary macOS login item.

Where Sensei Fits After the Uninstall

Use Anaconda's own tools for the Distribution and its environments. After that work is complete, Sensei's Uninstaller can remove selected Mac applications with their associated local files.

As of September 2026, Sensei 2.1.2 requires macOS 14 or later. It cannot export conda environments, interpret which Python environment contains valuable work, reverse shell initialization, or replace Anaconda's script.

That keeps a development-environment decision out of a general app remover, where it does not belong.

Keep the Recovery Options You Actually Need

The useful moment to slow down is before removal, while conda can still list and export what you built. Once those backups are outside the installation, the modern script is straightforward; only older installations need the manual branch.

If you are tidying other software afterward, Sensei can remove selected Mac apps with their associated local files. Your conda environments still deserve conda's own tools and your judgment.

Optimize Your Mac with Sensei

Monitor performance, clean storage, and manage Mac maintenance in one native app, with a full 7-day trial before you decide.

Download Free TrialView All Plans

Related Guides

• How to Uninstall Apps on Mac Completely
• How to Manage Startup Programs on Mac
• How to Free Up Disk Space on Mac