Most converters expect perfectly formed input. In practice, data rarely arrives that way — it's copied from Slack, pasted from an API response, exported from a legacy system, or typed by hand. Here's what happens to it before anything gets converted.
🔧Malformed JSON is repaired automatically
Single quotes instead of double quotes, missing quotes around keys, trailing commas, and smart quotes copied from Word or Google Docs are all fixed before parsing — paste data as-is instead of cleaning it up first.
📦Spreadsheet-style data just works
Pasted data that looks like rows and columns — an array of arrays — is converted into proper records automatically, using the first row as column headers.
🔍API responses are unwrapped for you
Paste a full API response and the converter finds the actual list of records inside it, even nested inside a "data" or "results" wrapper. If more than one list is found, you're shown each option with a record count so you can pick the right one.
🧩XML without a clean root element still converts
XML pasted without a single wrapping root — or with several different repeating elements, like both Orders and Customers — is repaired automatically or presented as a choice, instead of failing outright.
🌳Nested data is preserved where it can be
Converting between JSON and XML keeps nested objects and arrays intact — nested fields stay nested, repeated fields become repeated elements. Converting to Excel or CSV, which can't represent nesting, flattens nested fields into columns like "address.city" automatically.