The .env text stays in your browser. Secret-looking values are masked. Analytics and ads may load on the page.
Duplicate keys and unquoted values with spaces are flagged.
Missing or extra keys are reported.
How to lint a .env file
- 1
Paste .env
Paste the file you want to check. The sample has a duplicate key and an unquoted value with spaces. - 2
Optional example
Paste .env.example to see missing or extra keys. - 3
Lint
Read duplicate keys, unquoted spaces, and export prefixes. Secrets appear masked. - 4
Fix in your editor
Quote values that contain spaces and remove duplicate keys.
Why lint a .env file
Small mistakes in dotenv files fail at runtime. This page checks duplicate keys, unquoted values with spaces, export prefixes, and key drift. Secret-looking values are masked in the findings. The text is not uploaded to FindUtils. Analytics or ads on the page may still load.
Frequently Asked Questions
1
Does this upload secrets?
No. Linting runs in the browser. Secret-looking values are masked in the table. Analytics and ads may still load on the page.
2
What does it flag?
Duplicate keys, unquoted values with spaces, export prefixes, secret-looking values (masked), and drift versus .env.example.
3
Is this a parser for every dotenv dialect?
It is a lint for common dotenv files. It is not a full shell parser.
4
Can I compare two files?
Yes. Paste .env and .env.example.
5
Does it change my file?
No. It reports issues only.