Back to Article List

How to uninstall Miniconda on Linux, macOS and Windows

How to uninstall Miniconda on Linux, macOS and Windows

Most top-ranking answers for how to uninstall Miniconda say rm -rf ~/miniconda3 and stop there. That advice is older than conda init, and following it leaves a dead initialization block in your shell config, three hidden directories in your home folder and, on some setups, a shell that complains on every new terminal. The complete removal is barely longer. Here it is per OS, current for the 26.x installers, including uninstaller options that have only existed since late 2024.

Export your environments before uninstalling

Uninstalling destroys every environment you've created, all of them living inside the install directory. Any that took real effort to assemble should be exported first:

conda env export -n myproject > myproject.yml

Repeat per env (conda env list shows what exists) and park the files somewhere outside the Miniconda tree; each one rebuilds its environment later with conda env create -f, on this machine or another. A side thought before you commit: when the reason for uninstalling is just that the install feels old and crusty, rerunning a newer installer with -u over the same prefix fixes that without deleting anything, and the guide on how to update Miniconda covers when that's the better move.

Your idea deserves better hosting

24/7 support 30-day money-back guaranteeRefund covers the VPS plan on your first order. Cancel anytime
Cycle de facturation

VPS.S1

28.59 RON Save  17 %
23.82 RON Mensuel
  • 2 vCPU AMD EPYC
  • 2 GB RAMMÉMOIRE
  • 30 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas. inclus

VPS.S3

71.56 RON Save  33 %
47.69 RON Mensuel
  • 4 vCPU AMD EPYC
  • 6 GB RAMMÉMOIRE
  • 70 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas. inclus

VPS.S4

95.43 RON Save  20 %
76.33 RON Mensuel
  • 6 vCPU AMD EPYC
  • 8 GB RAMMÉMOIRE
  • 80 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas. inclus

EPYC VPS.P1

42.92 RON Save  22 %
33.37 RON Mensuel
  • 2 vCPU AMD EPYC
  • 4 GB RAMMÉMOIRE
  • 40 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas. inclus
  • Sauvegarde auto gratuiteComprend un emplacement de sauvegarde que vous pouvez programmer en quotidien, hebdomadaire ou mensuel.

EPYC VPS.P2

81.11 RON Save  24 %
62.01 RON Mensuel
  • 2 vCPU AMD EPYC
  • 8 GB RAMMÉMOIRE
  • 80 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas. inclus
  • Sauvegarde auto gratuiteComprend un emplacement de sauvegarde que vous pouvez programmer en quotidien, hebdomadaire ou mensuel.

EPYC VPS.P4

143.16 RON Save  23 %
109.75 RON Mensuel
  • 4 vCPU AMD EPYC
  • 16 GB RAMMÉMOIRE
  • 160 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas. inclus
  • Sauvegarde auto gratuiteComprend un emplacement de sauvegarde que vous pouvez programmer en quotidien, hebdomadaire ou mensuel.

EPYC VPS.P5

190.90 RON Save  25 %
143.16 RON Mensuel
  • 8 vCPU AMD EPYC
  • 16 GB RAMMÉMOIRE
  • 180 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas. inclus
  • Sauvegarde auto gratuiteComprend un emplacement de sauvegarde que vous pouvez programmer en quotidien, hebdomadaire ou mensuel.

EPYC VPS.P6

286.38 RON Save  25 %
214.77 RON Mensuel
  • 8 vCPU AMD EPYC
  • 32 GB RAMMÉMOIRE
  • 200 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas. inclus
  • Sauvegarde auto gratuiteComprend un emplacement de sauvegarde que vous pouvez programmer en quotidien, hebdomadaire ou mensuel.

EPYC VPS.P7

334.11 RON Save  29 %
238.64 RON Mensuel
  • 16 vCPU AMD EPYC
  • 32 GB RAMMÉMOIRE
  • 240 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas. inclus
  • Sauvegarde auto gratuiteComprend un emplacement de sauvegarde que vous pouvez programmer en quotidien, hebdomadaire ou mensuel.

Genoa VPS.G2

