How to compare two JSON files on Mac
To compare two JSON files on Mac with JSON Editor & Diff, place the original in Source and the other version in Destination, then check that both parse successfully. Inspect the path-based differences rather than judging line breaks alone. Keep the original files before formatting or repairing either version.
Decide which version is the reference
Give the two documents clear roles before comparing them. Source might be a saved configuration and Destination a proposed update. Record where each came from and preserve those originals so you can distinguish a difference in the inputs from a change made during cleanup.
Use non-sensitive sample data for a first check. API responses and configuration files can contain tokens or personal information, so avoid copying real secrets into screenshots or public debugging notes. A useful comparison needs trustworthy inputs, not merely two panes filled with text.
Load Source and Destination, then check validation
JSON Editor & Diff has two editing panes named Source and Destination, with validation while you type. Show Destination if the document opened with only Source visible, then place the second version there. Confirm both inputs parse before treating a missing comparison as meaning that nothing changed.
If an input is invalid, inspect the error and preserve a copy before using repair. The released repair feature removes comments and trailing commas; that does not establish that it can reconstruct arbitrary damaged JSON or recover the intended values. Formatting is a presentation change, while repair can change the text being compared.
- Keep copies of the two original files.
- Put the reference version in Source.
- Show Destination and add the second version.
- Resolve parsing issues before interpreting a diff.
Read the path and the value type
Use the app’s JSONPath-based output to locate an added, removed or changed value. In an illustrative configuration, changing retryCount from the number 3 to the text value "3" is a type change even though both contain the same digit. Follow the reported path back to both documents.
The JSON specification describes objects as unordered name/value collections and arrays as ordered sequences. A line-by-line view can exaggerate changes caused by spacing or object-key arrangement. Conversely, a changed array position can matter. Read the structure instead of assuming every visual movement has the same meaning.
Decide whether each difference is intended
For each reported change, ask whether it belongs in the proposed update. A different timestamp may be expected; a changed identifier or missing setting may need investigation. A diff identifies changes, but it cannot decide whether a server contract, configuration policy or business rule is still satisfied.
After an intentional edit, compare again and inspect the final saved result. Do not assume the app merged the documents or validated them against an external schema. Use editing, parsing and structural comparison as separate checks within the larger review process.
Questions
Can two differently formatted documents contain the same JSON values?
Spacing and object-key arrangement can differ without representing the same kind of change as a different value. Inspect the parsed structure and diff paths.
Why is there no usable comparison when one input is invalid?
Both documents need valid parsed values before a structural comparison is meaningful. Check the validation result first.
Does a clean diff prove my API change is safe?
No. It describes the compared inputs, not their compatibility with every application or schema.