Compare two .env files online

Why comparing .env files matters

When you clone a repository, your .env is often missing keys that exist in .env.example, either because the team added a new setting or because your copy is older. The app then fails at runtime with errors like PORT is not defined instead of telling you which key is missing.

This diff tool compares the two files and shows exactly what is missing, what is extra and what matches, so you restore the contract in seconds instead of guessing. Pair it with the validate tool so both files are checked for errors at the same time.

• Missing keys: present in .env.example but absent from your .env
• Extra keys: present in your .env but not in the example file
• Matched keys: defined in both files and ready to use

How to sync .env with .env.example

Follow these steps to bring any .env back in sync with its example file in under a minute.

1. Paste your current .env into the left editor
2. Paste the .env.example file into the right editor
3. Read the missing and extra keys highlighted in the report
4. Add the missing keys with the values your team expects
5. Run envy diff in the terminal to confirm the files match