Skip to Content
RowSlice

Guides

CSV Guides

Practical answers to the problems that come up when CSV files get large or messy.

Every guide here starts from a symptom you can see on screen — a warning, a column of run-together text, a number that has turned into 4.5E+15 — and explains what the program is actually doing before it gets to the fix. Where a job is quicker with a tool than by hand, the guide says so and links to it.

4 guides

When the File Won’t Open Properly

Excel shows an error, loads only part of the file, or the computer struggles to open it at all.

5 guides

When the File Is Over a Limit

Google Sheets, an upload form or an email refuses it, and it has to get smaller or be split.

3 guides

When Excel Changes Your Values

The file opens fine, but the values in it are no longer the ones you exported.

3 guides

Encoding and Delimiter Problems

Every row lands in one column, or accented characters arrive as nonsense.

5 guides

Combining, Splitting and Cleaning Files

Several exports have to become one, or one has to become several, without duplicates or shifted columns.

FAQ

Questions About CSV Files

What exactly is a CSV file?

A CSV is a plain text file in which each line is a record and a separator character — usually a comma — marks the boundary between fields. There is no formatting, no formulas, no column types, and nowhere in the file to record which character encoding or delimiter it uses. That last gap is the root of nearly every problem covered in these guides.

What is the difference between a CSV file and an .xlsx file?

A CSV holds text only; an .xlsx workbook holds text plus types, formats, formulas, several sheets and charts. That difference is why opening a CSV in Excel is lossy in one direction: Excel has to guess a type for every value, and it guesses wrongly on ZIP codes, long IDs and date-like codes. Converting a CSV to Excel covers the import route that avoids the guessing.

Is my CSV corrupted, or is the program just reading it wrongly?

Almost always the second. Garbled accents, everything landing in column A, and long numbers shown as 4.5E+15 are produced by the program reading the file, not written into the file. The bytes on disk are usually intact, which is why one export can look perfect in a text editor and wrong in Excel. The common exception is genuinely missing quoting in the original export, which no reader can undo.

What is RFC 4180, and does my CSV have to follow it?

RFC 4180 is the closest thing CSV has to a specification, and it is what the tools here follow. It says a field containing a comma, a double quote or a line break is wrapped in double quotes, and that the last record may or may not end with a line break. Nothing enforces it and plenty of real exports break it — but files that follow it survive being read by other programs.

Why does the same CSV look different in Excel, Google Sheets and a text editor?

Because each one guesses differently. A text editor shows the raw characters and guesses only the encoding. Excel splits on your Windows list separator and converts anything that looks like a number or a date. Google Sheets asks you for a separator and offers to convert types. The file does not change between them; three programs simply apply three sets of assumptions to the same bytes.

Which guide should I read first if my CSV will not open properly?

Start from the symptom. Everything in one column is a delimiter problem: why your CSV opens in one column. Strange accented characters are an encoding problem: UTF-8, UTF-16 and Windows-1252. A warning that the file was not loaded completely is a size problem: opening a CSV too large for Excel.