Free · Fast · Privacy-first

CSV to JSON with Delimiter Control

Not every file with a .csv extension is actually comma-separated.

Native JSON tool

CSV to JSON

Runs in your browser

CSV input

JSON output

Run the tool to see a task-specific result.

⚡

Auto-detect delimiter

🔒

Manual override

✨

Tab, semicolon, pipe support

⚡

Browser-only conversion

Cost: Free tier
Sign-up: Not required
Processing: Tool-specific
Privacy: Clearly disclosed

IframeResponsiveAttribution included

Add this CSV to JSON to your website

Drop the CSV to JSON into a blog post, product docs, intranet, or school portal with one iframe. Processing, privacy, and usage limits are the same as on the full tool page.

One copy-ready line of HTML
Responsive — adapts to any container width
No API credentials are placed in the snippet

Embed code

<iframe
  src="https://www.fixtools.io/json/csv-to-json?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="CSV to JSON by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/json/csv-to-json?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="CSV to JSON by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

Why explicit delimiter control matters for reliable conversion

CSV is a misleadingly broad term. The format started as comma-separated values, but in practice the same parser must handle tab-separated, semicolon-separated, and pipe-separated files because every spreadsheet program and database engine has its own export defaults. Excel in German, French, or Spanish locales exports with semicolons because comma is the decimal separator in those number systems. PostgreSQL COPY commands often produce tabs to avoid confusion with embedded commas in text fields. Legacy mainframe extracts use pipes for the same reason. A converter that hard-codes commas fails on all three cases. FixTools accepts every common delimiter and detects the right one automatically when possible.

Auto-detection works by sampling the first several lines of the input and counting how many times each candidate delimiter appears on each line. If every line has the same count of one delimiter, that is almost certainly the field separator. If two delimiters have consistent counts (which happens occasionally with data that contains commas inside tab-separated fields), the tool picks the most common one. The detection is fast and almost always right, but you can override the choice in one click if your file has unusual content that confuses the heuristic.

Quoting behaviour does not change with the delimiter. Whatever delimiter you select, a field surrounded by double quotes can contain that delimiter literally without breaking the row structure. A tab-separated file with a field "tab here" treats the embedded tab as data, not as a column break. A semicolon-separated file with a field "100;200" treats the embedded semicolon as data. This consistency means switching delimiters does not introduce new edge cases beyond what RFC 4180 already specifies for commas.

Mixed-delimiter files are not supported by any standards-compliant parser including FixTools. If you have a file where some lines use commas and others use tabs, the file is malformed and needs to be cleaned before conversion. The auto-detector will pick whichever delimiter appears most consistently and treat lines using the other delimiter as single-column rows. Open such files in a spreadsheet program, save as a properly-formatted single-delimiter CSV, then convert.

RFC 4180: Common Format and MIME Type for CSV Files PostgreSQL COPY documentation

How to use this tool

💡

The delimiter selector defaults to Auto. Switch to Comma, Tab, Semicolon, or Pipe to override detection.

How It Works

Step-by-step guide to csv to json with delimiter control:

1
Open the converter
Load the FixTools CSV to JSON converter in your browser. The delimiter selector appears above the input pane with Auto selected by default.
2
Paste or upload your file
Drop the file into the input pane or paste its contents. The auto-detector runs immediately and shows which delimiter it picked in a small badge next to the selector.
3
Override if needed
If the detected delimiter is wrong, click the selector and choose Comma, Tab, Semicolon, or Pipe explicitly. The parser re-runs with the new delimiter and the preview updates.
4
Convert and verify
Click Convert. Check that the JSON preview shows the expected column count and that values land in the right keys. A wrong delimiter usually shows up as a single long key per row.
5
Download or copy
Save the JSON file or copy the array to your clipboard for direct use in scripts, API requests, or database imports.

Real-world examples

Common situations where this approach makes a real difference:

European spreadsheet with semicolons

A German analyst exports a customer list from Excel where the locale uses comma as the decimal separator and semicolon as the field delimiter. FixTools auto-detects the semicolons and produces correct JSON without needing locale changes.

TSV from a database export

A backend engineer runs a Postgres COPY to stdout which defaults to tab-separated output. The file lands as .tsv but the workflow needs JSON. FixTools accepts tab as the delimiter and converts in seconds.

Pipe-delimited legacy extract

A data migration project receives a pipe-delimited file from a mainframe extract. The converter handles pipes natively, sidestepping the need to massage the file into commas first.

Mystery file from a partner

A partner sends a file with no documentation about its format. Auto-detection identifies the delimiter automatically and the preview confirms the parsing looks right before download.

When to use this guide

When your file uses a non-comma delimiter or auto-detection picks the wrong one.

Pro tips

Get better results with these expert suggestions:

Trust auto-detection first

Let the auto-detector pick the delimiter on the first pass. It is right the vast majority of the time and saves you a click. Only override when the preview shows wrong column count or merged fields.

