Skip to content
Format
JSON
Limit
1 MiB total
Runtime
Browser

Merge JSON changes from a shared base

Combine non-overlapping object changes and surface same-path conflicts explicitly.

Local processingNo sign-upNo presets or upload

Merge three JSON versions

Each document is capped at 512 KiB; combined input is capped at 1 MiB.

Tool Swim does not upload, fetch, save, log, or create presets from these values.

Merge candidate and conflicts

The report states the algorithm, semantics, paths, counts, or conflicts used as proof.

What this tool proves

Explicit, bounded structural semantics

The merger computes changes from the shared base. A path changed differently on both sides remains at the base value in the candidate and appears in the conflict list; arrays are treated as whole values.

Conflicts are never guessed away

The merger computes changes from the shared base. A path changed differently on both sides remains at the base value in the candidate and appears in the conflict list; arrays are treated as whole values.

Each document is capped at 512 KiB, combined input at 1 MiB, traversal at 100,000 values and 100 levels, reports at 10,000 entries, and output at 1 MiB. Source and results stay in the active browser tab.

Parsing and comparison semantics

Inputs use the browser's JSON parser. Duplicate object names therefore keep their last value, object member order is ignored, array order is preserved unless the selected tool explicitly says otherwise, and integers outside JavaScript's safe range are rejected instead of rounded silently.

Primary references

Questions and answers

Related Data Diff tools