10 Common CSV Formatting Mistakes (and How to Fix Them Instantly)

Most CSV headaches are not caused by “big data” problems. They are caused by ten small, predictable formatting mistakes that show up in almost every export. Once you know the pattern, the fix is usually a single click.

This post walks through ten common CSV formatting mistakes, how to inspect them in CSV Preview, and where to correct the source data or export settings.

1. The wrong delimiter

“CSV” is a misnomer: files use commas, semicolons, tabs, or pipes depending on locale and source system. Open a semicolon file with comma settings and you get a single column full of separators.

Fix: Check the separator in the export settings and match it to the importer. Re-preview after conversion to confirm the columns line up.

2. Stray BOM (byte order mark)

UTF-8 files saved by some Windows tools start with a hidden \uFEFF byte. Most readers ignore it, but a few break - and the first column header often shows up as \uFEFFname instead of name, breaking lookups.

Fix: Open the file in a UTF-8 aware editor, or strip the BOM when you re-export. CSV Preview surfaces the issue by showing a garbled first character.

3. Encoding mismatches (UTF-8 vs Windows-1252)

Names like José or Müller show up as José when a UTF-8 file is read as Windows-1252. This is the single most common cause of “weird characters” in CSV exports.

Fix: Re-export from the source as UTF-8, or convert with a tool that lets you pick the source encoding before you import.

4. Inconsistent quoting

A field with a comma in it must be quoted, but not every tool quotes consistently. Mix quoted and unquoted fields with embedded commas, and the next parser will split rows at the wrong place.

Fix: Use a CSV-aware parser to check column counts. Rows with the wrong number of columns can indicate broken quoting; correct the quoting in the source export.

5. Mixed line endings (CRLF vs LF)

Windows saves files with \r\n, Unix with \n, and old Mac files use \r. Mixing them on the same row is rare, but exporting a file across platforms often leaves both styles in one document. Strict parsers refuse; lenient ones merge rows.

Fix: Normalize to a single line ending when you re-export, or use a tool that accepts either.

6. Trailing commas and empty rows

Spreadsheet exports love to tack an extra , at the end of every row and add a few empty rows at the bottom. The empty rows are harmless; the trailing commas create an extra empty column that confuses downstream tools.

Fix: Column Tools can drop blank columns in one pass, or trim trailing delimiters when you re-export.

7. Inconsistent date formats

2026-08-30 or 08/30/2026 or 30/08/2026 - three rows, three formats. Sorting, filters, and database imports all silently produce wrong results.

Fix: Pick an ISO (YYYY-MM-DD) format for exports and stick to it. Find & Replace can help reshape legacy dates when re-exporting is not an option.

8. Whitespace you cannot see

Leading or trailing spaces in column values cause silent duplicates and missed joins. "John" and "John " look the same until you dedupe.

Fix: Data Process can trim whitespace from selected columns before deduplication or import.

9. Duplicate headers or rows

CRM exports often repeat the header row in the middle of the file. Combined with genuinely duplicate rows, that single header repetition is enough to break a unique import.

Fix: Remove Duplicates drops exact duplicates, and you can choose specific key columns (like email or order_id) to dedupe by business identity.

10. Numbers stored as text

Leading zeros (00123), currency symbols, or thousands separators turn numeric columns into text on import. ZIP codes lose their leading zero, IDs lose their formatting, and arithmetic silently fails.

Fix: Keep IDs and codes as text in the spreadsheet (format the column as “Text” before pasting), and strip currency symbols before numeric conversion. Find & Replace handles the symbol stripping; CSV to JSON preserves text types when you need structured output.

Quick checklist

• Preview - confirm columns line up before doing anything else.

• Fix delimiter - get real columns first.

• Validate - catch structural issues early.

• Normalize encoding, dates, and whitespace.

• Dedupe on the right key column.

• Convert to JSON or XLSX only after cleanup.

Why browser-only

The files that need this kind of cleanup are usually the sensitive ones: CRM exports, finance reports, employee lists. RividTech runs every step client-side, so your rows never leave your device while you fix the formatting. See our Privacy Policy for the details.

Get started

Begin with CSV Preview, correct delimiter or quoting issues in your source, then use Remove Duplicates and Data Process for cleanup. These browser tools process your data locally.