Because Micromamba lives entirely in your user folders, removing it is simple. Follow these steps to leave no hooks, binaries or environments behind.
Back up first: deleting the root prefix removes every environment inside it. Export anything you want to keep: micromamba env export -n NAME > NAME.yml.
Step 1: Remove shell initialization
micromamba shell deinit -s bash # or zsh, fish, xonsh
micromamba shell deinit -s powershell # Windows
Run it once for every shell you initialized. It removes the block that shell init added to files such as ~/.bashrc or ~/.zshrc. If the binary is already gone, open the profile file and delete the block marked as managed by micromamba by hand.
Step 2: Delete the binary
| Installed with | Remove |
|---|---|
| Official Linux/macOS script | rm ~/.local/bin/micromamba |
| Official Windows script | Delete %LOCALAPPDATA%\micromamba and remove it from your user PATH |
| Homebrew | brew uninstall micromamba |
| Manual extract | Delete the bin/micromamba file you extracted |
Not sure where it is? Run which micromamba (Linux/macOS) or Get-Command micromamba (PowerShell) before deleting.
Step 3: Delete the root prefix
The root prefix holds environments and, by default, the package cache.
# Linux / macOS (default location)
rm -rf ~/micromamba
# Windows PowerShell (default location)
Remove-Item -Recurse -Force $Env:UserProfile\micromamba
If you used a custom location, check MAMBA_ROOT_PREFIX or the -r path you passed to shell init. Also delete any environments you created elsewhere with -p.
Step 4: Remove configuration (optional)
Micromamba reads ~/.mambarc and ~/.condarc. Delete them only if no other tool, such as conda, uses them.
Windows: clean up PATH
- Open Start and search for "Edit environment variables for your account".
- Select Path under user variables and remove the
micromambaentry. - Remove a
MAMBA_ROOT_PREFIXuser variable if it exists.
Step 5: Verify
Open a new terminal and run micromamba --version. You should see "command not found" (or the PowerShell equivalent). If not, another copy exists on your PATH; locate it with which -a micromamba.
Removing it from Docker images and CI
In containers, uninstalling is usually done by rebuilding the image without the Micromamba steps rather than deleting files in a later layer, since earlier layers still keep the data. In CI, remove the Micromamba setup step and any cache entries that stored the package folder.
Checking for leftovers
- Search your shell profile files (
~/.bashrc,~/.zshrc,~/.config/fish/config.fish, PowerShell$PROFILE) for the wordmicromamba. - Look for a
MAMBA_ROOT_PREFIXline in your profile and remove it. - Delete Jupyter kernels you registered from Micromamba environments with
jupyter kernelspec listandjupyter kernelspec remove NAME. - Check your editor settings for interpreter paths that pointed inside the root prefix.
Keeping environments but removing the tool
Environments are normal folders, so their programs keep working without the Micromamba binary if you call them by full path. However, you will not be able to activate, update or manage them without a package manager. If you plan to switch to conda or mamba, export the environments first and recreate them with the new tool.
Reinstalling later
If you change your mind, reinstalling takes under a minute. See our Linux install guide or the install section on the homepage.
Related guides
Only want to remove one environment? Read how to delete a Micromamba environment. Unsure about paths? See where Micromamba is installed.