Feature guide macOSWindows

Compare environment variables and HTTP responses without uploading them

Compare .env keys with values masked, flag malformed or duplicate variables, and compare raw or JSON-shaped HTTP responses by HTTP version, status code, and reason phrase, case-insensitive headers, and semantic JSON bodies.

Capability overview

How can I use environment and http comparison in Diff Anything?

Compare .env keys with values masked, flag malformed or duplicate variables, and compare raw or JSON-shaped HTTP responses by HTTP version, status code, and reason phrase, case-insensitive headers, and semantic JSON bodies.

Spot meaningful code changes with Smart Diff across 117 editor languages. Switch to Line Diff whenever you want an exact line-by-line review. Both views keep syntax highlighting and editing close at hand.

Diff Anything comparing two JSON files, with user records matched by id and a changed role value selected
Semantic mode lists changed paths and values. Here a Compare by id rule matches user records, so a reordered list shows only the real changes. View full size

.env files

Checking environment files between stages

Environment File mode shows a table with Variable, Left value, and Right value. The toolbar reads Values are masked by default, and each value stays hidden until you click its eye button. Reveal all asks for confirmation before showing every value in the view.

The Differences pane shows masked values as well, so the list can be shared on screen or in a screenshot without exposing a secret.

Each difference reads plainly, for example DATABASE_URL exists only on the left or API_KEY has a different value. Turn on Compare presence only when staging and production are supposed to use different values and you only want to know whether every variable exists on both sides. Duplicate variables and lines that are not valid assignments are reported as warnings.

Right → left and Left → right copy a variable to the other file without revealing its value. A typical check is .env.example against .env.production before a deploy, to catch a variable that was added in one place and forgotten in the other.

HTTP responses

Comparing two captured API responses

HTTP Response mode takes a raw response with its status line and headers, a saved JSON object with the status, headers, and body, or a body on its own. It compares the HTTP version, status code, reason phrase, headers, and body separately, so a changed header and a changed field in the body appear as two clear entries.

Header names are matched regardless of letter case, and repeated headers keep all their values. A JSON body is compared as data. Headers that change on every request are listed under Ignored headers and do not count as differences; the list starts with date, server, set-cookie, x-request-id, and traceparent. The app compares responses you have saved or pasted and does not send requests itself.

Copying a header or body value into the other response edits that capture in its own format, keeping its status text, header lines, and layout. Compare presence only and the Ignored headers list are both saved with a Pro profile.

Sharing and storage

Keeping secrets out of reports and history

Pro report export has Redact environment values switched on for environment files. Turning it off asks you to confirm before a report with real values is written.

Pro comparison history can keep a text snapshot of small files so they can be reopened later. For .env files, the snapshot keeps the variable names and masks every value before it is stored. To keep file contents out of history altogether, turn off Keep small text snapshots so history can reopen them in Settings.

Both modes are marked Preview on the free plan. They show the complete result for files up to 5 MB per side, within 10 new comparison sessions per day. Pro removes those limits and adds report export and the env and http command-line modes.

In the workflow

How to use it

  1. Open the two files

    Choose two .env files or two saved responses. Auto opens them in Environment File or HTTP Response mode.

  2. Set what counts

    Use Compare presence only for .env files, or edit Ignored headers for responses.

  3. Check each difference

    Reveal a single value only when you need to see it, and read header and body changes separately.

  4. Fix or share

    Copy missing variables across, save the file, or export a redacted report with Pro.

Useful in practice

When to use it

Related manual

Choose the right comparison mode

Choose sources, understand automatic detection, and select the engine that answers the question you are actually asking.

Read the guide

Direct answers

Questions about environment and http comparison.

Can a colleague watch my screen while I compare .env files?

Yes. Values stay masked until you reveal one, and copying a variable to the other file does not show its value.

How do I compare only which variables exist?

Turn on Compare presence only. Missing and extra variables are reported, and value changes are not.

Can I stop the Date header from showing as a change?

date is in the Ignored headers list by default. Add any other header that changes on every request, one name per line.

Are .env files kept in comparison history?

With Pro and snapshots on, an .env snapshot keeps the variable names with every value masked. Turn off snapshots in Settings to keep only file locations, dates, and settings.

Free & Pro: what’s included

Available on the Mac App Store and Microsoft Store. Free desktop use lets you try every comparison engine for files up to 5 MiB per side and 10 new comparison sessions per local day; collection previews show the first 100 items and PDF previews show the first 3 pages. The free CLI supports text and JSON. A one-time Pro purchase removes the preview and session limits and unlocks larger sources within technical limits, saved profiles and history, report export, three-way merge, folder synchronization, batch manifests, trusted preprocessors, and every CLI mode.

Next

See all Diff Anything capabilities.

Back to capabilities