Re-detect after editing

If you paste a file, edit it in the input pane, and the column structure changes, re-run auto-detection by switching the selector to Auto and back. The new content may have different delimiter characteristics than what was originally sampled.

Watch for quoted delimiters

A field like "100,200" in a comma-delimited file is one value, not two. The parser handles this correctly only if the quotes are present. If your file omits quotes around fields containing the delimiter, the file is malformed and needs cleanup before conversion.

Use tab for spreadsheet pastes

When you copy cells directly from Excel or Google Sheets and paste into the converter, the clipboard format is tab-separated even if the file would export as comma-separated. Switch the delimiter to Tab for paste workflows.

FAQ

Frequently asked questions

Comma, tab, semicolon, and pipe are the four built-in choices, plus Auto which detects the right one from your file. These cover essentially every CSV file you will encounter in practice. Auto-detection is the default and works correctly for the vast majority of inputs.

The tool samples the first several lines of the input and counts how many times each candidate delimiter appears on each line. The delimiter with the most consistent count across lines is selected as the field separator. The check takes milliseconds and updates as you paste new content.

The four built-in options cover almost all real-world files. If you have a file using a truly unusual delimiter such as a caret or tilde, find and replace it with one of the supported delimiters in a text editor before pasting. Custom delimiter support is on the roadmap.

No. RFC 4180 quoting rules apply regardless of which delimiter is selected. A field surrounded by double quotes can contain the delimiter literally without breaking row structure. Embedded double quotes are escaped by doubling them, again regardless of delimiter choice.

Mixed-delimiter files are malformed and no standards-compliant parser handles them correctly. Clean the file in a spreadsheet program to use a single delimiter throughout before converting. The auto-detector will pick the dominant delimiter but the other lines will not parse correctly.

Tab-separated values files work exactly like comma-separated. Either rename to .csv or just paste the contents directly; the auto-detector will pick tab and the parser handles the rest. Output JSON is identical regardless of the input delimiter.

Yes. When you copy cells from Excel, Google Sheets, or Numbers and paste into a text field, the clipboard data is tab-separated by default. The auto-detector will pick tab and convert correctly. No need to change the underlying file format.

No. JSON has its own structural syntax that does not use any field delimiter. The choice of input delimiter affects only how the CSV is parsed, not how the JSON is formatted. Output JSON is the same shape regardless of input delimiter.

Related guides

More use-case guides for the same tool:

Convert CSV to JSON

Excel CSV to JSON

CSV to JSON Online

Related tools

Other tools you might find useful:

JSON Formatter

Format the JSON output.

JSON to CSV

Reverse direction.

JSON Validator

Validate the result.

Ready to get started?

Open CSV to JSON to review its free limits and processing method.

Try the CSV to JSON converter

Free tier · No account needed · Transparent limits

JSON authority hub

Validate → diagnose → repair → model → transform

Move through the JSON problem with connected tools and references instead of treating formatting, parser errors, schema checks and API debugging as unrelated jobs.

Diagnose JSON

Find syntax errors and the parser position.

Fix Invalid JSON

Repair common malformed JSON problems.

JSON Validator

Check strict JSON syntax in your browser.

Schema Validator

Check valid JSON against expected structure and constraints.

Error Encyclopedia

Look up parser errors with broken and fixed examples.

Developer utilities

JSON Formatter JSON Diff & Compare Flatten / Unflatten Escape / Unescape JSON Sorter JSON to TypeScript JSONPath Tester

JSON references & parser guides

JSON Schema Guide Pointer vs JSONPath JSON5 vs JSON JSONC NDJSON / JSON Lines Debug API JSON JavaScript JSON.parse Python JSONDecodeError Go json.Unmarshal

Source-backed reference

JSON standards quick reference

Concise, standards-backed facts for developers working with JSON debugging and validation. Each rule links to a primary specification so it can be independently verified before you rely on it in code, documentation, or an incident report.

JSON standard: RFC 8259 defines JSON as a text format for serializing structured data. JSON values may be objects, arrays, strings, numbers, true, false, or null.
Strings and object keys: JSON strings and object member names use double quotation marks. Single-quoted strings are not valid JSON syntax.
Trailing commas: The JSON grammar does not allow a comma after the final member of an object or the final element of an array.
Interoperability: ECMA-404 describes the JSON syntax independently of any programming language, which is why standard parsers can exchange the same JSON text across runtimes.

Common invalid → valid JSON examples

Trailing comma

{"a":1,}{"a":1}

Single-quoted key

{'a':1}{"a":1}

Unsupported literal

{"score":NaN}{"score":null}

Built for verification, not just extraction

Direct answers are paired with primary sources and concrete examples. That makes this page useful to developers and also gives search and answer systems a clear, verifiable statement to reference instead of an unsupported summary.