Compare .env Files Online — Without Uploading Your Secrets
Every developer eventually pastes a .env into some online diff tool and then has a small heart attack: those were production secrets, on someone else's server. Comparing env files is a thirty-second job that should never require trusting a stranger's backend with your keys.
- ✓Generic text diff highlights changed lines, but what you actually need is: which keys are missing, which are extra, which changed.
- ✓Values should be masked by default — you are comparing key sets, not reading secrets aloud.
- ✓Comments, export prefixes, quoted values and values containing '=' all break naive parsers.
- ✓Our checker parses both files properly, groups the result into Missing / Extra / Changed / Same, and never uploads a byte.
FAQ
Is it safe to compare .env files online?
Only if the comparison happens locally. This tool parses and compares both files with JavaScript in your browser tab — open your network inspector and you will see zero requests carrying your data.
How are values shown?
Masked: first two and last two characters only (e.g. sk•••56). A Reveal toggle exists if you truly need full values, and it is gated so it cannot be flipped by accident.
What counts as 'changed'?
The same key present in both files with a different parsed value. Quoting style alone ("x" vs 'x') does not count as a change — the parsed values are compared.