MakeFileWork

Create a ZIP from your files

Select files, package them into one verified ZIP, and download it. No folder paths from your device are included.

What this tool actually does

Create ZIP works with the real archive structure or creates a new container; it does not rename an extension. The workflow is designed for bounded local processing, with size and entry limits that prevent uncontrolled expansion or browser resource use.

How the result is verified

MakeFileWork validates the structure it creates or inspects and reports which entries could be processed. An archive operation is ready when the resulting container can be serialized and the expected entries are present, not simply because a file can be offered for download.

Limits and fidelity

TAR and TAR.GZ archives can contain traversal paths, symbolic links, colliding names and special entry types. Universal batch rejects those archives rather than offering falsely verified downloads. A valid GZIP stream alone does not prove that the claimed TAR is valid. Size and expansion limits also apply.

When to use this workflow

Use this workflow to package, inspect or extract supported archives. If a ZIP is damaged and the goal is content recovery, use the dedicated ZIP repair workflow instead because it distinguishes verified, partial and incomplete recovery.

Privacy and final verification

Keep the original file until the output has been reviewed in the destination application or portal. Supported workflows process locally in the browser and enforce bounded size and complexity limits. For Create ZIP, verify that the generated format preserves the properties that matter for your use case. For important data, compare a representative sample and confirm that format, content and quality meet the actual requirement before replacing the source file. Also open the generated file in the destination application when compatibility, colour, transparency, layout or compression matters.

What it does

MakeFileWork creates a standards-compatible ZIP containing your selected files. It stores CRC-32 integrity values and verifies the ZIP directory before download.

Safety limits

Up to 100 files, 60 MB total input and 25 MB per file. Unsafe filename characters are normalized and duplicate names are made unique.

How the ZIP is verified

After packaging, MakeFileWork reopens the stored ZIP, checks each CRC32 value and compares every output file byte with the selected source. A matching ZIP signature alone is not considered sufficient proof. ZIP store mode does not compress file contents.

Local processing

The files are read and packaged in your browser. ZIP store mode packages files reliably but does not reduce their size.

Unicode lookalikes and encoded filenames

A name such as ＣＯＮ.txt looks different from CON.txt, but Unicode compatibility normalization can turn it into a Windows device name. Similarly, report：2026.csv can become a filename containing a forbidden colon, and folder/%3a/data.csv may change when another program decodes percent escapes. MakeFileWork rejects these ambiguous names before packaging rather than changing them without permission. Rename the source to a simple name such as report-2026.csv and retry; the file bytes are not altered.

Cross-platform filename safety

Names that remain unsafe across operating systems (such as reserved device names or ambiguous trailing dots) are rejected before packaging. Case-insensitive and Unicode-equivalent duplicates receive distinct numbered names, and the output is re-opened for byte-for-byte verification.

Practical example: sending a project folder

Suppose you need to send invoice.csv, notes.txt and photo.png together. Select those three files, create the ZIP, and check the downloaded archive in Inspect archives. The ZIP preserves each file’s bytes but does not preserve the original folder tree or make the package smaller.

Duplicate names and invalid paths

Two files named report.csv are saved under distinct names, such as report.csv and report-2.csv. Reserved device names, unsafe trailing dots, path traversal and ambiguous Unicode names are rejected rather than silently overwritten. If the tool refuses a filename, rename that source file before retrying.

ZIP creation versus repair or inspection

Creating a ZIP packages valid input files; it does not repair a damaged ZIP or scan for malware. To check an existing archive’s headers, CRC32 and suspicious paths, use archive inspection. For a broken file, start with file diagnosis.