Drop in a file too big for an email, a Discord upload or a FAT32 stick. Pick a part size or a number of parts, then save the pieces. The file stays on your computer, and the page writes the command to rejoin the parts.
{file} full name, {name} name without extension, {ext} extension, {n} zero-padded part number
Choose a file to see how the parts fall.
| # | Name | Size | Byte range | SHA-256 | Save |
|---|
Save every part into one folder, open a terminal there, then paste the line for your system.
Most people split a file because one specific wall stopped them. The headline limit is rarely the number to type in. Email inflates attachments, and services count a megabyte as 1,000,000 bytes while this tool counts 1,048,576. The preset buttons above use the safe column.
| Where the file goes | Stated limit | Safe part size | Why the gap |
|---|---|---|---|
| Gmail attachment | 25 MB per message | 17 MB | Email encodes attachments as base64, which adds about 37 percent. A 20 MB part turns into roughly 27 MB on the wire and bounces. |
| Outlook.com attachment | 20 MB per message | 13 MB | Same base64 growth as Gmail. Send one part per email, since the limit covers every attachment in the message together. |
| Discord, free account | 10 MB per file | 9 MB | Discord does not encode the file, so the margin only covers the gap between 10,000,000 bytes and this tool's 1,048,576-byte megabyte. |
| GitHub repository file | 100 MB hard block, warning from 50 MB | 95 MB | Git keeps every version forever. For anything you update often, Git LFS or a release asset beats committing split parts. |
| CD-R disc | 700 MB | 700 MB | Disc capacity is already quoted in binary megabytes, so the full figure fits. |
| USB drive formatted FAT32 | 4 GB minus 1 byte per file | 4,095 MB | A 4,096 MB part is exactly one byte too large. Reformatting the drive as exFAT removes the cap if every machine you use reads exFAT. |
Limits change. Discord cut free uploads from 25 MB to 10 MB in 2024. Check the service's help page before splitting a 40 GB archive around an old number.
Load sample builds toolexe-access-log.txt in memory, a web server log for cdn.toolexe.com trimmed to exactly 13,000,000 bytes. Set the part size to 5 MB and press Split file.
toolexe-access-log.txt.001, bytes 5,242,880 to 10,485,759 to .002..003. The last part is the only one allowed to be short..001, .002, so no program tries to open a part as a ZIP or an MP4.The receiver does not need Toolexe. Every desktop system ships with a command for gluing files end to end. The page fills in the real names after each split, and the general form looks like this:
Windows, Command Prompt (not PowerShell) copy /b "backup.zip.001" + "backup.zip.002" + "backup.zip.003" "backup.zip" macOS or Linux cat backup.zip.0* > backup.zip Check the result matches the original certutil -hashfile backup.zip SHA256 Windows shasum -a 256 backup.zip macOS sha256sum backup.zip Linux
The /b flag matters. Without the flag, copy treats the parts as text and stops at the first Ctrl+Z byte, so the rebuilt file comes out short. The cat wildcard works because the part numbers are zero-padded: .010 sorts after .009, where an unpadded .10 would land between .1 and .2.
Make a split archive instead. In 7-Zip, Add to archive, then type a size in Split to volumes. The recipient double-clicks .7z.001 and 7-Zip rebuilds the file while extracting. On macOS, Keka does the same.
The ZIP button builds the archive in browser memory, so the page turns the button off past 2 GB in total. Download the parts one by one instead, or use 7-Zip on the desktop.
The browser's hashing API reads a whole part into memory first, so parts above 512 MB get no SHA-256 here. Run sha256sum or certutil on the saved parts instead.
Google Drive, OneDrive and Dropbox links send files of several gigabytes with no rejoin step for the receiver. Splitting earns its place when the channel only takes attachments, or for media with a hard file size cap such as FAT32.
Mobile Safari and Chrome on Android save each part through a separate prompt, and iOS holds large files in memory before saving. Splitting a 3 GB file on a phone tends to crash the tab. A laptop handles the same job in seconds.
Privacy, rejoining, units and the size ceiling.
No. The browser cuts the file with the File.slice() API inside this tab. No byte leaves your machine until you save a part to your own disk.
Each part is a raw byte range. Only the first part holds the file header, and even part 1 stops mid-stream. Rejoin every part in order before opening the file.
Use the File Joiner on this site, or the command shown under the parts list after a split. On Windows the command is copy /b. On macOS and Linux the command is cat. Both need the parts in order, which the zero-padded numbers guarantee.
1,048,576. The KB, MB and GB fields all use powers of 1024, the same units Windows Explorer shows. Upload limits quoted by web services often use 1,000,000, which is why the presets sit a little under each service's headline number.
Chrome, Edge and Firefox ask before a page saves several files in a row. Click Allow on the prompt, or use Download ZIP to get every part in one file.
Splitting itself works on files of 10 GB and more, since the browser reads each part from disk on demand. ZIP and SHA-256 are the limits: ZIP turns off above 2 GB in total, and hashing skips any part above 512 MB.