Env File Validator
Validate .env file format and compare against .env.example to find missing, extra, and duplicate keys. Color-coded results highlight issues instantly.
.env File
.env.example File
Paste your .env file content and click Validate to check for issues
Env File Validator
Validate .env file format and compare against .env.example to find missing, extra, and duplicate keys. Color-coded results highlight issues instantly.
Features
- Validate KEY=VALUE format with detailed error and warning messages
- Compare .env against .env.example to find missing and extra keys
- Detect duplicate keys, unquoted values with spaces, and empty values
- Color-coded results: green for matching, red for missing, yellow for extra keys
- Copy a full validation report to clipboard for sharing with your team
How to use
- Paste your .env file content in the left panel.
- Optionally paste your .env.example file in the right panel to compare keys.
- Click Validate to see format warnings and key comparison results.
Tips & Best Practices
- All processing happens in your browser — no data is sent to any server.
- Use the copy button to quickly transfer results to your clipboard.
- The tool works offline once loaded — no internet connection required for processing.
- Check the FAQ section below for answers to common questions.
- Share this tool with colleagues using the social sharing buttons.
FAQ
What format issues does it detect?
The validator checks for missing equals signs, invalid key names (keys must start with a letter or underscore), unquoted values containing spaces, empty values, and duplicate keys. Each issue includes the line number and a clear description.
How does the key comparison work?
When you provide both .env and .env.example content, the tool compares their keys. Missing keys are in .env.example but not in your .env, extra keys are in your .env but not in .env.example, and matching keys appear in both files.
Is the .env.example panel required?
No. You can validate just the .env file format without providing an .env.example. The comparison section will only appear when both files are provided.
Does it check the values of environment variables?
The tool validates the format of values (quoting, empty values) but does not evaluate or validate the actual content of values. It focuses on structural correctness and key consistency.
Is my .env data secure?
Absolutely. All validation happens entirely in your browser. No data is sent to any server. Your environment variables, secrets, and API keys never leave your device.
Can I use this for Docker .env files?
Yes. The KEY=VALUE format is the same for Docker .env files, docker-compose environment files, and standard dotenv files. The validator works for all of these formats.