What This Tool Does

This tool automatically fixes common CSV problems that cause import failures and data quality issues. Select which cleaning operations to apply, and get a clean, standardized CSV file. A change report shows exactly what was fixed.

Cleaning Options

Trim whitespace: Remove leading and trailing spaces from all fields. " John " becomes "John".

Remove blank rows: Delete rows where all columns are empty. Common artifact from copy-paste or export errors.

Remove BOM: Strip the Byte Order Mark from the start of files. Prevents "ColumnName" header issues.

Normalize line endings: Convert all line endings to LF (Unix style). Fixes mixed CRLF/LF issues.

Change report: See exactly what was cleaned: rows removed, BOM stripped, whitespace trimmed.

Common CSV Problems Fixed

Leading/trailing spaces: From fixed-width exports, manual editing, or copy-paste.

Before: "  Alice  ", " 30 ", " New York "
After:  "Alice", "30", "New York"

Blank rows at end: Excel and other tools often add trailing blank rows.

Before: 105 rows (100 data + 5 blank)
After:  100 rows

BOM markers: Windows Excel adds BOM that breaks some parsers.

Before: name,email
After:  name,email

Mixed line endings: Files edited on multiple systems have both CRLF and LF.

Example Cleaning Report

Cleaning Report:
- BOM removed: Yes
- Blank rows removed: 3
- Fields trimmed: 47
- Line endings normalized: CRLF → LF

Original size: 15.2 KB
Cleaned size: 14.1 KB

When to Use This

Before database imports: Clean data to avoid import errors from whitespace or blank rows.

After Excel exports: Excel often adds BOM and trailing blank rows.

Before data analysis: Whitespace causes grouping and matching issues in analysis tools.

API data preparation: Clean data before uploading to web services with strict validation.

Data quality improvement: Fix common issues that accumulate from multiple edits and exports.

What Is BOM?

BOM (Byte Order Mark) is a special character (U+FEFF) that some programs add at the start of UTF-8 files:

Added by: Windows Excel, Notepad, some Windows applications.

Problem: Parsers read it as part of the first column header, creating "name" instead of "name".

Fix: Remove BOM for compatibility with Unix tools, web applications, and most parsers.

Keep BOM if: You need the file to open correctly in Excel on Windows with accented characters.

Line Ending Types

CRLF (\r\n): Windows standard.

LF (\n): Unix, macOS, Linux standard.

CR (\r): Old Mac (pre-OS X). Rare today.

Mixed line endings cause parsers to miscount rows. Normalizing to LF ensures cross-platform compatibility.

Limitations

Large files: Works best with files under 50MB. Very large files may cause slow performance.

Complex issues: Doesn't fix structural problems like wrong column counts or encoding corruption.

Encoding: Assumes UTF-8 input. Other encodings may need conversion first.

Frequently Asked Questions

Will this change my data values?

Only whitespace at the start/end of fields is removed. Internal spaces and actual data values are unchanged.

Can I preview changes before saving?

The change report shows what was cleaned. Review it before downloading the cleaned file.

Should I remove BOM for Excel?

If the file is for Excel on Windows, keep BOM for proper accented character display. For web applications and databases, remove BOM.