Format YAML so the next diff is about content, not spaces
Inconsistent indent is how reviews go sideways. Paste YAML, get a normalized dump (and a parse error if it’s broken).
chars: 25
When to use
Before committing a messy merge, teaching indent rules, or cleaning a hand-edited values.yaml.
Examples
How it works
Parse → emit with fixed indentation (default 2 spaces). It is not a semantic linter for Helm charts.
Common pitfalls
- Invalid YAML fails — fix structure first.
- Comments may move or drop depending on the library path.
- Mixed tabs/spaces are a common parse failure.
How this differs
Formatter keeps YAML. YAML→JSON if you need JSON consumers. JSON→YAML if your source is JSON.
FAQ
Will formatting change meaning?
Shouldn’t for valid plain data; review diffs anyway.
Comments preserved?
Often lost on parse/dump — call that out honestly if true.
Same as a linter?
This reformats; it doesn’t enforce org style guides.
Related JSON tools?
Convert with JSON ↔ YAML pages.
Related tools
Runs in your browser. Nothing is uploaded. Not a security product —hashes and JWT decode are for debugging, not password storage or auth advice.