Check an import
Start with delimiter, quoting, encoding and header checks. A newline inside a quoted field is part of a record, and identifiers such as 00123 should remain text.
THE DATA & TABLES COLLECTION
Inspect CSV files, preserve your values and transform JSON. Prepare smaller exports for the next application without opening a spreadsheet.
12 tools
Try a broader task such as “text”, “CSV” or “image”. Try a specific task such as regex, timestamp or JSON.
Suggest a taskUse JSON Formatter for indentation, syntax errors or compact output. Choose JSON Viewer when you need to open nested branches and search for a value. Choose JSON Compare when two API responses need a structural comparison that ignores object key order.
For table workflows, CSV to JSON keeps fields as strings unless you enable type conversion. JSON to CSV exports object records with explicit nested-value handling. Check quoted fields and headers in the CSV Viewer before deduplicating, selecting columns, merging or splitting records. All operations process input locally in the browser; file selection is not an upload to a conversion service.
Use JSON / YAML Converter when configuration needs a different representation. Choose the direction explicitly. Strings and large integers keep their meaning; unsupported references and values that would lose precision are rejected. Keep the original YAML if comments matter, because JSON has no comment syntax.
Delimited files fail imports for predictable structural reasons. Confirm four things before converting: the delimiter (comma, semicolon, tab or pipe), quoting rules (embedded separators and doubled quotes), encoding (UTF-8 default; UTF-16 and Windows-1252 when the source system uses them) and whether the first record is a header. A newline inside a quoted field belongs to that record—not a new row.
Keep identifiers as text: opening a file in a spreadsheet and saving it can turn 00123 into 123 before another converter sees it. Use CSV Viewer to confirm structure, Delimiter Converter to change separators safely, Column Editor to align schemas, then convert with CSV to JSON or combine with CSV Merge / CSV Split. Deduplicate with an explicit key rule via CSV Deduplicate—never by guessing that similar names are the same record.
All table operations parse and export locally in the browser; file selection is not an upload to a conversion service.
START WITH YOUR PROBLEM
Start with delimiter, quoting, encoding and header checks. A newline inside a quoted field is part of a record, and identifiers such as 00123 should remain text.
Choose CSV-to-JSON when rows need named fields. Choose JSON-to-CSV when records need a flat table; inspect nested objects, arrays and missing values before exporting.
Merge only matching schemas, or split complete parsed records into numbered batches. Use the column editor before merging files whose fields have different names or order.
Diagnose delimiters, headers, quoting, encodings and leading-zero identifiers before changing a CSV.
Read the guide Data & Tables · Practical guideChoose whole-row or key-column matching and understand which record survives.
Read the guide Data & Tables · Practical guideUnderstand object flattening, arrays, missing fields and numeric precision before exporting JSON as a table.
Read the guide Data & Tables · Practical guideDistinguish syntax validity, pretty-printing, duplicate keys and application-level validation.
Read the guide