File A
Findings
0 issuesNo problems detected — every line is well-formed with a unique key.
Values are only ever compared, never logged. Keep secrets in these files — they stay in your browser.
No problems detected — every line is well-formed with a unique key.
Validate and compare .env files in your browser. Check syntax and duplicates, then diff your local secrets against your .env.example — all locally, nothing uploaded.
Run the diff against your local file to guarantee the example lists every key you actually use — and nothing stale.
Production behaves differently from your laptop. Diff your local .env against the deployed file (via a safe channel) and find the changed key.
Send them the validator findings window as the checklist: add these keys, remove these, fix these values.
"Duplicate key" you didn't expectWhy: The same key appears twice — maybe once in an export NODE_ENV=… line and once plain, or across two pasted stanzas.
Fix: Search the file for the key name and merge the duplicates; keep the last occurrence's value.
Spaces-around-equals on a health check lineWhy: Some generators emit KEY = value with spaces, which this validator flags as fragile.
Fix: Normalize to KEY=value — jjdotenv and most runtimes accept only the tight form.
A line you expect to be valid is flagged unquotedWhy: Values containing # comments or spaces benefit from quotes; without them parsing is ambiguous.
Fix: Wrap the value in double quotes and escape inner quotes/backslashes as your runtime expects.
Every line of your .env file: invalid key names, empty values, duplicate keys, stray spaces before/after the key, spaces around the equals sign, and lines that aren't a comment, blank line or KEY=VALUE pair. Values are never logged or sent anywhere.
To check your local .env against your .env.example (or a teammate's). You get three lists: keys in the example that are missing from your file, keys that exist only in yours, and keys whose values differ.
The diff lists key names and (truncated) values, and the report you copy/download names keys but never values unless a value differs from the example. Real secret values are never transmitted anywhere.
dotenv-compatible names: start with a letter or underscore, then letters, digits and underscores. Lines like 123=value or MY-KEY=value are flagged invalid.
Yes — and this is the dangerous one, because most loaders silently keep the last occurrence. The validator flags every definition of a key that appears more than once.
Yes. Lines like export NODE_ENV=production are parsed too (the export keyword is stripped), matching what dotenv with export support and shell sourcing do.
Last reviewed September 2026 · DataFormatter team — this tool processes data locally in your browser.