conda-forge /miniforge

A conda-forge distribution.

★ 10,364⑂ 554👁 64⑃ 359● 516▤ 121
ShellNOASSERTIONCreated 2019-11-14conda-forge.org/download
Download: Release 26.9.4-226.9.4-2 ↓22026-11-06
+0
Daily
10,364
stars
554
forks
64
watchers
359
prs
516
issues
121
releases

README

Miniforge




This repository holds the minimal installers for Conda and Mamba specific to conda-forge, with the following features pre-configured:

 Packages in the base environment are obtained from the conda-forge channel.
 The conda-forge channel is set as the default (and only) channel.

We put an emphasis on supporting various CPU architectures (x86_64, ppc64le,
and aarch64 including Apple Silicon) as well as the stability of this
installer.

 Goals

The goal of this installer is to provide you with an entry point to the
conda and mamba commands. If these two commands execute correctly, then this
installer has achieved its goal.

If you have issues with specific packages, please report them to the
associated feedstock. You may find the feedstock associated with a package using
our website

 Usage

Miniforge provides installers for the commands conda and
mamba.  Once the installer for your OS
and architecture has been executed, you should be able to use these commands in
a terminal.

 conda/mamba usable in any terminals

However, with the default choices of the Windows installer, these commands are
only available in the "Miniforge Prompt". To be able to use these commands in
other terminals, one needs to initialize conda for your shell by running in
the Miniforge Prompt.

sh
conda init


Note that one can also just add the C:\Users\myusername\miniforge3\condabin\ folder
to the path environment variable
manuallyto-add-a-path-to-the-path-environment-variable)
so conda and mamba may be used more conveniently from any command prompt with limited
chance of software conflicts.

The same situation arises on Unix if you use the non-interactive install.
Initialization can be done by calling conda with its full path, with something like

sh
~/miniforge3/bin/conda init


 Automatic activation of environments

By default, once conda has been initialized for your shell, the base environment is
activated so that the command python corresponds to the base Python provided by
Miniforge and conda install installs packages in the base environment. This can
be convenient for but it is cleaner to deactivate this automatic activation with

sh
conda config --set auto_activate false


and use conda or mamba to create and activate other environments, with for example
(to create an environment called my_project)

sh
conda create --name my_project jupyterlab numpy pandas
conda activate my_project
 Now you can start jupyter lab
jupyter lab


Finally, it is also possible to add to your shell configuration file
(typically ~/.bashrc or ~/.zshrc on Unix;
on Windows, edit with notepad $PROFILE) the activation command.

 Requirements and installers

Latest installers with Python 3.14 () in the base environment:

| OS      | Architecture                  | Minimum Version | File                                |
| ------- | ----------------------------- | --------------- | ----------------------------------- |
| Linux   | x86_64 (amd64)                | glibc = 2.17   | Minifo

Top issues

Discussions

Latest release

Release 26.9.4-2 26.9.4-2 2026-11-06
What's Changed
 Test that conda init works on windows by @isuruf in https://github.com/conda-forge/miniforge/pull/916
 Run offline tests as soon as the build test passes by @isuruf in https://github.com/conda-forge/miniforge/pull/917
 Bump the github-actions group with 2 updates by @dependabot[bot] in https://github.com/conda-forge/miniforge/pull/918
 Add Windows ARM64 installer builds and tests by @ClayWarren in https://github.com/conda-forge/miniforge/pull/903

 New Contributors
 @ClayWarren made their first contribution in https://github.com/conda-forge/miniforge/pull/903

Full Cha

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON