01
Prepare a portable collection
For a simple example, package a README and a few data files whose contents belong together. Give each a distinct basename before selecting it. This browser workflow sanitizes names and does not preserve a complete filesystem tree with ownership, permissions and symbolic links.
If the input is already one TAR file, the writer can compress that TAR directly. For a single supported ZIP or TAR.GZ input, the repacking path first reads its regular members. A RAR or 7Z file is not automatically extracted merely because the picker accepts its extension.
02
Check both layers of the result
This route loads a local 7-Zip engine and builds its output in memory. It caps the job at 1,000 files and 512 MiB of input members; practical limits can be lower. Bzip2 work can take time, so begin with a small representative package before attempting a large collection.
Open the download with an extractor that understands TAR.BZ2 and inspect the final files, not only the intermediate TAR. Confirm filenames and contents, then try the recipient's workflow. If you need a faithful backup of a Unix directory, make it with an archive tool that preserves the directory metadata you require.