Look at the separators
Consider this synthetic export:
Product;Quantity;Price
Notebook;4;12.50
Desk lamp;2;29.00
The fields are separated by semicolons. Reading it as comma-separated text leaves each row in one column. A tab-separated export has the same problem when opened with the wrong delimiter.
Try the delimiter control
- Open the .csv or .tsv file in QuickDataView.
- Start with automatic CSV delimiter detection.
- If the preview still has one column, select semicolon, comma or tab as appropriate.
- Check that headings and a few rows line up before exporting filtered CSV.
Do not replace every separator by hand
A quoted field can contain its own comma, semicolon or newline. Replacing punctuation globally can damage text values. For example, a comma inside a quoted address belongs to the address. Use a CSV-aware reader rather than a text replacement.
When the delimiter is not the problem
Unclosed quotes, inconsistent rows or an export that is actually another format need investigation in the source system. QuickDataView cannot infer every exporter’s intent. Ask for a small synthetic sample when discussing the issue, and retain your original file.
The local preview costs nothing and does not upload your data. Once columns make sense, use the CSV viewer guide for search and filtered export, or check leading-zero identifiers.
Credit to the format’s makers
CSV owes its usefulness to decades of spreadsheet and data-export practice rather than a single creator. Yakov Shafranovich’s RFC 4180 documents a common comma-separated convention. That simplicity makes a small export easy to move between tools.
Format reference: RFC 4180’s CSV documentation. Reference checked 7 October 2026. These links acknowledge the format; they do not imply endorsement or a partnership.