File Splitter

Splits a file into ordered parts inside a ZIP, with a manifest on this page.

Use this tool

Drop a file here, or use the picker. The file type is checked from its contents.

Result

The result appears in this panel after you run the tool.

About this tool

Paths that contain .. are rejected. The work stays in this browser.

Each part keeps the original file name, as in report.pdf.part-001. File Merger joins those parts in the order you select them.

How to use it

  1. Open this page and provide the input it asks for.
  2. Set the options that are visible, then use Split file.
  3. Read the result in the panel. Copy it or download it when a file is offered. The input stays in this browser.

Limitations

Cutting a file into numbered byte ranges

The cut is a byte length

The part size starts at 1048576, which is 1 mebibyte. Any size below 1024 bytes is rejected, and so is a blank or non-numeric entry. The file is read as a byte sequence and sliced from the start, stepping by that size. The last slice is shorter when the length is not an exact multiple. Nothing about the format is interpreted. A PDF is not split on page boundaries. A JPEG is not split on scans. The chunks are raw ranges of the original bytes, and only the full sequence, in order, is the original file again.

Names, the manifest, and the ZIP you download

Each slice is named from the file’s base name plus .part- and a three-digit number, starting at 001. A report called quarterly.pdf yields quarterly.pdf.part-001, then .part-002, and so on. A manifest.json member records the base name, the original byte length, and the part count. Those slices and the manifest are packed into one ZIP named with .parts.zip on the base name. The status line tells you how many parts were written and that the file merger can join them in order after you extract them. The ZIP is the delivery container. The part size you typed is the slice length, not a compression setting. The packer uses its library default for the ZIP members.

How to use the pieces

Extract the ZIP, keep the part files, and ignore the manifest when you join, or at least do not feed the manifest to the merger as if it were a slice. The part numbers in the file names are the order. A size of 1024 on a small text file produces many tiny pieces and a ZIP that may be larger than the text, because each member has overhead. Choose a size that matches the limit you were given, such as a mail cap, and check the part count in the status before you send the archive. The source file is not modified. You can change the size and run again to get a different set of slices.

Privacy

Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.