JSON Merger

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from JSON Merger

JSON Merger helps you merge two structured inputs in JSON. A deep merge combines nested content according to the tool’s merge rules, making it useful for comparing base settings with overrides. This is useful when the information is already available but its structure, presentation, or consistency makes it difficult to inspect. Work with a representative sample first so that you can recognize the expected result before applying the same operation to a larger document. Merging is not the same as appending every value. A shared key may be overwritten, and arrays may use a different policy from objects. Keep the original input available while reviewing the output. The important check is whether the result still has the intended values and relationships, rather than whether it merely looks neater. Test one conflicting key and one array before relying on a merge for real configuration.

Guide updated October 13, 2026

How to use this tool

1. Place the JSON input in the relevant editor. If the tool compares or combines documents, keep each document in its own input.
2. Select the available settings for the operation you need. Test one conflicting key and one array before relying on a merge for real configuration.
3. Review any syntax errors before interpreting the result. A valid document with the wrong structure needs a different fix from malformed input.
4. Inspect the changed portion and at least one unchanged portion. Keep a copy of the original JSON until the result has been checked in its destination.

SEE IT IN PRACTICE

A worked example

First: {"a":1}; second: {"b":2}

{"a":1,"b":2}

Disjoint keys can coexist in the result. Conflicting values require closer review because merge direction and array rules matter.

Decide the conflict policy

Before merging two objects, identify which document should win when both define the same path. Arrays add another decision: replacement, concatenation, and item-by-item merging have different outcomes. A null can mean an intentional override or a missing value, depending on the workflow. Build a tiny conflict example that matches your real data and review the result explicitly.

A merge is not a patch

A merge combines documents using a conflict policy; a patch describes explicit changes to specified paths. If a task needs to remove a property, assert an expected old value, or change one indexed array item, inspect whether a patch expresses the intent more precisely. For a merge, test the same key in both documents and read the resulting value before applying the operation to a large configuration.

When this tool is useful

• Combine sample configuration fragments while keeping the underlying structure visible.
• Investigate override behavior with a compact, reproducible sample.
• Assemble disjoint JSON fixtures before copying data into another application.

Tips for a better result

• Merging is not the same as appending every value. A shared key may be overwritten, and arrays may use a different policy from objects.
• Test one conflicting key and one array before relying on a merge for real configuration.
• Use a small JSON example to isolate an unexpected result. Add nested objects, arrays, quoted text, and empty values only as needed to reproduce the behavior.

Frequently asked questions