119.30 RON Save  20 %
95.43 RON Mensuel
  • 2 vCPUAMD EPYC Genoa 4e génération 9xx4 à 3,25 GHz ou similaire, sur architecture Zen 4. AMD EPYC G4
  • 4 GB DDR5MÉMOIRE
  • 50 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas. inclus
  • Sauvegarde auto gratuiteComprend un emplacement de sauvegarde que vous pouvez programmer en quotidien, hebdomadaire ou mensuel.

Genoa VPS.G4

214.77 RON Save  22 %
167.03 RON Mensuel
  • 4 vCPUProcesseur AMD EPYC avec cœurs vCPU dédiés, sur matériel serveur d'entreprise. AMD EPYC G4
  • 8 GB DDR5MÉMOIRE
  • 100 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas. inclus
  • Sauvegarde auto gratuiteComprend un emplacement de sauvegarde que vous pouvez programmer en quotidien, hebdomadaire ou mensuel.

Genoa VPS.G6

429.59 RON Save  22 %
334.11 RON Mensuel
  • 8 vCPUProcesseur AMD EPYC avec cœurs vCPU dédiés, sur matériel serveur d'entreprise. AMD EPYC G4
  • 16 GB DDR5MÉMOIRE
  • 200 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas. inclus
  • Sauvegarde auto gratuiteComprend un emplacement de sauvegarde que vous pouvez programmer en quotidien, hebdomadaire ou mensuel.

Genoa VPS.G7

763.75 RON Save  22 %
596.67 RON Mensuel
  • 8 vCPUProcesseur AMD EPYC avec cœurs vCPU dédiés, sur matériel serveur d'entreprise. AMD EPYC G4
  • 32 GB DDR5MÉMOIRE
  • 250 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas. inclus
  • Sauvegarde auto gratuiteComprend un emplacement de sauvegarde que vous pouvez programmer en quotidien, hebdomadaire ou mensuel.

AMD Ryzen VPS.R1

81.11 RON Save  18 %
66.79 RON Mensuel
  • 1 CPU dédié AMD Ryzen 9 7950X à 4,5 GHz ou similaire, sur architecture Zen 4. vCPU
  • 4 GB DDR5MÉMOIRE
  • 50 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6 inclus Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas.
  • Sauvegarde auto incluse

AMD Ryzen VPS.R2

143.16 RON Save  17 %
119.30 RON Mensuel
  • 2 CPU dédiés AMD Ryzen 9 7950X à 4,5 GHz ou similaire, sur architecture Zen 4. vCPU
  • 8 GB DDR5MÉMOIRE
  • 100 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6 inclus Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas.
  • Sauvegarde auto incluse

AMD Ryzen VPS.R4

525.06 RON Save  18 %
429.59 RON Mensuel
  • 8 CPU dédiés AMD Ryzen 9 7950X à 4,5 GHz ou similaire, sur architecture Zen 4. vCPU
  • 32 GB DDR5MÉMOIRE
  • 400 GB NVMeSTOCKAGE
  • Bande passante illimitée
  • IPv4 & IPv6 inclus Le support IPv6 est actuellement indisponible en France, Finlande ou aux Pays-Bas.
  • Sauvegarde auto incluse

*VAT excluded.

INCLUDED WITH EVERY PLAN

✓ No setup fees ✓1 Gbps network
✓ Full root access on KVM ✓ Free server monitoring ✓ Firewall management ✓24/7 support

Uninstall Miniconda on Linux and macOS

Four commands, in this order, because the second one needs conda to still exist:

conda activate
conda init --reverse --all
rm -rf ~/miniconda3
rm -rf ~/.condarc ~/.conda ~/.continuum

The first activates base so the right conda answers. The second is what the old guides miss: conda init --reverse --all undoes what conda init did at install time, pulling the initialization block out of every shell config it touched, .bashrc, .zshrc and friends. Then the install directory goes (sudo rm -rf /opt/miniconda3 instead, for a system-wide install), and the last line clears the hidden leftovers: your channel config, the environments directory some tools create and the ancient .continuum folder. Open a new terminal afterwards and conda should come back as command not found, which this one time is the success state.

