CSV to JSON
Quoted fields and embedded commas handled.
Never uploadedConvert YAML to JSON and back, with real parse errors rather than guesses.
YAML to JSON, or JSON back to YAML.
Parsing happens in your browser.
Errors report the line, so you can find the real problem.
Because a colon followed by a space starts a key. A value containing one - a URL, a time - has to be quoted, and that is the single most common YAML error.
JSON has no comment syntax, so they are dropped in the YAML-to-JSON direction. There is no way to preserve them.
YAML's older spec treats yes, no, on and off as booleans. Quote them if you meant the strings. This catches out anyone writing country codes, where NO means Norway.
Completely - and tabs are forbidden, only spaces. Mixed indentation is the second most common reason a YAML file won't parse.
Convert YAML to JSON and back in your browser, with genuine parse errors rather than a vague failure. A few YAML behaviours account for most problems: a colon followed by a space starts a key, so URLs and times must be quoted; indentation is significant and tabs are forbidden entirely; and the older spec treats yes, no, on and off as booleans, which surprises anyone writing NO for Norway. Comments cannot survive the trip to JSON, because JSON has no syntax for them.
The last couple are from other categories - there are 81 tools here in total.
Quoted fields and embedded commas handled.
Never uploadedShrink PDFs to fit email, chat, or upload limits.
Shrink JPG, PNG or WebP without visible quality loss.
Never uploadedStrong random passwords, generated in your browser.
Never uploadedFormat, validate and minify JSON instantly.
Never uploadedMonthly payment with tax and insurance included.
Never uploaded