ToolAtlas
FavoritesRecent

JSON ↔ YAML

Processed in this browser

Text limit: 2000000 characters

This tool never uploads your input.

A config that is YAML in Git and JSON in an API. Tables belong on JSON↔CSV. Validate JSON first if the paste is dirty.

GitOps YAML in the repo, JSON in the HTTP body. This page changes the skin. It will not kubectl apply.

Pretty-print: JSON formatter. Tables: JSON ↔ CSV. Kubernetes secrets should not live in either paste box longer than you need.

NO becoming false

YAML 1.1-style implicit booleans still bite country codes and the word NO. Quote them. This is skin conversion, not kubectl apply or Helm. Tabs break YAML; CSV/Excel is the other converter.

How to use it

  1. Paste JSON or YAML.
  2. Convert. Read the warning if types shifted (off, NO, version 1.0).
  3. Copy back to the file. Diff in git.

Honest limits

Not Helm. Not a schema validator beyond “did it parse.” Not a 50 MB CRD dump.

FAQ

Why did `NO` become false?

YAML 1.1-ish implicit booleans. Quote the string if you meant the country code or the word.

Anchors and merge keys?

Support is only as rich as the parser in this tab. Complex Helm charts may fail.

Is this CSV?

No. Arrays of objects for Excel are JSON↔CSV.

Tabs in YAML?

YAML hates tabs. If conversion fails, look at indentation.

Is the config uploaded?

No. Still do not paste production secrets into random sites — this one stays local.

Related tools