Skip to content

Global configuration in pixi#

Pixi supports some global configuration options, as well as project-scoped configuration (that does not belong into the project file). The configuration is loaded in the following order:

  1. XDG compliant configuration folder ($XDG_CONFIG_HOME/pixi/config.toml or $HOME/.config/pixi/config.toml)
  2. Global configuration folder, depending on the OS:
    • Linux: $HOME/.config/pixi/config.toml
    • macOS: $HOME/Library/Application Support/pixi/config.toml
    • Windows: %APPDATA%\pixi\config.toml
  3. Global .pixi folder: ~/.pixi/config.toml (or $PIXI_HOME/config.toml if the PIXI_HOME environment variable is set)
  4. Project-local .pixi folder: $PIXI_PROJECT/.pixi/config.toml
  5. Command line arguments (--tls-no-verify, --change-ps1=false etc.)


To find the locations where pixi looks for configuration files, run pixi with -v or --verbose.


The following reference describes all available configuration options.

# The default channels to select when running `pixi init` or `pixi global install`.
# This defaults to only conda-forge.
default_channels = ["conda-forge"]

# When set to false, the `(pixi)` prefix in the shell prompt is removed.
# This applies to the `pixi shell` subcommand.
# You can override this from the CLI with `--change-ps1`.
change_ps1 = true

# When set to true, the TLS certificates are not verified. Note that this is a
# security risk and should only be used for testing purposes or internal networks.
# You can override this from the CLI with `--tls-no-verify`.
tls_no_verify = false

# Override from where the authentication information is loaded.
# Usually we try to use the keyring to load authentication data from, and only use a JSON
# file as fallback. This option allows you to force the use of a JSON file.
# Read more in the authentication section.
authentication_override_file = "/path/to/your/override.json"

# configuration for conda channel-mirrors
# redirect all requests for conda-forge to the mirror
"" = [

# redirect all requests for bioconda to one of the three listed mirrors
# Note: for repodata we try the first mirror first.
"" = [
    # OCI registries are also supported

# disable fetching of jlap, bz2 or zstd repodata files.
# This should only be used for specific old versions of artifactory and other non-compliant
# servers.
disable_jlap = true  # don't try to download repodata.jlap
disable_bzip2 = true # don't try to download repodata.json.bz2
disable_zstd = true  # don't try to download repodata.json.zst

Mirror configuration#

You can configure mirrors for conda channels. We expect that mirrors are exact copies of the original channel. The implementation will look for the mirror key (a URL) in the mirrors section of the configuration file and replace the original URL with the mirror URL.

To also include the original URL, you have to repeat it in the list of mirrors.

The mirrors are prioritized based on the order of the list. We attempt to fetch the repodata (the most important file) from the first mirror in the list. The repodata contains all the SHA256 hashes of the individual packages, so it is important to get this file from a trusted source.

You can also specify mirrors for an entire "host", e.g.

"" = [

This will forward all request to channels on to Channels that are not currently mirrored on will fail in the above example.

OCI Mirrors#

You can also specify mirrors on the OCI registry. There is a public mirror on the Github container registry ( that is maintained by the conda-forge team. You can use it like this:

"" = [

The GHCR mirror also contains bioconda packages. You can search the available packages on Github.