Debug a Broken .env File
Find why your environment variables aren't loading.
💡 Catches duplicate keys, spaces around =, unquoted values, and naming-convention issues — then gives you a cleaned, sorted file and a ready-to-commit .env.example. Your secrets are parsed entirely in your browser and never uploaded.
debugging tips
Duplicate keys and spaces around "=" are common causes of "my env var is wrong" — both are flagged with line numbers.
Unquoted values with spaces often get truncated; the linter points these out so you can quote them.
When a key is defined twice, most loaders use the last one — the tool shows you which.
Paste a real file safely — it's never uploaded.
Jak to funguje
Proč používat náš?
Also check out…
Generate a .env.example
Create a .env.example from your real .env so teamm
Clean Up a Messy .env
Sort, de-duplicate, and normalise an .env file.
Enforce .env Naming Conventions
Check that environment variable names follow UPPER
Validate .env Before Deploying
Catch config mistakes before they reach production