Last updated
Common Use Cases
- Sending large files via email (split to stay under attachment limits)
- Uploading large files to cloud storage with size restrictions
- Processing large CSV/log files in memory-constrained environments
- Transferring large database backups over unreliable connections
- Parallel processing of large datasets
- Splitting large video files for upload to platforms with size limits
The File Splitter on TechConverter.me generates numbered chunks with checksums and ready-to-run reassembly scripts, making it easy to split any file and reconstruct it reliably on any platform.
Examples
Example 1: Splitting for Email Attachments
A 75 MB archive needs to be sent via email (25 MB limit per attachment):
Input: project-backup.zip (75 MB)
Split by: size
Chunk size: 24 MB (leaving room for email overhead)
Output:
project-backup.zip.001 (24 MB)
project-backup.zip.002 (24 MB)
project-backup.zip.003 (24 MB)
project-backup.zip.004 (3 MB)
checksums.txt (SHA-256 for each part)
reassemble.sh (Linux/macOS reassembly script)
reassemble.bat (Windows reassembly script)
Send parts 001-004 in separate emails.
Recipient runs reassemble.sh to reconstruct the original file.
Example 2: Splitting a CSV File by Line Count
A 10-million-row CSV needs to be processed in batches of 1 million rows:
Input: sales-data-2025.csv (2.3 GB, 10,000,000 rows)
Split by: line count
Lines per chunk: 1,000,000
Preserve header: yes
Output:
sales-data-2025_part001.csv (230 MB, rows 1-1,000,000, with header)
sales-data-2025_part002.csv (230 MB, rows 1,000,001-2,000,000, with header)
...
sales-data-2025_part010.csv (230 MB, rows 9,000,001-10,000,000, with header)
Each part is a valid, self-contained CSV with the header row included.
Process each part independently or in parallel.
Example 3: Splitting a Database Backup
Input: production-backup-2026-03-17.sql.gz (48 GB)
Split by: size
Chunk size: 1 GB
Output: 48 parts (production-backup-2026-03-17.sql.gz.001 through .048)
Transfer strategy:
- Upload each 1 GB chunk independently
- If a chunk fails, retry only that chunk
- Verify checksums after all chunks are transferred
- Run reassemble script to reconstruct the backup
- Restore from the reassembled file
Advantage over single-file transfer:
A failed 48 GB transfer requires restarting from 0 GB.
A failed 1 GB chunk only requires retrying 1 GB.