Review configuration changes without losing structure

The job to be done

Find the setting that changed, not the lines that moved.

Formatters and deployment tools rewrite configuration files constantly. A key moves or a generated list comes out in a new order, and a line diff buries the one value that matters: a different port, a removed feature flag, or a variable that production does not have yet.

Diff Anything reads JSON, YAML, TOML, INI, property lists, and XML as data, even when the two files use different formats, and lists each change with its path, for example $.services.api.port, beside the old and new value. Environment files are read as named variables whose values stay masked until you choose to show one.

Recommended path

Review one environment against another.

Put the configuration you trust on the left, such as the file deployed today, and the proposed version on the right.

1. Open the pair

   Choose two JSON, YAML, TOML, INI, property list, XML, or .env files, or paste their contents. Auto picks the mode from the file name and content, and a JSON file beside a TOML or YAML file is compared by its data.

2. Hide the changes you expect

   In JSON, YAML, TOML, INI, or property list mode, open Semantic rules and add Ignore paths for generated fields such as a build timestamp. Recommended rules proposes more rules from the differences it finds.

3. Pair list items correctly

   Records with a unique id, _id, uuid, or key field are paired automatically. For others, add an Array keys rule, for example $.services = name, or list the path under Unordered array paths. XML elements are paired by a key attribute such as id or name; add the parent element under Unordered elements when sibling order carries no meaning.

4. Check variables without exposing them

   Environment File mode lists missing, extra, and changed variables with their values hidden. Turn on Compare presence only when just the names must match.

5. Copy the corrections you approve

   Pick a difference and copy it across with Right → left or Left → right. JSON, TOML, INI, and XML property list targets are edited in place and keep their comments and layout; YAML and XML targets are rebuilt from parsed data after a confirmation, which drops comments and custom layout.

Capabilities involved

Three parts of Diff Anything do the work here.

Limits to know

Where the rules apply and where they stop.

Semantic rules, including Ignore paths, Array keys, and Numeric tolerance, work in JSON, YAML, TOML, INI, and property list mode, including pairs of two different formats. XML offers Unordered elements for child order, and .env offers Compare presence only.

Values are compared as parsed, and numbers by value, so 1 and 1.0 are equal. Lists without an id-like field are matched by position, so an inserted item can mark later positions as changed; add an Array keys rule when records have another identifying field.

Masking covers the comparison view, and exported reports redact environment values by default. Pro history snapshots of .env files keep variable names with every value masked, and you can switch snapshots off in Settings.

The free plan runs every configuration format in the app with complete results for files up to 5 MB each and 10 comparisons per day. Saved profiles, history, report export, and command-line runs of every mode except text, JSON, and notebooks need Pro.

Related manual

Choose the right comparison mode

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

Its sections cover start with the review question, choose and load sources, how automatic mode resolves, read text and structured results, compare spreadsheets across formats, choose smart diff or line diff for code, navigate and review, resolve a three-way merge, recover from input problems. Use it when you are ready to reproduce this workflow with your own project data.

Direct answers

Questions about this use case.