BREAK A FILE UP · VERIFY EVERY BYTE BACK

File Splitter & Verified Joiner

Split a binary file into raw byte chunks and a SHA-256 manifest. Reassemble only when every part and the complete original checksum match.

1. Choose a workflow

Workflow

Original file (up to 100 MiB)

No source selected.

Chunk size

100 MiB original maximum · 200 parts maximum · 64 KiB–25 MiB chunks · two-minute worker limit. Larger files require larger chunks. Empty files produce one empty chunk.

Chunks are raw bytes, not independently usable media or multi-volume ZIP files. The ZIP is a convenience package; unzip it before joining. Your originals are never changed.

2. Check & download

Choose a source or try the sample.

No completed output.

Part	Filename	Bytes	SHA-256

Split, transfer and rebuild

Select the original and choose a chunk size. Run and download the ZIP containing raw parts, manifest.json and instructions.
Unzip the package and retain the manifest with every part. Transfer parts individually if required.
Switch to Verify & join, select the manifest and all .bin parts. File selection order does not matter; descriptors determine order.
Download the original only after all part hashes and its complete checksum match.

What verification can prove

A missing, duplicate, wrongly sized or altered part stops reassembly. Hashes detect mismatch with this manifest, not authenticity or safety. An attacker who replaces both parts and manifest can supply matching hashes. Keep a trusted manifest or original checksum independently.

No automatic archive import, encryption, parity repair or recovery of missing parts is provided. The entire bounded file may be held in memory; use smaller files on low-memory devices.

Using File Splitter & Verified Joiner

Break a bounded binary file into byte chunks and verify every piece when rebuilding it.

Select the original, choose chunk size and download the parts ZIP.
Unzip and keep manifest.json with all numbered parts.
Choose the manifest and parts in Join mode; download after all hashes match.

Example

The 150,000-byte sample produces three parts at 64 KiB, including a shorter final part.

Questions & answers

Can I join parts in any order?

Yes. The manifest determines order by exact numbered filename. Missing, extra, duplicate, wrongly sized or mismatching parts stop reassembly.

Is the package a multi-volume ZIP?

No. It is a regular ZIP containing raw byte chunks and a manifest. Unzip it first, then select manifest.json and the .bin parts separately.

What are the limits?

The original file is at most 100 MiB, with 200 parts maximum and chunk sizes from 64 KiB to 25 MiB. Worker jobs stop after two minutes. Empty files use one empty part.

Can this repair missing or damaged parts?

No. It detects missing or changed parts but has no parity repair or recovery mechanism. Retain the original until you verify the reassembled copy.

Does a matching checksum prove safety?

No. Hashes verify agreement with the manifest, not authenticity or safety. Keep a trusted manifest or checksum independently. Files are never executed or uploaded for processing.