conda-forge: Community Conda Package Channel
conda-forge is a community-maintained collection of conda packages distributed through a public channel on anaconda.org. Over 25,000 feedstocks (package repositories) produce builds for Linux, macOS, and Windows across multiple CPU architectures. Each feedstock contains a build recipe in its own GitHub repository, and automated infrastructure rebuilds packages when dependencies change or new platforms appear.
Note
The default Anaconda channel requires a paid license for commercial use in organizations with more than 200 employees. conda-forge has no such restriction.
Key Features
- Free for all use, including commercial, with no licensing restrictions
- Automated version bumps: bots monitor upstream releases on PyPI and open pull requests to update feedstocks within hours
- Broad platform coverage: Linux (x86_64, aarch64, ppc64le), macOS (x86_64, arm64), and Windows (x86_64)
- Community governance: an elected steering council and open RFC process manage policy decisions
- OCI mirror: an experimental mirror on GitHub Packages provides a vendor-independent distribution path using the Open Container Initiative specification
Default Channel Configuration
Conda and Miniconda ship with the Anaconda repository as the default channel. Switching to conda-forge removes the commercial licensing requirement:
conda config --add channels conda-forge
conda config --set channel_priority strictSetting channel_priority strict tells conda to prefer conda-forge when both channels provide the same package, preventing version conflicts from mixed channels.
Miniforge and Pixi use conda-forge as the default channel out of the box.
Package Submission Process
Anyone can submit a new package by opening a pull request to the staged-recipes repository with a build recipe. Once merged, conda-forge creates a dedicated feedstock repository and grants the submitter maintainer access. A single feedstock may produce multiple output packages (for example, a library and its Python bindings) through multi-output recipes.
conda-forge vs. the Anaconda Channel
| conda-forge | Anaconda channel | |
|---|---|---|
| Maintainer | Community volunteers | Anaconda, Inc. |
| License | Free for all use | Paid license required for organizations above 200 employees |
| Feedstocks / packages | 25,000+ feedstocks | ~7,500 curated packages |
| Update speed | Hours to days after upstream release | Weeks to months |
| Platform coverage | Linux (x86_64, aarch64, ppc64le), macOS (x86_64, arm64), Windows | Linux, macOS, Windows (x86_64 only) |
| Governance | Elected steering council, open RFCs | Internal to Anaconda, Inc. |
Pros
- No commercial licensing restrictions
- Faster package updates than the Anaconda channel
- Broader platform and architecture support
- Transparent, open-source build infrastructure
- Large maintainer community (thousands of contributors)
Cons
- Package quality depends on volunteer maintainers, not a dedicated curation team
- Mixing conda-forge with the Anaconda channel can cause solver conflicts
- Build infrastructure relies on donated CI resources, which occasionally leads to build backlogs
Learn More
Handbook Pages
- Understanding the Conda/Anaconda ecosystem
- Is Conda actually free?
- Why should I choose conda?
- uv vs. Pixi vs. Conda for scientific Python