Micromamba keeps two things in different places: the binary (the program itself) and the root prefix (where environments and caches live). Knowing both makes troubleshooting, backups and uninstalling much easier.
Quick answer
| Item | Linux / macOS (official script) | Windows (official PowerShell script) |
|---|---|---|
| Binary | ~/.local/bin/micromamba | %LOCALAPPDATA%\micromamba\micromamba.exe |
| Root prefix (default) | ~/micromamba | %USERPROFILE%\micromamba |
| Named environments | ~/micromamba/envs/NAME | %USERPROFILE%\micromamba\envs\NAME |
Homebrew installs the binary inside Homebrew's own prefix, and manual installs put it wherever you extracted it.
How to find the binary
# Linux / macOS
which micromamba
# Windows PowerShell
Get-Command micromamba
If nothing is found, the folder is not on your PATH. On Linux and macOS, make sure ~/.local/bin is listed in echo $PATH.
What is the root prefix?
The root prefix is Micromamba's home. All named environments and, by default, the package cache are created under it. It is controlled by the MAMBA_ROOT_PREFIX environment variable, which micromamba shell init -r PATH sets for you. The official documentation notes it defaults to ~/micromamba when not set.
echo $MAMBA_ROOT_PREFIX # Linux / macOS
$Env:MAMBA_ROOT_PREFIX # PowerShell
The fastest check: micromamba info
micromamba info
This prints the version, the root prefix, environment directories, package cache folders, channels and your platform. It is the first command to run when something looks wrong.
Configuration files
Micromamba ships no configuration file of its own, but it reads .condarc and .mambarc files when they exist, for example in your home folder. Commands such as micromamba config append channels conda-forge write to your user configuration. Run micromamba config list to see the active settings.
Changing the install location
- Binary folder: the Linux/macOS script asks "Micromamba binary folder?" and defaults to
~/.local/bin. - Root prefix: the script asks "Prefix location?" and defaults to
~/micromamba. You can also rerunmicromamba shell init -r /new/path. - Single project: create an environment anywhere with
-p /path/to/env.
Tip: on machines with a small home partition, put the root prefix on a larger disk. Large scientific environments can take several gigabytes.
Paths in Docker images
Container setups often set MAMBA_ROOT_PREFIX explicitly so environments live in a predictable folder inside the image. Check the documentation of the image you use for its chosen paths.
Paths on CI systems
On CI services the home folder is often reset between jobs. Many pipelines cache the package folder under the root prefix to speed up later runs, or set MAMBA_ROOT_PREFIX to a path inside the workspace. Whatever you choose, keep it consistent between the step that creates the environment and the steps that use it.
Finding multiple copies
It is easy to end up with two binaries, for example one from Homebrew and one from the install script. Run:
which -a micromamba # Linux / macOS: every copy on PATH
where.exe micromamba # Windows
The first entry is the one your shell uses. Remove or rename the copies you do not want, then open a new terminal.
What to back up
- Environment files: export each environment with
micromamba env export. These small text files are the most valuable thing to keep. - Configuration:
~/.mambarcor~/.condarcif you customized channels. - Not needed: the binary itself (it can be downloaded again) and the package cache (it rebuilds automatically).
Related guides
Use these paths when you uninstall Micromamba or delete an environment.