Large-file friendly
Incremental checksums read small portions at a time, rather than loading the whole file into memory.
Split files into exact-size chunks. Put every byte back together with checksum verification. Simple, secure, and completely local.
Any file type—video, archive, document, or disk image.
Each part is a separate file; the final part can be smaller.
Thoughtful details for file transfers, backups and offline workflows.
Incremental checksums read small portions at a time, rather than loading the whole file into memory.
Processing stays in your browser. No account, server upload, or hidden storage.
Every numbered part and the final reassembled file are checked with SHA-256.
Choose a local file and select a part size, for example 25 MiB or 100 MiB.
Generate checksums, then save a folder of numbered parts plus the JSON manifest. Each part is checked while saving. On browsers without folder access, download each part separately.
Load the manifest and all parts, verify their hashes, then save your reconstructed file.
No. Files are read and processed locally by your browser. The tool requires no network request or account to split, verify or reassemble them.
Any nonempty file, including MP4, ZIP, PDF, ISO, database backups and project archives. The parts are binary segments, not independently playable or readable media files.
Keep every .pkpart000001-style chunk and the .pixelokay-manifest.json file. Open the Reassemble tab, add the manifest and chunks, verify, then save the result. Direct disk saving checks the bytes again before committing.
In supported desktop Chromium browsers on localhost or HTTPS, folder save and file save let the tool write incrementally. Other browsers use Blob-backed downloads, which can fail for very large files due to browser and device limits. Verify disk space before starting.
You can transfer and store the parts individually, but this tool requires its manifest to validate checksums and reconstruct the original file. Keep the manifest alongside the parts.
Divide a local file into numbered binary parts with a versioned SHA-256 manifest, then verify a complete part set and reconstruct the original bytes.
Split a large archive into parts, store the manifest alongside them, then select all parts later and verify the reconstructed file hash against the original record.
Splitting does not encrypt, compress or add recovery parity. Hash agreement detects byte mismatches but does not authenticate an untrusted manifest. Native file/folder pickers and streaming support vary by browser; bounded download fallbacks apply. Cancellation can leave already completed parts, and the tool does not promise resume support. Keep the original until reconstruction is confirmed.
No. It verifies parts and reconstructed bytes but contains no parity data to rebuild missing content.
No. A hash comparison checks byte equality against the manifest, not manifest authenticity or file safety.