# Configuration YAML overview

Your Bitrise CI configuration is defined and stored inside YAML files. When you modify your configuration on the GUI of the Workflow Editor, you modify YAML files. The files define:

- The format version of [the Bitrise CLI](/bitrise-ci/bitrise-cli/installing-and-updating-the-bitrise-cli) the build will use. The format version number determines what Bitrise CLI versions will be able to run the configuration.
- The type of the project (for example, Android or iOS).
- The default [source of Steps](/bitrise-ci/references/steps-reference/step-reference-id-format) used.
- The [stack](/bitrise-ci/configure-builds/configuring-build-settings/setting-the-stack-for-your-builds#setting-the-stack-in-the-configuration-yaml) and [machine type](/bitrise-ci/configure-builds/configuring-build-settings/setting-the-stack-for-your-builds#setting-the-stack-in-the-configuration-yaml) of the build and of the specific Workflows or Pipelines.
- [Build triggers](/bitrise-ci/run-and-analyze-builds/build-triggers/about-build-triggers) based on Git events.
- App- and Workflow-level [Environment Variables](/bitrise-ci/configure-builds/environment-variables#setting-env-vars-in-the-configuration-yaml) accessible to the build.
- The Workflows and Steps used in the build.

The default configuration YAML file is called `bitrise.yml`. Each Bitrise project has a `bitrise.yml` file. You can find detailed reference information on the `bitrise.yml` file: [Configuration YAML reference](/bitrise-ci/references/configuration-yaml-reference).

:::tip[Work on your configuration locally]

The [offline Workflow Editor](/bitrise-ci/bitrise-cli/installing-and-upgrading-the-offline-workflow-editor) runs on your own computer: you can edit your project's configuration YAML file without logging in to [bitrise.io](https://www.bitrise.io/), and your configuration never leaves your network. It offers most features of the Workflow Editor.

:::

Configuration YAML files can be stored on:

- The Bitrise website. This is the default setting.
- Your own Git repository.

When you store your configuration in your own Git repository, the [Workflow Editor can push changes directly to it from the browser](/bitrise-ci/configure-builds/configuration-yaml/storing-an-apps-configuration-yaml#updating-a-bitriseyml-stored-in-the-repository): select a branch to load, make your changes, and commit back without leaving Bitrise. This feature is available for repositories hosted on GitHub and GitLab. Bitbucket Cloud doesn't support it.

If you store your YAML configuration in your own Git repository, you can also use a modular YAML configuration. This means that in addition to the default `bitrise.yml` configuration file, you have one or more additional YAML files containing additional configuration. This allows breaking down large configurations into smaller, modular components, as well as efficient reuse of configuration segments across multiple different repositories and Bitrise projects: [Modular YAML configuration](/bitrise-ci/configure-builds/configuration-yaml/modular-yaml-configuration).

:::important[Enterprise only]

A modular YAML configuration is only available to Workspaces on an [Enterprise plan](https://bitrise.io/pricing). For now, it is not available if you store your YAML configuration on bitrise.io.

:::
