🔗
Developer/JSON Merger

JSON Merger

Combine multiple JSON files — array concat or recursive deep merge. 100% in-browser.

100% LOCALConcat & deep mergeNested arrays addMulti-file queue100% local
🔗
Add JSON files
Merge order = list order below

Add two or more JSON files, pick a strategy, and merge them

Data Source & Legal Disclaimer
Effective: 2026Last updated: TodayUpdate: Manual review
Sources: JSON merging — client-side only

JSON merging runs entirely in your browser. Your data is never uploaded to any server.

See all data sources & update policy →

Concat vs deep merge — illustrated

Concat (arrays only) is order-preserving glue: [a] + [b] = [a, b], duplicates included. Deep merge (objects only) recurses: object keys merge pairwise, arrays inside objects concatenate, and later files overwrite earlier scalars — so config overlays work the way you expect. The rule of thumb: lists of records → concat; settings/layers → deep merge.

Concat glues arrays · deep merge recurses objects
CONCAT (arrays)[a, b][b, c][a, b, b, c]DEEP MERGE (objects){tags:[x], level:1} + {tags:[y], level:2}{tags:[x,y], level:2}duplicates keptlater wins onscalars.

Later files win on scalar conflicts; arrays always concatenate, even inside objects.

Combining locale files — Iris' i18n build

Iris splits translations per team: en-core.json (array of 214 phrase entries), en-marketing.json (87 entries), and a settings overlay shared-config.json.

  1. Queue all three:She drops the files in order — core first so marketing entries land after, and the overlay last so it wins conflicts
  2. Concat the arrays:The two phrase arrays glue into one 301-entry array (214 + 87 = 301 ✓ shown in the summary)
  3. Deep merge the overlay:A second run deep-merges the merged settings object: nested arrays concatenate and the overlay's later scalars overwrite defaults
  4. Ship:merged.json downloads and the build picks it up unchanged — no scripting required
↩ Back to merger

About this tool

What is this tool?

Merge multiple JSON files online free: concat for arrays, deep merge for objects with stated override rules.

Concat & deep mergeNested arrays addMulti-file queue100% local

Two Honest Merge Strategies

Most merge tools pick one behavior and hide the edge cases. This tool gives you two named strategies with stated rules: concat appends arrays for dataset combining, and deep merge recursively combines objects where nested arrays add together and later scalars override earlier ones. You choose the semantics instead of discovering them from a wrong result.

Order Matters in Deep Merge

Deep merge resolves scalar conflicts in favor of the later file in the queue, so put your authoritative source last. Arrays at any depth concatenate rather than replace - merging two configs that both define a tags array gives you both tag sets. The live preview shows the exact merged tree before you download.

Frequently Asked Questions

When should I use concat vs deep merge?

Concat is for arrays: it appends every input items into one array, which is the right move for combining datasets like exports or log batches. Deep merge is for objects: it recursively combines keys, nested arrays add together, and when both inputs define the same key with a scalar, the later file wins - a rule that is stated up front, not hidden.

What happens to conflicting keys in deep merge?

Nested objects merge recursively at every depth. If both files set the same scalar key, the value from the later file in the queue overwrites the earlier one, so ordering the queue matters. If both values are arrays, they are concatenated rather than replaced.

Can I merge files with different root types?

Concat requires every input to be an array and says so if one is not. Deep merge requires every input to be an object. Mixed-type queues are rejected with a clear message instead of producing a silently wrong result.

Related tools

Joke of the Day
Sep 7

Why did the elephant paint its toenails red?

100% Free, Forever

Keep Tools Free for Everyone

No paywalls, no signups, no data sold. Built by a solo developer who believes useful tools should be accessible to everyone.

Support me on Ko-fi— keep tools free

100% of proceeds go towards hosting & building more free tools.