Line Chunker: control text line structure
Paste the source, set Lines per part, and select Process text. Each part has its own download link; the preview and copy control refer only to the first part.
Try the example
Load example sets Lines per part to 2. Five entries create three files. part-001.txt contains one and two, part-002.txt contains three and four, and part-003.txt contains five. Download each file you need; this tool does not automatically download multiple files or create a ZIP.
Exact transformation rules
Parts contain sequential groups with no repeated headers and no overlapping rows. Empty lines count toward each group’s size. The final source terminator is not an extra entry. Each exported part uses LF separators and adds no final terminator; concatenating files without inserting a separator will not reconstruct the original text.
Use this for dividing a line-based checklist or input queue. For CSV records with quoted embedded line breaks, use CSV Row Splitter; splitting physical text lines is not CSV parsing.
Limits and result review
Lines per part accepts integers from 1 to 10,000, with at most 100 files per run. Each input supports 100,000 UTF-16 code units and 10,000 logical lines. Unpaired UTF-16 surrogates are rejected so UTF-8 export does not silently replace them. Browser textareas may normalize CRLF or CR before processing. A result consisting of an empty entry can produce a zero-byte file; inspect the reported count and source before treating it as no data.
Changing text or settings clears the old preview and download links. Processing does not overwrite a local source file. Download results before reloading if you need to keep them.
Use Unicode Code Point Inspector to inspect unexpected character sequences. Use Line Range Extractor when the task is selecting specific consecutive lines rather than changing their layout.





