Where Does Micromamba Store Environments?
Micromamba keeps every environment under its root prefix, which defaults to ~/micromamba, with named envs in the envs subfolder and packages in pkgs.
Last updated
Micromamba has no hidden install maze: almost everything sits under one root prefix directory. Named environments live in its envs subfolder, downloaded packages pile up in pkgs, and the base environment is the root itself. The default root is ~/micromamba unless you said otherwise.
Overrides exist at every level, which is why micromamba info is the command to memorize. MAMBA_ROOT_PREFIX, the -r flag, and condarc entries can each move things. Check the resolved paths before deleting anything by hand.
Where Micromamba stores this, by platform
~/micromamba/envs
Named environments live in the envs subfolder; pkgs holds the shared package cache. Override with MAMBA_ROOT_PREFIX or the -r flag. Portable and custom installs commonly relocate this whole tree.
~/micromamba/envs
Same default as Linux. Shell init writes hooks into your rc file, but the environments themselves stay under the root prefix. Move the root and re-run shell init to relink.
%USERPROFILE%\micromamba\envs
Set MAMBA_ROOT_PREFIX to a short path without spaces if installers misbehave. The envs subfolder rule is identical; only the default root differs from Unix.
Frequently asked questions
How do I confirm my actual root prefix?
Run micromamba info and read the envs directories and root prefix lines. That output reflects your overrides (MAMBA_ROOT_PREFIX, condarc, flags), so it beats any documented default.
How do I fully remove an environment?
Delete the environment folder under envs, or run micromamba remove -n name --all. Wiping the whole root prefix removes everything including the package cache, which is the scorched-earth uninstall.
Notice an outdated path? Let us know.