.env Validator
Check dotenv assignments for invalid names, missing equals signs, unclosed quotes, duplicate keys and unresolved Git markers. Inspect line numbers while keeping input values in your browser.
Find Dotenv Syntax Errors by Line
Uses Node.js dotenv syntax. Files and values stay in this browser.
.env Validator: how to use it
- Paste or open a .env file and select Validate .env. Use Load example to check a document with a multiline value and three issues.
- Read the physical line numbers. A duplicate points to the earlier assignment so you can compare the values in your source.
- Fix the assignments and validate again. Check required variables and accepted values separately in the application that loads the file.
Limits and notes
Each input and resolved document supports up to 262,144 UTF-16 code units and 10,000 lines. Uses Node.js dotenv syntax with explicit diagnostics for malformed assignments and duplicate names. Displays up to 100 issues. Checks syntax and key uniqueness without expanding references, running shell commands or checking application-specific settings.
How your privacy works →.env Validator: common questions
Does KEY= count as missing syntax?
KEY= is a valid assignment of the empty string. A line with just KEY needs an equals sign.
When is # part of the value?
A # inside a quoted value is preserved. Outside quotes it starts a comment. Quotes can wrap a value that spans physical lines.
Does a valid file guarantee my application will accept it?
A passing result establishes syntax and uniqueness under the tool’s Node.js dotenv rules. Required names, value ranges and variable expansion depend on the loader and application.