JSON Merge — Deep Merge Two JSON Documents Online

Combine a base JSON document with an overlay using deep or shallow merge. The result updates automatically, and a live conflict preview lets you control arrays, null handling, and conflict resolution.

Loading…
JSON merge, combine documents playbook
Merge base and overlay JSON with control over depth, arrays, conflicts, and nulls. Preview conflicts before copying.

Developer notes

Both documents must be valid JSON. Automatic merge — the result updates when both inputs are valid (debounced) and when you change options; no Merge button. B wins is the default conflict strategy: overlay values override base scalars. Error on conflict blocks output and lists conflicting JSON paths. Union by key merges arrays of objects like a database upsert on `id`. Ignore nulls skips null values from the overlay — useful for sparse patches. This is not RFC 7386 Merge Patch — the tool outputs a merged document, not a patch file. After merging, use JSON diff to verify against your expected baseline.

JSON merge options

Merge depth
Deep merges nested objects key by key; shallow replaces entire nested objects and arrays from the overlay.
Array strategy
Replace (default), concatenate, concatenate unique values, or union arrays of objects by a key field.
Union key
Field used to upsert objects when the array strategy is union by key, similar to a database merge on `id`.
Conflict resolution
Overlay wins (default), base wins, or error on conflict to block output and list conflicting paths.
Null handling
Ignore null overlay values (default), merge nulls, or delete keys when overlay sets null.
Indent size
Spaces per indentation level in the formatted merged output.
Indent style
Spaces or tabs for output formatting.

When teams pick this route

Merge environment config (base + staging overlay). Combine package.json overrides. Stitch partial API responses. Apply feature-flag deltas to a defaults file.

Worked examples

Deep merge config

Base (A)

{"app":{"name":"api","port":3000},"features":{"auth":true}}

Overlay (B)

{"app":{"port":8080},"features":{"metrics":true}}

Port becomes 8080; both feature keys remain after a deep merge with overlay winning on conflicts.

Array concat

Base (A)

{"tags":["alpha","beta"]}

Overlay (B)

{"tags":["gamma"]}

Tags become `["alpha","beta","gamma"]` with array strategy set to concat.

Navigate related JSON tools

Compare merged output in JSON diff. Normalize key order first with JSON sort. Validate with the JSON validator, fix syntax with JSON repair, or browse the JSON tools hub.

JSON merge FAQ

Merge vs diff, arrays, and nulls

Do I need to click Merge?

No. The merged JSON updates automatically when both documents are valid and whenever you change merge options.

How is JSON merge different from JSON diff?

JSON diff highlights differences between two documents. JSON merge produces a single combined document using your depth, array, and conflict rules.

Which document wins on conflicts?

By default, the overlay (document B) wins on scalar conflicts. You can switch to base wins or error on conflict.

What is shallow vs deep merge?

Deep merge combines nested objects key by key. Shallow merge replaces entire nested objects and arrays from the overlay.

How are arrays handled?

Choose replace (default), concat, concat unique, or union by key for arrays of objects.

What happens when the overlay contains null?

With ignore nulls (default), nulls in the overlay are skipped. With merge nulls, they are written as null. With delete on null, the key is removed from the result.

Do you support three-way merge?

No. This tool merges exactly two JSON documents (base and overlay).

Is this JSON Merge Patch (RFC 7386)?

No. The output is a merged JSON document, not an RFC 7386 patch operations file.

Validate, format, repair, compare and explore JSON in your browser, alongside the JSON minifier and converters.