The merger parses each YAML input, combines the resulting mappings, and formats the merged output. Inputs are merged in order, which makes it useful for base config plus environment overrides such as Helm values or deployment manifests.
For keys that appear in more than one document, you can choose whether the later input or the earlier input wins. Arrays can be concatenated or replaced, and nested mappings are merged recursively under the selected strategy.
Because YAML often controls deployment behavior, merge results should be reviewed before being copied into a live config. The browser-only workflow helps you test strategy choices without uploading internal configuration.
Common questions and answers about this topic.
Merges two or more YAML documents into one, combining mappings from all sources with configurable conflict and array strategies.
Yes — up to 5 inputs can be merged in a single pass. They are combined left-to-right, so the rightmost input has the final say on conflicting keys (unless you switch to A → B).
By default the value from the later document takes precedence (B → A), and arrays are concatenated. You can switch to A → B to keep the first document's value, or set the array strategy to Replace so the later array wins outright.
Yes — nested mappings are merged recursively under both conflict strategies, and arrays follow the chosen array strategy (Concat or Replace) at every depth.
Common use cases include merging Kubernetes manifests, combining Helm chart values across environments (base + dev/staging/prod overrides), and consolidating multi-file CI/CD config (GitHub Actions, GitLab CI) into a single review-friendly document.
No, YAML merging is performed entirely in your browser. Both files are merged locally with JavaScript — nothing is uploaded.