YAML to JSON Converter

This converter reads simple, flat YAML and emits the equivalent JSON object. It is built for the everyday cases where YAML is used as a plain key-value list: a short config block, a set of environment-style settings, a feature-flag list, or a snippet someone pasted into a ticket or chat. If you have a handful of `key: value` lines and you need them as JSON to drop into a script, an API request body, or a test fixture, this is the quick path.

Typical users are developers reviewing a config during a handoff, ops staff turning a settings stanza into JSON for a tool that only accepts JSON, and students or analysts who received a small YAML file and want it in a format their code or spreadsheet pipeline already understands. Because each line becomes one JSON property, the output is easy to scan and diff against the original.

It runs entirely in your browser. The YAML you paste or drop is parsed locally, nothing is uploaded to a server, and nothing persists once you close the tab. That makes it reasonable for config fragments that contain internal hostnames, ports, or environment names you would rather not send anywhere.

The flow is paste or drop your YAML, let it process in place, then copy the JSON or download it as a `.json` file. The parser works line by line: it looks for a `key: value` shape on each line, trims whitespace, and writes one property per match into a single JSON object. Lines that do not contain a colon are skipped rather than flagged.

Value types are inferred. `true` and `false` become JSON booleans, `null` becomes null, anything that parses cleanly as a number becomes a number, and everything else is treated as a string with surrounding single or double quotes removed. The output is pretty-printed with two-space indentation so it is readable straight away.

What it does not do is the important part: there is no support for nested mappings, lists, multi-line block scalars, anchors and aliases, or multiple documents separated by `---`. Indentation that implies hierarchy in real YAML is not interpreted, so a nested structure will not be rebuilt into nested JSON. Treat this as a converter for flat key-value YAML, not a full YAML 1.2 engine.

The most common surprise is nesting. If your YAML has indented child keys under a parent, every key is flattened into one object and the indentation is lost — child keys land at the top level and can silently overwrite each other if names repeat. Lists written as `- item` lines are not captured as arrays at all, since those lines have no colon and are skipped.

Type inference is literal and can misread intent. A version like `1.20` becomes the number `1.2`, a ZIP code or ID such as `01234` loses its leading zero, and a string that happens to read as a number is no longer quoted. Inline comments after a value are kept as part of the string, and a stray colon inside an unquoted value can split the line in an unexpected place. Quote values you want preserved exactly.

Because non-matching lines are dropped quietly, a malformed or genuinely complex YAML file can produce JSON that looks complete but is missing entries. Very large pastes are also held in memory in the browser, so extremely big files may feel slow. If your input is anything beyond flat key-value pairs, this tool is the wrong fit and you should reach for a full YAML library.

Compare the property count in the output against the lines in your source. If keys are missing, those lines either lacked a colon or were nested, and you will need to handle them by hand. Confirm that nested or list structures you expected actually appear; if they collapsed or vanished, the input exceeded what this converter supports.

Spot-check the value types. Make sure numbers that should stay as text — versions, IDs, postal codes, phone numbers — are quoted, that leading zeros survived, and that booleans and null came through as intended rather than as strings. Open the result in a JSON validator or your editor to confirm it parses.

For anything official, financial, or contractual, verify the JSON manually against the original YAML field by field before relying on it. This is a convenience converter for simple data, not an authoritative transformation, and a quiet dropped line or a coerced number should never be the basis for a record that matters.