Quote & Escaping Validator

Quoting rules are where .env files disagree with each other. Standard dotenv treats KEY="a value" and KEY='a value' as fine, collapses whitespace inside quotes, and handles escapes differently from docker-compose or a shell export. A file that works locally can corrupt a secret in production if a quote is unclosed or a backslash hangs at the end of a line.

The Quote & Escaping Validator reads every line and reports unclosed quotes, mixed quote styles, lone trailing backslashes, and empty quoted values — each with its line number, so the fix is mechanical. Clean output means the file parses identically across the common dotenv implementations.

It never uploads anything; the parse runs in your browser.

• Unclosed quotes: KEY="abc caught per line.
• Balanced-quote check: odd quote counts reported.
• Mixed quote styles: nested conflicts inside a value.
• Trailing backslash: \\ at end of line flagged.
• Empty quoted values: KEY="" surfaced (optional).
• Severity: each issue is error or warning.
• Line numbers: jump straight to the fix.
• Private & free: all in-browser.

1. Paste your .env into the input, or load the sample.
2. Pick whether to also see empty quoted values.
3. Click Validate. Each issue is listed with line and severity.
4. Fix the flagged lines and re-validate until clean.

Example 1 — Truncated secret. A password with a trailing backslash got cut off in .env. The validator flags the lone backslash at line 23 before it breaks auth.

Example 2 — Unclosed quote. KEY="alpha\nbeta without a closing quote parses fine in some libraries and badly in others. The validator nails the line.

Example 3 — Mixed quotes. A value contains an apostrophe inside double quotes, which is legal, but a double quote inside an unquoted bare value is not; the report separates the two.

Example 4 — Empty string semantics. KEY="" and KEY=(nothing) behave differently in some parsers. The optional check surfaces them so the team agrees on one style.

Example 5 — Pipeline drift. After tests pass on Node but fail under docker, the validator finds the offending escaped colon in a URL value.

• Cross-parser safety: catch what dotenv libraries disagree on.
• Locatable: line numbers for every issue.
• Severity aware: errors vs warnings.
• Quoted semantics: handles both quote styles.
• Private: no data leaves the browser.
• Free: use as often as you like.