Identifies your project in Dotenv Vault.

Part of πŸ” Layer 2 Protection

The .env.project file uniquely identifies your project in Dotenv Vault. You SHOULD commit this file to source control. It is safe to do so. Aside: DON'T commit your .env or .env.me to source control.

You can think of it like a unique git url at GitHub. It identifies your project so that your teammates pull the correct .env file from Dotenv Vault.


Here's an example of what a .env.project file looks like:


The first thing you might notice is the formatting is the same as a .env file. This is intentional to allow for maximum future interoperability.

The DOTENV_PROJECT key is important. It is required. It is that value that identifies your project uniquely to the Dotenv Vaulting mechanisms.


You can generate a .env.project file at ui.dotenv.org or through the dotenv vault tool. The process is similar to creating and cloning your very first git repo on GitHub.

Ready to get started?

Join millions of developers that already trust and use Dotenv.

No credit card required
Dotenv for
  • Agencies
  • Startups
  • Enterprises
  • Bootstrapped Startups
  • Side Projects
  • Developers

πŸ’› Est. 2013