Where Does Conda Keep Environments and Packages?
Where conda puts environments and the package cache relative to its base install, and the file that lists them all.
Last updated
Conda installs self contained: environments go in envs/ and downloads in pkgs/, both inside the base install folder (miniconda3 or anaconda3). A Windows graphical install lands in your user profile, a macOS package install in /opt, a shell install wherever you ran it. The base path is the only variable; envs and pkgs hang off it.
Custom locations split the picture. envs_dirs and pkgs_dirs in .condarc (plus --prefix environments) scatter environments across disks, which is exactly when the registry file matters. Read environments.txt instead of assuming every environment sits under base.
Where Conda stores this, by platform
C:\Users\[Username]\miniconda3\envs
Graphical installs use this path; adjust for anaconda3 vs miniconda3. Packages cache in the pkgs sibling. Registry at %USERPROFILE%\.conda\environments.txt lists environments kept elsewhere.
/opt/miniconda3/envs
Package installs land in /opt; shell script installs default to ~/miniconda3 or /opt/miniconda3 depending on version. Run conda info --envs to list regardless of layout.
~/miniconda3/envs
Shell installs typically use ~/miniconda3 or ~/anaconda3. Same envs/pkgs split and same ~/.conda/environments.txt registry as other platforms.
Frequently asked questions
How do I list every conda environment, wherever it lives?
Open ~/.conda/environments.txt (or %USERPROFILE%\.conda\environments.txt). conda registers every environment there on creation, including ones made with --prefix outside the base tree. conda info --envs reads the same registry.
The pkgs folder is huge. How do I clean it safely?
Run conda clean --all. It empties the pkgs cache, tarballs and unused packages in one pass. Environments keep working: they hold linked copies, and anything missing refetches on the next install.
Notice an outdated path? Let us know.