Base64 to YAML Converter

About the Base64 to YAML Converter

Kubernetes secrets, CI variables and Helm values all store YAML as Base64, which means the config you actually need to read is one decode away from being visible. This tool does that decode and then goes a step further by running the result through a real YAML parser.

That parse step is the valuable part. YAML is famously sensitive to indentation, and a config that was edited as a Base64 string, or that lost a space somewhere in transit, will look plausible while failing to load. The status line reports how many documents the payload contains and describes the top level shape, either a key count or a list length, so you can tell at a glance whether the structure survived. A parse failure is reported with the line number the parser stopped on.

Reindenting is optional and off by default, because the raw form is what you usually want to compare against the original. Turn it on and the payload is rebuilt from the parsed data with your chosen indent width, which normalises mixed tabs, inconsistent nesting and inline flow collections into one consistent style. Sorting the keys on top of that makes two versions of the same config diffable.

Reformatting resolves anchors and aliases into their expanded values, so leave it off if you need those preserved. Multi document payloads separated by three hyphens are handled throughout. Encode again with YAML to Base64, or convert with YAML to JSON.

How to use

1. Paste the Base64 value from your secret, variable or config field.
2. Read the document count and structure summary in the status line.
3. Tick Reindent through the parser to normalise the formatting.
4. Copy the YAML or download it as a file.