Where Does Mamba Keep Envs and Package Caches?
Micromamba centers on a root prefix with envs and pkgs inside. Defaults per OS, MAMBA_ROOT_PREFIX moves and info reveals all.
Last updated
Micromamba keeps one root prefix holding everything: named environments under envs, the shared package cache under pkgs, plus repodata indexes. Classic mamba instead layers on conda's config files, while micromamba ships empty and reads .condarc/.mambarc only if present.
The default root is ~/micromamba (or %USERPROFILE%\micromamba on Windows), movable with MAMBA_ROOT_PREFIX or -r. Never guess: micromamba info prints envs directories, package cache, config files and root prefix for your exact install. Removing the root prefix wipes every env at once, so back up environment.yml exports first.
Where Mamba stores this, by platform
%USERPROFILE%\micromamba
Default root prefix with envs and pkgs inside. Set $Env:MAMBA_ROOT_PREFIX to relocate. User rc files resolve through ~/.condarc and ~/.mambarc as on Unix.
~/micromamba
Same default-root role. Confirm with micromamba info before scripting around it. Separate package caches outside the root show up there too.
~/micromamba
Mirrors macOS. System rc files layer from /etc/conda down through root prefix to user files. Named envs activate from $MAMBA_ROOT_PREFIX/envs by default.
Frequently asked questions
How do I find where my micromamba envs live?
Run micromamba info and read the envs directories and root prefix lines. Named envs sit in $MAMBA_ROOT_PREFIX/envs unless created elsewhere with an explicit path. The base env is the root prefix itself.
How do I fully uninstall micromamba?
Delete the root prefix directory (~/micromamba by default) plus any separate package cache from micromamba info. That removes all envs and cached packages together. Export environment.yml files first for anything worth recreating.
Notice an outdated path? Let us know.