JSON, YAML, XML, CSV, and TOML each have a page whose name is the direction you came for. CSV to JSON and JSON to CSV used to be three overlapping tools. They are two pages now, and the old addresses redirect. The same split applies to YAML and XML. TOML stays one page, JSON to TOML, and the swap control on it still flips toward JSON.

The stronger converter was kept: file open, and the options that page already had. A swap button is still there if you arrived with the other format. The canonical link is the direction in the address, so search engines are not offered two URLs for one default.

Directional converters
Job	Tool	What it will not do
CSV into JSON	CSV to JSON	Delimiters and an optional header. Not a spreadsheet workbook.
JSON into CSV	JSON to CSV	An array of objects. Nested objects should be flattened first.
YAML into JSON	YAML to JSON	Comments do not survive. Tabs in the indent are a YAML error.
JSON into YAML	JSON to YAML	No comments are added. Quote values that look like yes or no if a strict parser matters.
XML into JSON	XML to JSON	Attributes can be kept. A round trip is not byte-identical.
JSON into XML	JSON to XML	Elements from objects. Attributes are not invented.
JSON and TOML	JSON to TOML	One page, still swappable. TOML comments are dropped on the way through JSON.

Converter questions

Why do two directions have two addresses?

So the page you open already faces the way you searched. The swap control remains for the return trip. Old bookmarks redirect rather than competing.

Did the file-upload converter get dropped?

No. CSV, YAML, and XML still open a local file. The weaker paste-only duplicates were the ones removed.

Does conversion upload the document?

No. Parsing runs in the tab. Config files and exports stay on the device.