No issues found. 6 keys: APP_NAME, PORT, DEBUG, DATABASE_URL, REDIS_URL, LOG_LEVEL
About .env Validator — Check & Lint .env File Online
A `.env` file looks trivial, but a single bad line — a duplicate key, an unquoted value with a space, a missing `=` — can silently break a deploy or leave a setting unset. This .env validator scans your file line by line and reports every problem with its exact line number, so you can fix config issues before they hit production.
It catches the mistakes that bite most often: duplicate keys, invalid key names, missing assignments, values with spaces that need quoting, trailing whitespace, empty values, and lowercase keys (flagged as a warning, since environment variables are conventionally UPPER_CASE).
Everything runs entirely in your browser. Your `.env` file — secrets, tokens, connection strings and all — never leaves your device, so it's safe to paste even production config.
Features
- Per-line errors and warnings with exact line numbers
- Detects duplicate keys, invalid names, missing "=", and empty values
- Flags unquoted values with spaces and trailing whitespace
- Tolerates the `export KEY=value` form; fully offline
How to use
- Paste your .env file into the input pane.
- Read the Valid / Invalid badge and the issues list in the output pane.
- Jump to each reported line number and fix the error or warning.
- Re-check until the badge reads Valid with no issues.
Frequently asked questions
What counts as an error versus a warning?
Errors are problems that break parsing or duplicate a key — a missing "=", an invalid key name, or a redefined key. Warnings are style or correctness smells that still parse: unquoted values with spaces, trailing whitespace, empty values, and lowercase keys. A file is "valid" when it has no errors, even if it has warnings.
Why should values with spaces be quoted?
Many dotenv parsers stop reading a value at the first space unless it is quoted, so `GREETING=hello world` may load only "hello". Wrapping it as `GREETING="hello world"` keeps the whole value intact across parsers.
Does it support the `export` prefix?
Yes. Lines like `export DATABASE_URL=...` are common when a .env file is meant to be sourced by a shell. The validator strips the leading `export ` before checking, so it will not flag it as an error.
Is it safe to paste production secrets?
Yes. All validation happens locally in your browser with no network requests. Nothing you paste — including API keys, passwords, and connection strings — is ever uploaded or stored.
Related tools
Everything runs locally in your browser — your input is never uploaded.