Count rows, columns, and cells in large CSV files
Count data rows, header columns, total cells, and non-empty cell percentages in any CSV.
🛡️ Your rows never leave your browser.
Why Onfyt: Reports stats without loading a full grid—handles 500,000-row files in under a second using streaming browser parsing.
Interactive Sample Data
| id | name | |
|---|---|---|
| 1 | Grace Kerubo | grace@corp.com |
| 2 | Peter Njoroge |
How this tool works
Before processing a CSV file, engineers need to know its dimensions: how many data rows (excluding header), how many columns, how many non-empty cells, and what the completeness rate is. This information determines whether the file matches an expected schema ('should be exactly 5,000 rows and 12 columns') and guides memory planning for large-file ETL jobs.
DataFix reads the file in-browser and returns a compact stats card without loading the entire dataset into a grid. This is especially useful for very large files (100,000+ rows) where opening in Excel would take minutes.
Verifying file dimensions prior to ETL ingestion confirms that bulk exports completed without premature socket timeouts or record truncation. In addition to measuring raw line counts, our engine computes true logical record counts, accounting for multi-line quoted fields that span multiple physical lines.
Accurately auditing CSV file dimensions before downstream ingestion prevents silent truncation bugs in production ETL pipelines. In legacy data feeds, missing final line breaks or truncated network buffers can result in severed final records. Our streaming dimensional scanner reads character-by-character boundaries across CRLF and LF variations, verifying that the logical record matrix matches expected relational constraints across every single row.
Auditing spreadsheet dimensions before launching automated ETL scripts verifies that exports completed without truncated file buffers. By distinguishing physical newline characters from logical quoted records, our counter computes true tabular dimensions with complete accuracy.
Things that usually go wrong
- Multi-line cells (line breaks inside quotes) are counted correctly as one row.
- BOM-prefixed files add a phantom character to the column count of the first column.
Edge cases we tested
🧪 File with no newline at end
Last row counted correctly; no phantom empty row added.
🧪 Header-only file (no data rows)
Reports 0 data rows; column names listed.
🧪 Quoted cells containing embedded newlines
Multi-line cells counted as one row correctly.
Frequently Asked Questions
Is the header row counted in the row count?
The tool reports both: 'X data rows + 1 header row = X+1 total rows'.
Can I count rows without uploading?
No — the file must be parsed to count accurately.
Related tools
Validate
Validate CSV
Audit CSV files for structural errors, encoding problems, and row-length inconsistencies.
Open Tool →
Validate
Validate JSON
Parse and validate JSON strings to expose syntax errors at exact line and column positions.
Open Tool →
Validate
Find Duplicate Rows
Identify and count duplicate rows in CSV files by exact match or by key column selection.
Open Tool →