Submission ZIP package

Package checked materials with a manifest and reports

Create a ZIP of original materials plus a manifest and JSON/Markdown preflight reports. Use a free account for standard names or Pro for custom naming.

A completed archive is not evidence that every file meets the rules. The package checks uploaded bytes and includes a report for each input, making failed requirements visible to people and agents.

Open this tool

Choose a file

Local checks stay in your browser. Basic image and PDF processing works without login and uploads files only when you run it.

Drop or select an image or PDFJPG, PNG, WebP, GIF, PDF

Preflight acceptance mode

Server conversions use this mode to decide whether output is accepted.

Maximum file size (bytes)

Default: 200,000 bytes (about 200KB)

Maximum pages (optional)

PDF page count is checked after server inspection.

Require consistent PDF page sizesChecks every page width and height after server inspection.

Result

Choose a file to see its actual facts

Your preflight report will appear here.

How it works

Sign in, add your materials and choose the desired order and package name.
Apply a rule and choose strict mode or best-effort. The default naming template works with a free account.
Create the ZIP and review manifest.json and the reports before submitting.

Capabilities and limits

Free accounts allow up to 10 inputs per job; Pro allows up to 100, with the same 25 MB combined engine limit.
Custom naming uses {name}, {index}, {type}, {date} and {ext}; path traversal and unsafe names are rejected.
Files in the package are the original inputs. Convert or compress them first if they need changes.

Questions

What happens if one material fails preflight?

Strict mode refuses the package and returns per-file failures. Best-effort creates the archive with explicit warnings and reports; it does not certify that the materials will be accepted.