Where Does Miniforge Store Environments?
Miniforge installs to ~/miniforge3 by default, with named environments in its envs subfolder and downloaded packages cached in pkgs.
Last updated
Miniforge follows the classic conda layout under one roof directory. The installer suggests ~/miniforge3, named environments land in its envs subfolder, and the pkgs subfolder caches every downloaded tarball for reuse. The base Python itself lives at the root. Environments created elsewhere with -p are your own bookkeeping; named ones stay inside the prefix where conda info can see them.
Custom prefixes and condarc entries can relocate pieces, which is why conda info is worth running before deleting anything. The .condarc in your home directory is the usual suspect when environments appear somewhere unexpected.
Where Miniforge stores this, by platform
~/miniforge3/envs
Named environments in the envs subfolder, package cache in pkgs. The installer default is ~/miniforge3; a custom prefix during setup moves the whole tree. Check conda info when unsure.
~/miniforge3/envs
Same default as Linux. Apple silicon and Intel installs agree on this spot. Shell init edits your rc file but environments stay under the prefix.
%USERPROFILE%\miniforge3\envs
Pick a short path without spaces at install time to spare yourself quoting pain. The envs and pkgs subfolder rules match Unix exactly.
Frequently asked questions
How do I confirm my actual base prefix?
Run conda info and read the base environment and envs directories lines. That output reflects condarc overrides and env vars, so it beats any documented default when the two disagree.
I have both Miniforge and Micromamba. Which owns an environment?
They share the layout but not the folder. Micromamba defaults to ~/micromamba while Miniforge defaults to ~/miniforge3, and each reads its own condarc. Check both before assuming an environment belongs to one of them.
Notice an outdated path? Let us know.