Will comments in JSON survive?
Standard JSON has no comments. Repair comments first if you pasted JS-style input, then convert.
Paste JSON on the left and copy YAML on the right. Built for Kubernetes snippets, CI config, and docs that prefer YAML.
JSON formatter
Run a tool to see a polished result here
Objects, arrays, strings, numbers, booleans, and null map to YAML. Invalid JSON is rejected before conversion. YAML-to-JSON is available from the same editor sidebar. Everything stays local.
The editor is prefilled with a small example for JSON to YAML. JSON to YAML keeps objects, arrays, strings, numbers, booleans and null. Invalid JSON is rejected; switch the sidebar for YAML to JSON. Replace it with your own file; the sample and your payload stay in this tab.
{
"apiVersion": "v1",
"kind": "ConfigMap",
"metadata": { "name": "jfmt" },
"data": { "enabled": "true" }
}This dedicated JSON to YAML URL matches that search intent; the homepage stays the general formatter. JSON to YAML keeps objects, arrays, strings, numbers, booleans and null. Invalid JSON is rejected; switch the sidebar for YAML to JSON. Related tools on this site include beautify, validate, minify, JSON to CSV, JSON to YAML and JSON to XML — all local. JFmt runs in a Web Worker in this tab. Do not paste production secrets if you share your screen. Read errors in the output pane instead of sending production payloads to another service.
Standard JSON has no comments. Repair comments first if you pasted JS-style input, then convert.
This URL starts in JSON→YAML. Switch the sidebar to convert the other way without leaving the editor.
No.
No. Parsing and conversion run in a Web Worker in this tab. jfmt.dev does not receive the payload.
So people searching for this operation land on a page that already selects it. JSON to YAML keeps objects, arrays, strings, numbers, booleans and null. Invalid JSON is rejected; switch the sidebar for YAML to JSON.