Use the uninstall.sh script on newer installs

Installs made from Miniconda 24.11.1 or later ship an uninstaller of their own, and the official uninstall documentation now leads with it:

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

Those flags fold the manual cleanup into one command; run the script bare instead if .condarc should survive for a future install. System-wide installs take sudo -E /opt/miniconda3/uninstall.sh. No uninstall.sh in the install directory means the install predates the script, and the four manual commands above are the route.

Uninstall Miniconda on Windows

The install folder, by default miniconda3 in your user profile, contains Uninstall-Miniconda3.exe. Run it from there, or find Miniconda under installed apps in Settings. Beyond deleting files, it removes the Start Menu entries and the registry values the installer created, which is precisely the part a bare folder deletion never cleans up, so it stays the right tool even when deleting the folder looks quicker.

Scripted and fleet removals have a silent mode:

start /wait .\miniconda3\Uninstall-Miniconda3.exe /S

Since version 24.11.1 the uninstaller also accepts cleanup flags, making a full silent removal:

start /wait .\miniconda3\Uninstall-Miniconda3.exe /S /RemoveCaches=1 /RemoveConfigFiles=user /RemoveUserData=1

On older installs those flags don't exist, and you finish by deleting .condarc and the .conda folder from your user profile by hand.

Remove Miniconda installed with Homebrew

An install that arrived via the cask leaves via brew, but run conda init --reverse --all first, since brew won't touch your shell config:

conda init --reverse --all
brew uninstall --zap --cask miniconda

--zap earns its extra characters here: the miniconda cask defines a zap stanza covering ~/.conda, ~/.condarc and ~/.continuum, so the hidden-directory sweep happens for you, where a plain brew uninstall --cask miniconda removes only the install itself. Worth knowing in passing: the miniconda and miniforge casks conflict, so on macOS this uninstall is the mandatory first step of a switch. A fair number of people remove Miniconda for exactly that reason, moving to conda-forge-first tooling, and the Miniconda vs Miniforge comparison goes through what changes when you do.

Check your shell config for leftovers

On any machine where conda has been installed more than once over the years, verify the cleanup:

grep -n conda ~/.bashrc ~/.zshrc ~/.bash_profile 2>/dev/null

Clean output means done. What you're hunting is the block fenced by # >>> conda initialize >>> and # <<< conda initialize <<<, plus any manual PATH exports pointing at a miniconda directory. Orphaned lines like these cause most of the odd shell behavior people meet after a partial removal, the terminal printing a missing-directory error on every launch being the common one, and that family of problems has its own entry in the Miniconda troubleshooting guide. Delete the block, open a fresh terminal, and the shell is back to what it was before conda moved in.

Coming back someday is cheap, for the record. A clean reinstall takes minutes on any platform, and the walkthroughs to install Miniconda on Ubuntu and install Miniconda on Windows both start from an empty machine.

Questions?

Can I keep my environments and reinstall Miniconda later?

Not in place. Environments carry hardcoded paths back into the install that created them, so parking the envs/ folder aside and dropping it into a new install breaks in subtle ways. The route that works is in the article: export each env to a yml file before uninstalling, then rebuild with conda env create -f after the reinstall. Rebuilds go quickly, since the new install downloads only what the files name.

About the author

Oliver P. Redmond

I studied history and, for a while, expected to end up in archives (or academic publishing). Instead I took a copy-editing job with a small specialist publisher, learnt rather more about XML than the job description had implied and gradually found myself editing software manuals. Naturally, technical writing followed from there.

What I like about infrastructure is the accumulated quality. A modern service may have an elegant interface sitting on top of conventions and protocols that are sometimes older than the person using it. And so, understanding a system often means following those layers backwards. I write mostly about Linux systems, virtual machines and storage. I live in Bristol and still use a fountain pen for notes.

Deploy your next project in seconds

Bring your winning ideas online faster, with modern hardware and unmetered bandwidth. Join a European cloud trusted by thousands of developers and businesses worldwide.