Paste your .env and get a live report. Duplicates, stray quotes and inline comments are caught instantly, entirely in your browser.
Drop the file into the editor, or load a sample to see a clean parse instantly.
Metrics, a status banner and a per-key table update as you type.
Every issue points at a line number. Copy any key with one click.
Live validation, 100% in your browser
Keys parsed
6
Errors
0
Warnings
0
Duplicates
0
| Status | Key | Value | Line | |
|---|---|---|---|---|
| OK | PORT | 3000 | L2 | |
| OK | HOST | 0.0.0.0 | L3 | |
| OK | DATABASE_URL | postgres://localhost:5432/app | L4 | |
| OK | SECRET_KEY | dev-only-key | L5 | |
| OK | API_KEY | L6 | ||
| OK | FEATURE_FLAGS | beta,nightly | L7 |
6 entries · Last validated just now
Runs locally in your browser
A .env validator parses a .env file and flags anything that would break at runtime.
Most frameworks load these files with dotenv-style parsers that fail quietly. A validator surfaces the problem before your deploy does.
.env.example as the contract for every key your app reads.envy validate before you commit..env against the example with the diff tool so nothing is missing.envy validate in CI as a pre-deploy gate so broken configs never ship.Common questions about validating .env files
No. Every check runs in your browser with native parsing. Your file never leaves this tab, there is no upload button and no network request.