How do I merge Helm values files online?

Paste the chart values.yaml on the left and the override on the right. Nested maps merge. Lists replace. null in the override deletes that key.

Is this a helm values.yaml validator?

It checks that each file is a YAML mapping and reports parse errors with a line and column. It does not lint keys against a chart schema.

Why did my list replace instead of append?

Helm treats lists as a whole value. To change one item, paste the full list in the override.

Are the values uploaded?

No. Both files are merged in your browser. They are not sent to a cluster or an application server.

Merge Helm values files online

Merge Helm values files online by pasting chart defaults and an override. Nested maps combine; lists are replaced.

This merge runs in the browser. It does not load a chart, talk to a cluster, or evaluate templates. Invalid YAML is not repaired.

Ctrl+Enter or ⌘+Enter runs this tool immediately.

YAML indent

2 spaces4 spaces

Base values

Override values

Merged values

Paste both documents to merge them.

Waiting for input.

Parsing stays in this browser. Input is not uploaded or saved.

How to use this tool

Paste the chart's values.yaml on the left and the environment override on the right, or load the sample.
Read the merged YAML. Notices list each path the override added, removed, or changed.
A null value in the override deletes that key. A list in the override replaces the whole list.

What this conversion loses

Comments and aliases from both files.
List items are not merged by name. An override list replaces the base list.
Templates, --set flags, and subchart values from Chart.yaml are not applied.

Supported formats and limitations

Each side is one YAML mapping. A list at the root is an error. A --- stream is rejected.
Maps merge recursively. Scalars and lists in the override replace the value at that path.
null in the override removes the key. Older Helm coalesce left the base value when the override was null.
This does not lint keys against a chart schema. Unknown keys are kept.

Examples

Override a nested tag

image.repository stays from the base. image.tag becomes 1.26.

image:
  tag: "1.26"

Delete with null

drop: null removes drop from the merge.

drop: null

Common errors and solutions

Helm values must be a mapping: The root of values.yaml is an object. A list of documents or a single scalar is rejected.
Tabs used for indentation: Replace the tab with spaces. The merger does not rewrite the file.

FAQ

How do I merge Helm values files online?: Paste the chart values.yaml on the left and the override on the right. Nested maps merge. Lists replace. null in the override deletes that key.
Is this a helm values.yaml validator?: It checks that each file is a YAML mapping and reports parse errors with a line and column. It does not lint keys against a chart schema.
Why did my list replace instead of append?: Helm treats lists as a whole value. To change one item, paste the full list in the override.
Are the values uploaded?: No. Both files are merged in your browser. They are not sent to a cluster or an application server.

Privacy check

Open DevTools → Network, paste a document, and confirm no request carries the editor text. The page load and the Google tag still appear. Analytics events carry the tool name, never what you pasted.

Related tools

Docker Compose to Kubernetes YAML
Convert Docker Compose to Kubernetes YAML in the browser. Services become Deployments and Services; the Compose file is not uploaded.
JSON and YAML diff
Compare two JSON or YAML documents by value in the browser. Key order, formatting, and comments are ignored, and Kubernetes lists are matched by name.
YAML validator
Check YAML syntax without converting or rewriting it. Errors include a line and column when the parser provides them, and valid input is left unchanged.