CSV / TSV to JSON

Turn tabular text into structured JSON without uploading the file to a conversion provider.

Drop files here or choose themProcessed locally in your browser when supported.

What this tool actually does

CSV → JSON creates a new file in the target format; it does not merely rename the extension. MakeFileWork processes the source in the browser where this conversion supports local execution and keeps the job bounded so a single file cannot consume unlimited memory or CPU.

How the result is verified

Before download, the engine re-serializes, reopens, parses or otherwise checks the output according to the format. The result shows concrete evidence such as pages, structure, extracted text or generated format instead of treating any downloadable blob as a successful conversion.

Limits and fidelity

Formats do not represent every feature in the same way. Layout, fonts, animation, formulas, metadata, transparency or interactive elements can change when the destination cannot preserve them. The tool does not promise fidelity that the target format cannot support and calls out known trade-offs.

When to use this workflow

Use this workflow when another application, device or upload portal requires the target format and you need a newly generated, verifiable file. If the rejection also specifies KB/MB, pixel dimensions or other measurable limits, use the upload-requirement workflow to validate those constraints together.

Privacy and final verification

Keep the original file until the output has been reviewed in the destination application or portal. Supported workflows process locally in the browser and enforce bounded size and complexity limits. For CSV → JSON, verify that the generated format preserves the properties that matter for your use case. For important data, compare a representative sample and confirm that format, content and quality meet the actual requirement before replacing the source file. Also open the generated file in the destination application when compatibility, colour, transparency, layout or compression matters.

Convert a CSV table to JSON records without guessing columns

Use this converter when an API, script or import process expects an array of JSON objects rather than spreadsheet rows. The first CSV record becomes the property names; each following record becomes one object. Values remain text, so a ZIP code such as 00123 keeps its leading zero instead of being treated as a number.

Commas, semicolons, tabs and quoted fields

The parser recognizes comma, semicolon, tab and pipe separators. Quotes protect embedded separators and line breaks: a quoted address containing a comma is one cell. When two different separators each produce a consistent table, the file is rejected rather than choosing an arbitrary layout. For example, id,name;role is ambiguous if subsequent records contain both separators in the same positions. Normalize the source to one clear delimiter before retrying.

Headers and data-loss safeguards

Empty or repeated column names receive unique replacements; existing names are not overwritten. Every data row must contain the same number of columns as the header. An invalid UTF-8 sequence, unfinished quote, or inconsistent row width stops the conversion. This avoids silently shifting a value into the wrong JSON property.

When to repair instead of convert

If some records have missing columns, start with Repair CSV and inspect any padded empty fields. To convert a valid CSV into tab-separated text, use CSV to TSV; for the reverse export use JSON to CSV. The local converter accepts at most 10 MiB of input, 50,000 rows, 200 columns and 100,000 characters per cell. Review the JSON structure before importing it into another system.