File handoff pack

Prepare renamed copies without losing the mapping

A client, reviewer or project folder may need a different naming convention from the one you use internally. File handoff pack creates a separate ZIP of sequentially named copies and records how every copy relates to its source. You can choose ordinary local files, review their order, and save the result without changing the original files on disk.

This tool does not inspect or render file contents. A photograph remains the same encoded photograph, a spreadsheet remains the same workbook and an empty file remains empty. Only the names of the copies inside the ZIP change. The included manifest records byte counts and SHA-256 digests so you or a recipient can compare extracted files with that record.

Build a handoff in four steps

1. Choose up to 100 files, with at most 20 MiB of file bytes in total. Selection replaces the current list rather than appending to it.
2. Enter a short prefix such as client or site-a. Prefixes use ASCII letters, digits, hyphens and underscores, beginning with a letter or digit.
3. Use Up, Down and Remove to arrange the displayed order. The file chooser's initial order may vary by browser, so review it before building.
4. Build the pack, review the complete mapping, then download the ZIP. You can also save the same manifest separately.

For example, the fictional sample becomes files/client-001.txt, files/client-002.bin and files/client-003.txt. The original names, including the Tamil filename, remain in the JSON manifest. Two source files with the same name still receive different numbered paths. No duplicate is silently removed.

Exactly how names are chosen

The number is the file's one-based displayed position, padded to three digits. The last filename extension is retained and changed to lowercase. A source called archive.tar.gz therefore becomes a numbered name ending in .gz; this does not decompress or convert the archive. A leading-dot name such as .env is treated as extensionless and receives a numbered extensionless name.

The tool rejects a final extension containing spaces, punctuation or more than twelve characters. Rename that source explicitly if needed, then select it again. This bounded naming rule avoids guessing whether punctuation belongs to an extension. Generated paths contain no source folder names, drive letters or original basename components. Their short ASCII names avoid common reserved-character and case-collision problems, but this is not a guarantee for every upload portal or filesystem.

What the downloads contain

The ZIP has a files/ folder, a manifest.json and a short README. For each selected file the manifest records position, exact original name, archive path, byte count and lowercase hexadecimal SHA-256. The table displays source names in JSON quotes so spaces and control characters are visible as data. The optional pack label is included in the manifest, not in the generated file names.

SHA-256 is a byte comparison aid here. A matching digest does not establish who created a file, whether its contents are safe, whether its extension is truthful or whether you may share it. This pack is not signed, encrypted or a virus scan. Metadata embedded inside the source bytes, including document authors or photo location information, remains present. Renaming does not remove it.

Limits to understand before handing files over

This is a flat selection of files. Folder structures, source timestamps, filesystem permissions, extended attributes and symbolic links are not preserved. ZIP entry dates are fixed to January 1, 1980, rather than presented as the original creation or modification dates. The ZIP uses uncompressed entries, so it will generally be larger than the selected data plus the small manifest and README. It is not intended for large folders, backups, forensic evidence or chain-of-custody records.

Existing references between files can break when names change. Do not use this workflow to rename the pieces of a website, linked project or software package unless you also update and test those references yourself. The tool cannot make a multi-file project work under new names. Check the recipient's required names, accepted extensions and unpacking process separately.

Temporary local processing

Selected files and generated results stay in this page's memory. The app has no account, upload step or automatic sharing. Building reads selected bytes to compute digests and assemble the ZIP; it does not open those files as webpages or send their contents elsewhere. Editing inputs or changing the list clears stale results, and Clear all or reloading discards the current selection. Downloads remain wherever your browser saves them, and the manifest itself contains the original filenames, so share it only with the intended recipient.