Skip to content

Focused tools

10 data-diff jobs

Runtime

Your browser

Private Data Diff tools for JSON changes

Compare arrays by order, key, or counts; ignore volatile paths; merge three versions; and generate, validate, or apply RFC 6902 and RFC 7396 patches.

Every public operation stays in the active browser tab.

Choose a JSON change job

Each route owns a different matching, merge, or patch contract.

JSON Array Index DiffAlign ordered arrays without turning one insertion into a cascade of positional changes.Open tool
JSON Array Keyed DiffMatch records by an explicit primitive key instead of their array position.Open tool
JSON Array Set DiffIgnore order while retaining duplicate-value counts on both sides.Open tool
JSON Diff with Ignored PathsExclude known volatile fields before generating a structural patch report.Open tool
Three-Way JSON MergeCombine non-overlapping object changes and surface same-path conflicts explicitly.Open tool
JSON Patch GeneratorCreate add, remove, and replace operations that transform source into target.Open tool
JSON Patch ApplierApply a sequential JSON Patch to a cloned document with validation enabled.Open tool
JSON Patch ValidatorCheck operation shapes alone or validate sequential applicability against a document.Open tool
JSON Merge Patch GeneratorDescribe target object changes with nested values and null deletions.Open tool
JSON Merge Patch ApplierApply recursive object updates and whole-value replacements to a JSON document.Open tool

Start with ordered array alignment

See where values were retained, added, or removed without a positional cascade, or open a dedicated keyed, multiset, ignored-path, merge, or patch route.

Compare ordered arrays

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.

Ordered alignment report

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

A bounded structural workspace

Diffs can expose credentials, payloads, and unreleased configuration. The public workbench parses source only inside the current tab.

Every route states whether order, keys, duplicate counts, ignored pointers, common ancestry, sequential operations, or null-deletion semantics control the result.

The engine rejects unsafe integers, dangerous prototype-member names, oversized documents, excessive nesting, and reports over 10,000 entries.