Validate, compare, and diff `.env` files against one `.env.example` template.

Compare `.env.local`, `.env.dev`, `.env.qa`, and `.env.prod` against your reference template to see exactly which keys are missing, extra, or different.

or Drag multiple env files here.

.env.example

0 required keys without defaults. 0 template defaults will not count as missing.

1Environments
0Missing required
0Undocumented
0Duplicate groups
0Malformed lines
0Warnings

Paste or upload a template and at least one environment file to start.

Add more tabs with the plus button if you want to compare local, QA, and production files against the same reference contract.

FAQ

How this environment file validator works

Can I use this to compare or diff two .env files?

Yes. Load one file as the reference template and the others as environments to diff them key by key. The tool highlights which keys are missing, extra, duplicated, or differently defined across every file.

Does this tool upload any environment files?

No. Parsing, validation, and comparison all happen locally in the browser.

What counts as a missing key?

Only template keys without default values count as missing. Defaulted template values are treated as optional fallbacks.

Are template duplicates and malformed lines still validated?

Yes. Duplicate keys and malformed lines stay visible in the reference template and in every environment file.

Which dotenv syntax is supported?

The validator covers common dotenv syntax: KEY=value assignments, export prefixes, inline comments, quoted values, quoted hashes, and multiline quoted values. Variable references like $NAME or ${NAME} are treated as plain string values and are not expanded at runtime.