Bidirectional JSON, YAML, and TOML Configuration Conversion
Cloud-native infrastructure, CI/CD pipelines, and package manifests frequently mix JSON, YAML (Kubernetes manifests, GitHub Actions workflows, Docker Compose, OpenAPI specs), and TOML (Rust Cargo.toml, Python pyproject.toml, Hugo configs). This tool parses and serializes all three formats locally in your browser with configurable 2-space or 4-space indentation, comment stripping, and multiline string preservation.
Automatic Format Detection
Leave the input selector on Auto-Detect to automatically identify RFC 8259 JSON, YAML 1.2 block mappings and sequences, or TOML v1.0 tables ([section]) and arrays of tables ([[items]]).
Kubernetes & CI/CD Ready
Convert verbose JSON output from kubectl get -o json or AWS CLI responses into clean, human-readable YAML manifests with preserved boolean, number, and null types.
TOML Table & Dotted Key Support
Accurately parses TOML inline tables, dotted keys, ISO timestamps, and multiline strings into nested JSON objects or YAML hierarchies without server round-trips.
Frequently Asked Questions
What happens to YAML or TOML comments when converting to JSON?
Because standard RFC 8259 JSON does not support comments, inline # comments in YAML and TOML are stripped during AST parsing while preserving all key-value data structures, arrays, and primitive types.
Why did TOML serialization reject a top-level array or null value?
Unlike JSON and YAML, the TOML specification requires the root document to be a key-value table and does not have a native null literal. When converting to TOML, top-level arrays are wrapped in a root key and null properties are omitted or serialized safely.