Validate your .env file online

Common .env file mistakes this validator catches

Most broken deployments come from a .env file that looks fine until the app boots. This validator applies the exact rules the Envy CLI uses, so a file that passes here works everywhere else too.

• Duplicate keys, like two DATABASE_URL lines, where the last value silently wins
• Missing values, such as KEY= with nothing after the equals sign
• Invalid URLs in connection strings that fail at runtime instead of startup
• Spaces around the equals sign, which break some dotenv parsers
• Unquoted values with special characters like # or ; that get truncated
• Stray quotes and inline comments that change a value silently

How to validate a .env file before committing

Paste your .env file into the editor above and the report builds itself as you type. Every duplicate, empty value and unquoted special character is listed with its line, so you fix it before it reaches production.

Run the same checks from the terminal with envy validate to catch problems before a pull request is merged. Combine both: validate in the browser for quick fixes, then add envy validate to CI so a broken .env never ships. Compare the file against .env.example with the diff tool to catch missing keys before the merge.