JSON converter for Next.js & Supabase data. In your browser.

Free, no sign-up. Inputs and outputs stay in your browser, with no processing endpoint or upload. Copy and download are local. Usage events contain only a fixed tool name and action, never your data.

No. CSV has no native JSON types. Objects or nonempty arrays of objects export as rows; nested values become JSON text in a cell. Import keeps every cell as a string. Absent properties export as empty cells. Check types and nulls before a database import.

The existing Papa Parse library handles quoted delimiters, doubled quotes and embedded newlines. CSV import requires unique, nonempty headers and equal row widths, and rejects parsing errors. Untrusted cells can be spreadsheet formulas, so inspect the CSV as text before opening it in a spreadsheet.

YAML core scalars, lists and mappings that can represent JSON. Aliases, duplicate keys, custom tags, nonfinite numbers and integers outside JavaScript safe precision are rejected. Comments and YAML formatting do not survive conversion. Dates remain strings under the core schema.

Choose Plain XML for items/item elements and keys such as name as element names. Plain output loses JSON type, null and empty-collection distinctions and requires simple XML names. Choose Typed XML for a json root with entry/item elements and key attributes; it preserves arbitrary keys, arrays, booleans, null and strings for exact round-trips. Other XML imports as a root tree with attributes and ordered children, preserving mixed text and repeated elements rather than guessing types.

No. DTD and custom entity declarations are rejected before native DOM parsing. XML 1.0-invalid control characters cannot be exported. Conventional XML comments and processing instructions are not data in the imported tree; Plain or typed XML output is generated from JSON data, not a recreation of an arbitrary original XML document.