What counts as an 'incomplete record'?

Any data row whose cell count doesn't equal the header row's cell count. Most commonly this means fewer cells (missing trailing values), but a row with extra cells is also flagged as a mismatch.

Does this tool fix the incomplete rows, or just list them?

It only lists them, with row numbers and cell counts, so you can decide how to fix each one. Use the incomplete record filler if you want short rows padded automatically.

What row number does it report for a row that spans multiple physical lines?

It reports the data-row position (counting the header as row 1), not the raw physical line number, since a single row can legitimately span multiple lines when a field contains a quoted embedded newline.

What if there are no incomplete records?

The tool reports that every data row matches the header's cell count, so a clean result is unambiguous.

CSV Incomplete Record Finder - List Ragged Rows

Overview

Introduction

When a CSV import fails or produces misaligned columns, the usual culprit is a handful of rows with the wrong number of fields. This tool finds exactly which rows those are, instead of leaving you to eyeball a large file.

It reports each mismatched row by number along with its actual and expected cell counts, so you can jump straight to the problem.

What Is CSV Incomplete Record Finder?

A diagnostic tool that scans every data row in a CSV file and flags any row whose cell count doesn't match the header's.

It's read-only: it identifies incomplete or overlong records without modifying the file.

How CSV Incomplete Record Finder Works

The input is parsed with a full RFC 4180-aware parser into a grid of rows, so quoted fields containing delimiters or embedded newlines are handled correctly rather than causing false positives.

The header row's cell count becomes the expected value, and every subsequent row is checked against it; any row with a different count is recorded with its row number and actual cell count.

When To Use CSV Incomplete Record Finder

Use it right after a CSV import or export fails validation, to pinpoint exactly which rows are malformed.

It's also useful as a quick health check on a large CSV file before committing to further processing.

Often used alongside CSV Incomplete Record Filler, CSV Validator and CSV Extra Comma Remover.

Features

Advantages

Pinpoints exact row numbers instead of a vague 'malformed CSV' error.
Correctly handles quoted fields with embedded commas or newlines when counting cells.
Runs entirely client-side, so the file never leaves your browser.

Limitations

Row numbers count data rows (with the header as row 1), not raw physical lines, since one row can span multiple lines.
It only flags cell-count mismatches, not other structural problems like unclosed quotes: use the CSV validator for a fuller conformance check.

Examples

Finding a short row

Input

id,name,active
1,Ada,true
2,Alan
3,Grace,true

Output

Row 3: 2 cell(s), expected 3

Row 3 (the second data row, 'Alan') only has 2 cells against a 3-column header, so it's reported by row number.

Best Practices & Notes

Best Practices

Run this before the incomplete record filler if you want to manually review which rows will be padded.
Cross-check flagged rows against the raw file to see whether the missing data can be recovered, rather than always padding with blanks.
If most rows are flagged, check whether the delimiter is actually correct for the file before assuming the data itself is broken.

Developer Notes

This shares the same row-length comparison as the CSV validator's ragged-row check, but returns a dedicated `incompleteRecords` array alongside the human-readable summary, so a caller that only cares about the row list doesn't need to parse the summary text.

CSV Incomplete Record Finder Use Cases

Diagnosing which specific rows caused a CSV import to fail
Auditing a large CSV export for missing trailing values before analysis
Reviewing incomplete records manually before deciding how to fill them in

Common Mistakes

Assuming a flagged row is always missing data at the end; a row can also have too many cells if a value wasn't properly quoted around an embedded comma.
Confusing the reported row number with a raw text line number when the file contains quoted multi-line fields.

Tips

Once you've reviewed the flagged rows, the incomplete record filler can pad the short ones automatically in one step.
If a row has too many cells instead of too few, the extra comma remover addresses that case specifically.

CSV Incomplete Record Finder