File Merger

Joins file parts in the order you select them 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.

Select the parts from first to last. Parts named report.pdf.part-001 download again as report.pdf.

How to use it

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

Limitations

Joining selected byte ranges in picker order

Order is the order you selected

Choose at least two files. Fewer than two is an error that asks for at least two parts, in order. The bytes of each file are appended in the order of that selection. There is no sort by part number. If you click part 003 before part 001, the output has those bytes in that clicked order and will not match the original. After the join, the panel shows the part count and the total length. That length should match the original file when you selected every slice exactly once, in sequence, and nothing else.

What the restored name depends on

When every selected name has the same stem followed by .part- and exactly three digits, the download is named that stem. quarterly.pdf.part-001 together with quarterly.pdf.part-002 downloads as quarterly.pdf. If any selected name fails the pattern, or the stems disagree, the tool still concatenates the bytes and leaves the download name unset. The three-digit pattern is the one the splitter writes. A hand-named piece that uses part-1 with a single digit will not satisfy it. The merger does not open manifest.json and does not read the recorded length. If you include the manifest in the selection, its JSON bytes are inserted into the output at that position and the file is corrupt relative to the original.

The parts ZIP is not the input

The splitter’s download is a ZIP of the slices. This page does not unzip that archive. Extract the members first, then select the part files in order from the picker. Selecting the .parts.zip itself as one of the inputs would append ZIP bytes, not the slices inside it. After a correct join, the result is a single binary blob of the concatenated ranges. A split PDF becomes a PDF again only if the slices were pure byte ranges of that PDF and you put them back in order. Check the total length against the manifest’s recorded size if you still have that JSON open beside you. The merger itself will not do that comparison.

Privacy

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