Split a CSV Into Multiple Files

No. “Rows per file” counts data rows only - with the header option on, each file gets the header row plus up to that many data rows. Splitting 250 data rows into files of 100 gives you three files: 100, 100, and 50 rows, each with the header on top.

They take the original file’s name with a numbered suffix - orders.csv split three ways becomes orders-part-01.csv, orders-part-02.csv, orders-part-03.csv. The numbers are zero-padded so the files sort in the right order in any file manager.

Correctly - this tool reads the whole file with a full CSV parser, so a quoted field like "Smith, John" or a quoted field containing its own line break is kept as one field of one row. That matters more for splitting than almost any other CSV operation: a tool that split on raw line breaks would cut a multi-line field in half and corrupt both output files around it.

The usual reasons: a tool or form that caps how many rows it accepts per import (many CRM, email, and e-commerce importers stop at 500–10,000 rows), a spreadsheet that struggles with a very large file, or sharing a big export in reviewable pieces. Set “Rows per file” to whatever your importer’s limit is and each piece comes out ready to load.

No. The file is read, split, and zipped entirely on your device. Turn off your Wi-Fi after the page loads and it still works. This page loads 11KB of JavaScript, gzipped - about what your browser's network tab will show for this page's own scripts.

Rows whose cells are all empty are dropped rather than carried into an output file - they’d otherwise waste a slot in a row-count split and show up as empty lines mid-file. Rows with any real content are kept exactly as they are.

The input file is capped at a generous size (shown on the drop zone) so a single huge file can’t freeze the tab, and one split is capped at 2,000 output files - if your settings would produce more, the tool says so and asks you to raise “Rows per file” rather than silently building a zip your browser can’t handle.