How Configpair works, what it does, and how to reach us.

Yes. Configpair runs entirely in your browser. The env content you paste never reaches any network — there is no upload, no API call, no server-side processing, and no storage. The comparison happens in-memory in your tab. Your data is as safe as the browser tab it is open in. If you close the tab, the data is gone.

Additionally, keys whose names suggest a credential (anything containing SECRET, TOKEN, PASSWORD, KEY, API and similar patterns) have their values masked by default in the output, so a screen share does not leak them. Click "Show secrets" to reveal them locally.

Configpair compares keys by exact string equality, case-sensitively. The most common causes of a false MISSING are:

• Case difference: DB_HOST and db_host are treated as different keys.
• Whitespace: A trailing space on one side (DB_HOST = value vs DB_HOST=value) — the tool strips spaces around the = sign, but a space inside the key name itself would make it different.
• Quoting: DB_HOST="localhost" and DB_HOST='localhost' both parse to the key DB_HOST with value localhost (quotes are stripped). But if one side has DB_HOST="localhost" and the other has DB_HOST=localhost, the values are identical after parsing — this is handled correctly.
• Multi-line values: Values that span multiple lines (using backslash continuation or quoted multi-line strings) are not supported. If your file uses these, the key may be parsed incorrectly. This is a known limitation (see below).

When in doubt, copy the two lines exactly as-is from your source files. The tool compares what it receives.

Click the "Show secrets" button in the toolbar above the result area. This toggles all masked values to their full visible state. The button label changes to "Hide secrets" while they are visible. Click it again to re-mask them.

This toggle is local to your browser tab. Refreshing the page returns to the default masked state. There is no way to permanently unmask a value because nothing is persisted.

No. Configpair does not store comparison results or provide shareable URLs. Once you close the tab or refresh the page, the comparison is gone. This is by design: the tool has no server and no database — it cannot save anything even if it wanted to.

If you need a permanent record:

• Export CSV — downloads a structured file you can open in any spreadsheet or text editor.
• Copy report — puts a plain-text summary on your clipboard to paste into a ticket, document, or commit message.

Do this before navigating away from the page.

Not in a single view. Configpair compares exactly two files — one on the left, one on the right. If your workflow involves three environments (for example, dev, staging, and production), run the tool twice: first compare dev vs staging, then staging vs production (or any pair you need).

A multi-file comparison view is not planned. The tool is deliberately narrow in scope: compare two files, show the difference, export the result.

Yes, Configpair is free. Every feature — paste, compare, toggle secret visibility, export CSV, copy report — is available immediately with no sign-up, no credit card, and no cap on how many files you compare.

There is no paid tier, no subscription, and no trial that expires. The tool runs in your browser and uses your CPU, not ours. It costs us nothing to serve, so charging for it would make no sense.

If a Team tier with server-side features (CI integration, automated drift detection, audit logs) is ever built, it would be a separate product on a different infrastructure model. The browser-based comparison tool this page describes would remain free.