Skip to content
Input
TOML
Limit
1 MiB
Runtime
Browser

Merge TOML root tables with an explicit policy

Combine two parsed root tables recursively and make scalar, array, or incompatible-type collisions follow a visible policy.

Local processingNo sign-upNo content logging

Merge TOML

Inputs are limited to 1 MiB and stay in this browser tab.

Paste or edit the source. Tool Swim does not upload or save it.

The second document stays under the same local limits.

Merged TOML

Nothing is placed in a URL, account, or remote log.

What this tool does

Strict, bounded, local processing

TOML defines no standard document merge. This tool never evaluates templates, environment variables, or application inheritance.

Collision policy defines the result

Nested tables merge recursively. Scalars, arrays, and incompatible types are complete-value collisions handled by the selected policy.

Serialization changes presentation

Generated TOML may not retain comments or dotted-key and inline-table choices. Compare and validate the result before deployment.

Primary references

Questions and answers

Related TOML tools

TOML ComparatorParse both documents and emit deterministic path-based differences while keeping array order significant and table order non-semantic.TOML Schema ValidatorParse TOML, project supported values into a documented schema model, and return structured violations from a supplied JSON Schema.TOML Path QueryNavigate table keys and array indexes with a small deterministic path grammar, then serialize the selected typed value.