---
title: Configure project paths
description: The path section of the filebeat.yml config file contains configuration options that define where Filebeat looks for its files. For example, Filebeat...
url: https://www.elastic.co/docs/reference/beats/filebeat/configuration-path
products:
  - Beats
  - Filebeat
applies_to:
  - Elastic Cloud Serverless: Generally available
  - Elastic Stack: Generally available
---

# Configure project paths
The `path` section of the `filebeat.yml` config file contains configuration options that define where Filebeat looks for its files. For example, Filebeat looks for the Elasticsearch template file in the configuration path and writes log files in the logs path. Filebeat looks for its registry files in the data path.
Please see the [Directory layout](https://www.elastic.co/docs/reference/beats/filebeat/directory-layout) section for more details.
Here is an example configuration:
```yaml
path.home: /usr/share/beat
path.config: /etc/beat
path.data: /var/lib/beat
path.logs: /var/log/
```

Note that it is possible to override these options by using command line flags.

## Configuration options

You can specify the following options in the `path` section of the `filebeat.yml` config file:

### `home`

The home path for the Filebeat installation. This is the default base path for all other path settings and for miscellaneous files that come with the distribution (for example, the sample dashboards). If not set by a CLI flag or in the configuration file, the default for the home path is the location of the Filebeat binary.
Example:
```yaml
path.home: /usr/share/beats
```


### `config`

The configuration path for the Filebeat installation. This is the default base path for configuration files, including the main YAML configuration file and the Elasticsearch template file. If not set by a CLI flag or in the configuration file, the default for the configuration path is the home path.
Example:
```yaml
path.config: /usr/share/beats/config
```


### `data`

The data path for the Filebeat installation. This is the default base path for all the files in which Filebeat needs to store its data. If not set by a CLI flag or in the configuration file, the default for the data path is a `data` subdirectory inside the home path.
Example:
```yaml
path.data: /var/lib/beats
```

<tip>
  When running multiple Filebeat instances on the same host, make sure they each have a distinct `path.data` value.
</tip>


### `logs`

The logs path for a Filebeat installation. This is the default location for Filebeat’s log files. If not set by a CLI flag or in the configuration file, the default for the logs path is a `logs` subdirectory inside the home path.
Example:
```yaml
path.logs: /var/log/beats
```