tenuko*

JSON to YAML

Convert JSON into clean, readable YAML for Kubernetes, CI configs and OpenAPI specs - instantly and privately in your browser.

From JSON to readable YAML

JSON is perfect for machines but heavy on punctuation for humans - every brace, bracket, quote and comma has to line up. YAML strips most of that away and leans on indentation instead, which is why it dominates infrastructure config. Paste JSON above and it is converted to YAML as you type, ready to drop into a manifest or pipeline.

Options that matter

  • Indent - 2 spaces (the standard) or 4 for deeply nested files.
  • Style - block style gives classic indented YAML; flow style keeps short collections inline, JSON-like, on one line.
  • Quote strings - leave YAML to quote only where needed, or force single or double quotes around every string for consistency.

A quick example: the object name maps to name: web, the array ports becomes a sequence with each port on its own - line, and numbers like 3 stay bare so they read as numbers, not strings.

Valid JSON in, valid YAML out

The converter parses your input with the browser JSON engine first, so if there is a stray trailing comma or a single quote where a double belongs, you get the exact line and column of the problem rather than surprising YAML. Fix the flagged spot and the output appears instantly.

Going the other way? Use the YAML to JSON converter. To clean up the source first, try the JSON formatter, or convert a legacy feed with the XML to JSON converter.

Frequently asked questions

Why convert JSON to YAML?
YAML is easier to read and write by hand, so it is the format of choice for Kubernetes manifests, CI pipelines, Docker Compose files and OpenAPI specs. Converting from JSON lets you take an API response or generated config and turn it into something a human can maintain.
Is the conversion lossless?
Yes for data. Objects become mappings, arrays become sequences, and strings, numbers, booleans and null all map to their YAML equivalents. Only formatting differs - JSON comments do not exist to carry over, and key order is preserved.
What is block style versus flow style?
Block style is the familiar indented YAML with one item per line. Flow style uses JSON-like inline brackets and braces, so a short list becomes [a, b, c] on a single line. Block is the default because it is what most YAML files use.
How is indentation chosen?
You can pick 2 or 4 spaces. Two spaces is the near-universal default for YAML and what Kubernetes and most tools expect; four spaces can help very deeply nested files stay legible.
Is my JSON uploaded anywhere?
No. The conversion runs entirely in your browser with JavaScript. Nothing you paste is sent to a server, so it is safe to use with private configuration and secrets.

Related tools

JSON Formatter

Format, validate and minify JSON with syntax highlighting and clear error messages showing exactly where invalid JSON breaks.

Base64 Encode/Decode

Encode text or files to Base64 and decode Base64 back, with full Unicode support and URL-safe mode. Runs entirely in your browser.

URL Encode/Decode

Encode text for safe use in URLs or decode percent-encoded strings, with component and full-URL modes and a reference of common encodings.

HTML Encode/Decode

Convert special characters to HTML entities and decode entities back to text. Essential for displaying code and user input in web pages.