How to convert helm chart values.yaml to json
- Step 1Copy values.yaml from the chart — Get the default values with helm show values <chart> > values.yaml, or open the values.yaml file from a cloned chart repository. Paste the contents into the converter.
- Step 2Convert to JSON — The output is a JSON object matching the values structure. Nested keys like image.repository, service.port, and ingress.hosts become nested JSON objects.
- Step 3Validate against values.schema.json — Many Helm charts include a values.schema.json. Paste the converted JSON into a JSON Schema validator to catch missing required values before running helm install.
- Step 4Use in Terraform or a CI script — Pass the JSON string to Terraform's helm_release values argument, or use it as the base for a values comparison script that diffs default values against environment-specific overrides.
Frequently asked questions
How do I convert my environment-specific override values and compare them to defaults?+
Convert both values.yaml (defaults) and your override YAML separately, then use the JSON Diff tool to see exactly which values your override changes. This is useful for reviewing what a values file for production changes relative to the chart defaults.
Will Helm conditional blocks and template functions parse correctly?+
This tool converts values.yaml — the data file — not the Helm templates themselves. Template files with {{- if .Values.enabled }} blocks are not values files and should not be pasted here. values.yaml contains only static YAML configuration with no Go template syntax.
Is chart configuration data transmitted to JAD Apps?+
No. YAML parsing runs entirely in your browser using js-yaml. Image registry credentials, TLS secret references, and cluster-specific configuration in the values file are never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.