Convert JSON to Helm Values YAML — Free Online Converter

Helm charts consume values in YAML (values.yaml) but Helm itself will also accept JSON via the -f flag. If you have JSON from an API, a CI pipeline, or a config management tool, converting to YAML gets you an override file that's readable, diffable, and easy to commit. This guide covers the common Helm JSON-to-YAML scenarios.

Override JSON Becomes values.yaml

Typical workflow:

1. You have JSON from a config service, secrets manager, or CI output.
2. Paste into the converter.
3. Save the YAML as values.yaml (or values-prod.yaml, values-staging.yaml).
4. Run helm install my-release my-chart -f values.yaml.

Example input:

{"replicaCount":3,"image":{"repository":"nginx","tag":"1.25"},"service":{"type":"ClusterIP","port":80},"resources":{"limits":{"cpu":"500m","memory":"512Mi"}}}

Output:

replicaCount: 3
image:
  repository: nginx
  tag: "1.25"
service:
  type: ClusterIP
  port: 80
resources:
  limits:
    cpu: 500m
    memory: 512Mi

Ready to commit.

Per-Environment Values Files

Most Helm workflows split values across environments: a base values.yaml, plus values-prod.yaml, values-staging.yaml, values-dev.yaml. If your team generates environment configs from a central source as JSON, converting to YAML gives you four clean files instead of four JSON blobs.

Helm merges multiple -f flags in order, so you can layer overrides:

helm install my-release my-chart \
  -f values.yaml \
  -f values-prod.yaml \
  -f secrets-prod.yaml

Each file can come from a different source. YAML wins over JSON for the human-edited ones.

Sell Custom Apparel — We Handle Printing & Free Shipping

Helm's --values Accepts JSON Too

If you want to skip conversion, Helm's -f flag accepts JSON files directly. Both work:

helm install my-release my-chart -f values.json
helm install my-release my-chart -f values.yaml

So why convert? Readability and Git. CI-generated JSON is fine for ephemeral use; anything you're committing or reviewing should be YAML.

Secrets — Convert and Use Local-Only

Helm values files often contain API keys, database passwords, or service account credentials. Never paste those into a converter that uploads your input. Our converter runs entirely in the browser — nothing is uploaded. Verify with DevTools → Network tab: click Convert, confirm no outgoing request.

For full context on client-side safety, see our JSON to YAML privacy guide.

When to Use helm template Instead

If you want to go the other direction — render a full Kubernetes manifest from chart + values — use helm template:

helm template my-release my-chart -f values.yaml > rendered.yaml

That's a different workflow: chart templates + values → final K8s YAML. Our browser converter covers the JSON-to-YAML format flip for the values file itself. Different tool for each step.

Frequently Asked Questions

Does Helm require values files in YAML format?

No — Helm accepts both JSON and YAML with the -f flag. YAML is the convention for anything checked into Git because it's easier to read and diff.

Can I convert a chart's Chart.yaml to JSON?

You can convert JSON to YAML here. For the reverse, use our YAML to JSON converter. Both are lossless.

How do I merge multiple JSON values files into one YAML?

Convert each JSON to YAML separately, then merge with Helm's multiple -f flags at install time. Or merge the JSON first with jq, then convert the result. Helm's native multi-file merge is usually cleaner.

Will conversion preserve nested objects and arrays?

Yes — nested structures are preserved identically. Helm reads the same data whether it's indented YAML or brace-nested JSON.