ZIP for Form Upload — Clean ZIP for Portals

This tool exists for one recurring frustration: an online upload form rejects your ZIP and gives no useful reason. Government and tax portals, university and school submission systems, job application uploads, tender sites, and bank KYC forms tend to enforce strict, undocumented rules — a hard size cap, no spaces or special characters in filenames, no hidden system files, and no deep folder nesting. This tool rebuilds your archive to satisfy those common requirements so the upload goes through on the first try.

Concretely, it fits document-submission work rather than developer or media archiving. Typical cases are bundling scanned PDFs and photos for a portal that allows a single ZIP, preparing a flat set of supporting documents for an application form, or assembling GST/tax or KYC files that a bank form expects under a few megabytes. If your goal is sharing source code, delivering work to a client, or staying under an email attachment limit, FormatOS has separate tools better suited to those.

Everything runs in your browser. The files you drop in are processed locally with JavaScript; nothing is sent to a server and nothing persists once you close the tab. That matters here because the documents involved are often personal or financial.

The flow is: drop in loose files (or a ZIP whose contents you want re-packaged), pick a target size, optionally adjust filename handling, then click Create upload-ready ZIP. The output downloads automatically as a single .zip, and a plain-text upload checklist is available as a separate download for your records.

During processing the tool flattens the folder structure into a single level (no nesting), strips system junk that portals dislike — .DS_Store, __MACOSX, Thumbs.db, desktop.ini — and removes hidden dotfiles. Filenames are sanitized: special characters are removed, spaces become hyphens, names longer than 60 characters are shortened, and lowercase conversion is optional. Size targets are 1, 2, 5, 10, or 20 MB, or a custom value you type in. Compression runs at the maximum level. After rebuilding, it reports whether the result is under your chosen limit.

What it does not do: it will not split an oversized archive, will not password-protect or encrypt the ZIP, and will not predict a specific portal's private rules. It also cannot re-compress already-compressed content into something dramatically smaller — see below.

The biggest misconception is that maximum compression always shrinks a ZIP. JPGs, PNGs, MP4s, MP3s, and PDFs are already compressed, so zipping them yields little or no size reduction — the tool warns you when such files are present. If a checklist shows the size check failing, the archive itself is genuinely too big; the fix is removing or downsizing files, or splitting the archive, not re-running this tool.

The size and filename targets are sensible defaults, not your portal's actual rules. The presets are guesses at common limits; your form may demand 2 MB when you assumed 10, or forbid uppercase, or want a particular naming pattern. Read the portal's instructions and set the target and filename options to match. Also note that flattening removes folders entirely — if a form expects files inside a named subfolder, this tool is the wrong choice.

Two more practical traps: the output filename defaults to documents.zip, so rename it to whatever the portal expects before or after download; and the renamed-files count in the checklist means your filenames changed, so confirm those new names still make sense to a human reviewer.

Start with the on-screen checklist: confirm the size row passes against the exact limit your portal stated, that hidden system files were removed, and that filenames were cleaned. Then open the downloaded ZIP and look inside — verify every document you intended is present, that nothing was dropped, and that the flattened, renamed files are still recognizable. Check that the .zip filename itself matches what the form asks for.

Open at least one or two files from the archive to confirm they are intact and not truncated, especially scans and multi-page PDFs. If filenames were lowercased or shortened, make sure a reviewer can still tell which document is which; rename anything ambiguous and re-run if needed. Keep the text checklist alongside your submission as a simple record of what you sent.

For official, financial, or legal submissions — tax filings, bank KYC, court or tender documents — treat this tool as preparation, not verification. It checks size and filename hygiene, not whether your content meets the authority's requirements. Manually confirm the document set, file integrity, and the portal's stated rules yourself, and where possible do a test upload before the deadline.