A practical workflow for a batch of 30 images

Separate source masters from delivery files

Create a source folder that remains untouched and a separate location for the optimized delivery files. Use filenames that identify the product, page or asset rather than a sequence you will have to reconstruct later. A batch of thirty similarly named images is harder to review than a batch whose names already communicate their purpose.

If the job contains unrelated requirements, divide it before uploading. Transparent logos, editorial photographs and screenshots may need different formats or dimensions. One set of settings can be convenient, but convenience does not make it suitable for every asset. Group images by the output they need and keep exceptions visible.

Know the current limits before selecting the folder

The current PikoZip image toolkit accepts up to 30 images in one batch, up to 10 MiB per input file and up to 24 million decoded pixels per image. Ten MiB means 10,485,760 bytes. These limits describe the input and batch; they are not an assurance that every output will fit a particular website upload limit.

A compact file can still decode into a very large image. File bytes and pixel dimensions are separate constraints, so check both when preparing unusually large exports. Unsupported, empty, corrupt or animated files can also be rejected. Read the specific notice or row error instead of assuming that every failed item needs the same fix.

Find the settings with one representative image

Choose an image that contains the difficult details in the collection: soft shadows, fine text, a transparent edge or a textured product surface. Select the required output format and maximum width, process it and inspect the comparison. This small trial is more useful than discovering an unsuitable setting after thirty files finish.

PikoZip shows real output bytes and dimensions. Use those measurements together with the preview. A pleasing percentage alone does not tell you whether the result is suitable for a large product zoom or a small thumbnail. Once the representative export is acceptable, use the same deliberate settings for similar assets.

Review the batch as a collection of individual results

Wait for the batch to finish and read the summary, then check rows that report an error, a larger conversion or an unmet target. A single exception should not disappear inside a successful total. Keep filenames visible while reviewing, and compare images with important edges rather than relying only on the first row.

A same-format, same-dimension source may be retained when it is smaller than the encoded result. Explicit conversions may grow because their purpose is to produce the requested format. Both are explained by the result. Reprocess with new settings only when there is a clear reason, using the original source as the starting point.

Download, extract and confirm before clearing

Download an individual result when you need to review it in another application, or use Download ZIP for the completed collection. In supporting browsers, selecting a folder preserves relative paths in the ZIP. When different inputs would create the same output filename in one folder, a suffix distinguishes them rather than overwriting another result.

Open the downloaded archive and check its contents before replacing a published collection. Confirm a few files in the actual destination, including a mobile layout if they are for a website. PikoZip does not overwrite your local originals or automatically replace images in a CMS. Those final publishing choices remain yours.

Treat each batch as a working session

Processing happens on your device. Encoding large images, trying Smart mode or exporting AVIF can take longer than a small fixed-format batch. A busy device may benefit from a smaller group. Avoid treating a long encode as evidence that image bytes have been sent to a processing server.

After verifying your downloads, clear the batch before adding the next group. Clearing stops the current processing worker and removes this page’s working results. A page refresh does not provide a saved image gallery, so download what you need before leaving. Files already downloaded remain in your own download location.

What happens when a batch contains a problem file?

A successful batch summary should not hide rejected files. These cases are covered by PikoZip regression checks. The visible notice explains skipped inputs; a source that fails during decoding should leave the queue able to continue with the next valid image. The free file-size limit labelled 10 MB is 10 MiB: 10,485,760 bytes.

Check folder paths and filename collisions

Folder upload preserves relative folders where the browser supports directory selection. ZIP names are sanitized and path traversal segments are removed. When outputs would have the same name in one folder, a numeric suffix keeps the files distinct. Extract the archive and review a few results before replacing production assets.

Clearing or leaving the tool cancels work and suppresses late ZIP downloads. A prepared batch is not an online gallery: download it before refreshing or leaving. These lifecycle behaviors are checked separately from encoding quality, so good compression does not conceal a broken delivery flow.