How to detect a CSV delimiter without uploading it
A CSV that will not import is usually not broken data — it is the wrong separator. A team expects commas and receives semicolons. A European export uses semicolons because commas are decimal points there. A data pipeline hands over tabs, a command-line tool hands over pipes. The file looks fine in a text editor, and every import either collapses into one column or explodes into dozens.
This tool finds the separator where the file already is: on your own device. When you paste text or drop a file here, your browser:
- Scores every candidate delimiter — comma, semicolon, tab, pipe, colon and space, plus any custom character you supply — by parsing a sample of your text with a quote-aware parser and counting how consistently rows split into the same number of columns. A delimiter inside a quoted field never counts.
- Reports the winner with a confidence verdict — High, Good, Uncertain or Low — plus the full score table, so you can see why it won and how close the runner-up was. The header row is called out, and any row whose column count disagrees is named by line number.
- Shows a parsed preview and a one-click re-export — the first rows split on the detected delimiter, so a wrong call is visible at a glance, and a download that rewrites the file with the delimiter of your choice, quoting fields that need it.
What makes this detector different
The pages that top the results for this search mostly process your text on their server, cap the input at 200 KB, or sell the same check as a paid API — and the linters that include detection treat it as a side feature of a bigger report. This page is the only free, fully client-side dedicated delimiter detector we found that shows its work: every candidate scored in the open, a parsed preview, header detection, batch detection across 20 files, and a re-export with a chosen delimiter — with no daily limits, no account and no upload — plus a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to.
When is detecting the right choice — and when is it the wrong one?
Detecting is right whenever a file has to import somewhere else: a spreadsheet, a database, a CRM, a mail merge, or a data pipeline that expects a specific separator. It is the wrong choice for a file you only ever open yourself in a text editor, where the separator never matters, and for a file whose rows genuinely have different column counts — ragged data cannot be fixed by choosing a delimiter, and the score table will show that plainly. If the source system can export again, export with quoting switched on instead of patching the file.
Honest limitations
Heuristic, not a validator
This tool scores candidates on column-count consistency — it is not a CSV validator. It cannot certify that a file is well-formed or that its values are correct.
Unquoted delimiters in data
If a comma appears inside unquoted free text in a comma file, no detector can tell data commas from separator commas. Quote those fields in the source export.
Space is the weakest candidate
Ordinary sentences can split “consistently” on spaces by accident. A space win with a low score is reported as uncertain — check the preview before trusting it.
Header detection is a guess
The first row is called a header when it is all distinct, non-numeric text. A data row that happens to look like that will be miscalled — the preview shows the call.
Sampled, not whole-file
Detection is scored on the first 100 KB and 200 rows of each source. A file whose delimiter changes halfway through will be scored on its opening — the ragged-row warning flags the rest.
It never changes your file
This tool only reports and re-exports to a new download. Your original file is never modified — to fix broken quoting, repair the export in the application that made the file.