Compare two .env files to see which variables are missing from each and which differ, with every secret masked on both sides and no way to unmask.
Waiting for two files
Nothing is uploaded. Secret values are masked on both sides — a row says that a value differs, never what it differs to.
The comparison appears here
Paste both files to see which variables are missing, which differ, and which match.
Secret values are masked on both sides and there is no way to unmask them here, because the useful answer is that a value differs rather than what it differs to. A variable present on the right and missing on the left is usually the one that breaks a deploy; the reverse is usually configuration nobody removed. Both are listed separately for that reason.
.env Comparison runs entirely on your device — nothing is uploaded, logged or stored.
You’re on the Free plan. Compare plans
The question this answers is "which variables does production have that my local file does not", which is the usual reason a deploy comes up missing a key and fails with a message about something unrelated.
It never shows what a secret differs to. A row says the value differs and shows both sides masked, with no unmask control anywhere. Knowing that `STRIPE_SECRET_KEY` differs between two environments is the whole of what you need; having both live keys side by side on a screen is not, and that is precisely the thing that goes wrong in a screen share.
The two directions are counted separately because they mean different things. A variable present on the right and missing on the left is usually a deploy that will fail. The reverse is usually configuration nobody removed. Reporting them as one number loses the distinction that makes the comparison useful.
Nothing is uploaded, logged or written to browser storage. Both files live in React state and are gone when the tab closes.
No, deliberately, and there is no control to turn it on. The useful answer is that a value differs; putting two live keys side by side on a screen adds risk and no information.
A variable present in the deployed environment and missing locally usually means your local setup is incomplete. The reverse — present locally, missing in production — is the one that breaks a deploy, and it is reported separately for that reason.
Yes, and that is a good use of it. Keys in the example that are missing from your real file are the ones you have not set yet.
No. Both are parsed in your browser, never logged and never written to browser storage.
Because they were not detected as secrets — a port, a hostname, a feature flag. Detection uses the name, the value's shape and its entropy, and a credential that looks like none of those is shown. Treat the masking as a help rather than a guarantee.