Diff AnythingFile and folder comparison for Mac and Windows

No. Comparison is local. The application has no account, cloud comparison service, analytics, or telemetry.

Compatible spreadsheet formats can use the shared spreadsheet comparison even when their extensions differ, matching structured formats use their semantic engine, two files in different data formats, such as JSON and TOML, are compared by their data, two folders use folder comparison, an archive beside a folder is compared as the folder it holds, and other compatible inputs fall back to text. You can always choose a concrete mode.

Yes. Diff Anything compares Excel, OpenDocument, and Apple Numbers workbooks in any pairing, sheet by sheet and row by row. Rows are matched by their content, or by key columns you choose under Match rows by, so an inserted row is one added row. A CSV or TSV file opened beside a workbook is compared by cell values with one sheet, the first by default; choose another under Compare with sheet. Values are compared as stored text, so 20 and 20.0 count as different. Formulas are compared between two workbooks of the same format; formatting, charts, macros, and workbook layout are not compared. Sheets are matched by name, and a Numbers file shows each table under its own name, “Table 1” unless you renamed it. Before you compare a Numbers file with an Excel or ODS copy, give the table in Numbers the same name as the other file's sheet; otherwise its rows show as removed and added.

Yes. The Microsoft Store version on Windows includes the command line. On a Mac, install the free command-line helper, which adds the diff-anything command to the Mac App Store version and uses the Pro purchase made in the app on the same Mac. The CLI supports difference exit codes, machine-readable output, Git difftool configuration, and a Git diff driver for file types you assign in .gitattributes. The free CLI compares text, JSON, and Jupyter notebooks; Pro adds every other CLI mode, the merge driver, the merge tool that git mergetool opens in a window, batch manifests with JSON, JUnit, or SARIF output, and --fail-on breaking for API schema checks.

Three-way merge is part of Pro. Choose a common Base for Ours and Theirs. JSON, YAML, TOML, and INI files are merged by their data, value by value, so a conflict appears only where both sides changed the same value differently; other files merge by lines. Focused source diffs show what each side changed from Base, and independent line edits, or edits to separate words of the same line, combine automatically. When both sides change the same words, the result is a conflict; a value is never assembled from parts of each side. Overlapping edits offer Ours, Theirs, Ours then Theirs, Theirs then Ours, and Base choices, with conflict navigation, bulk side choices, and reset. The result remains editable and cannot become the current right source while conflict markers remain; saving that modified source is a separate action.

Yes. Pro folder synchronization previews create, update, delete, and move actions, rejects stale plans, applies the reviewed selection transactionally with progress and cancellation, preserves supported metadata, uses durable recovery journals and restart-safe rollback, and offers one-click undo after a successful synchronization.

ZIP/ZIP64 and ZIPX, ZIP-based packages, 7z, RAR 1.3 through 7, TAR and compressed TAR variants, plus standalone Gzip, Bzip2, XZ, and Zstandard streams. Encrypted ZIP, 7z, and RAR archives are supported, as are numbered 7z and common RAR volume sets. Split ZIP, ACE, ARJ, CAB, ISO/disk images, and filesystem images are not archive-mode inputs.

Selected text, JSON, YAML, TOML, INI, property list, XML, environment-file, HTTP-response, and API-schema differences can be applied in either direction. JSON, TOML, INI, XML property list, and HTTP targets are edited in place, so their comments, indentation, and layout are kept; a binary property list is compared but never written. Between two data formats, a change is written in the target's own format, or refused, with the reason, where that format cannot hold it. YAML and XML targets are rewritten from their parsed data after a confirmation, which drops comments and custom layout. A JSON API schema keeps its layout; a YAML schema is rewritten after a confirmation.

Yes. In Settings → Difference colors, choose Blue and yellow. Additions become blue and removals yellow, in light and dark themes. Written difference descriptions provide another way to check what changed. The setting is part of the free plan.

Yes. With Pro, open a file that contains conflict markers and choose Resolve: its conflicts open in the merge workspace, every line outside them stays as Git merged it, and the resolved file is saved in its own encoding and line endings. Diff Anything can also be Git's merge tool, so git mergetool opens each conflicted file in its merge window: the Microsoft Store version on Windows directly, and the Mac App Store version through the free command-line helper. Seeing the conflicts in a file is free.

Yes. The interface is available in English, German, and French. It follows the system's language or the one chosen in Settings, and switches at once.

Yes. With Reopen tabs from last time in Settings, on by default, the tabs that were open reopen in their order, with their comparison types, options, and views, and files and folders are read again from disk. Pasted text and unsaved edits are not kept.

Yes. The accessible workspace (Command-Shift-A on a Mac, Control-Shift-A on Windows) lists every difference in words with its location and both values, and lets you review, ignore, and apply changes from the keyboard. On a Mac it opens automatically when VoiceOver is running.