Convert YAML to JSON
Converts YAML to JSON for tools and APIs that only accept JSON.
Convert YAML to JSON →- Runs on
- the built-in JSON converter, running in this tab
- Steps
- Direct, a single conversion
- Input
.yaml· application/yaml- Output
.json· application/json- Uploads
- None. The file never leaves your device.
What to expect
Comments are lost, because JSON has no way to represent them. YAML dates and other rich scalars become strings.
Why convert YAML without uploading
Most online converters take your file, send it to their servers, convert it there and hand back a download link. That means your document sits on someone else's disk, subject to their retention policy and their breaches. It also means you cannot use them offline, and cannot use them at all for anything confidential.
frogConvert does the conversion in the page itself, with the built-in JSON converter. There is no upload step because there is no server. You can disconnect from the network and it still works.
About the formats
YAML
A whitespace-significant superset of JSON built to be written by hand, which is why configuration files use it. Indentation errors are the price of the readability. More about YAML files.
JSON
The default interchange format for structured data on the web: objects, arrays, strings, numbers, booleans and null. No comments, no date type, no schema. More about JSON files.
Common questions
- Is my file uploaded when converting YAML to JSON?
- No. The conversion runs entirely in your browser. The file never leaves your device, there is no server to upload to, and the page works offline once loaded.
- Is YAML to JSON conversion free?
- Yes, with no account, no watermark and no file limit per day. frogConvert is open source and there is no server cost to recover, because your device does the work.
- How large a file can I convert?
- Up to 2 GB for a single file, 500 MB total per batch, and 300 files at once. The practical limit is your device's memory, since everything is processed locally.
- What is lost converting YAML to JSON?
- Comments are lost, because JSON has no way to represent them. YAML dates and other rich scalars become strings.