Choose a single output format for mixed input files
When a batch contains both JPEG and PNG files, “JPG or PNG” is ambiguous. Specify “convert to PNG” or “output JPG” if you want every file in the same format. Without an explicit format, the tool preserves each compatible input format when possible.
Safe filenames and an auditable ZIP
Output names receive deterministic numeric prefixes so duplicate input names do not collide inside the archive. Unsafe path characters are replaced. The ZIP includes a JSON report for each input; a partial failure is identified separately from successfully processed images.
What happens when an image fails?
A corrupted image, unsupported decoder or impossible pixel/byte requirement is recorded as a failure. Other valid files can still be included. If every image fails, the workflow does not offer an empty success ZIP.
Limits and cancellation
Select at most 50 images totaling 60 MB. Editing the requirements or selecting new files invalidates the previous output; an in-progress image encode may finish internally, but its stale result cannot be published as the new batch.
Related tools
For a portal rejection affecting only one image, start with upload requirement fixer. For a single-file target size, see compress image.
Verified images, not just a finished progress bar
Each image is checked after encoding: the actual JPEG, PNG or WebP signature, pixel dimensions, container structure and SHA-256 fingerprint must agree with the output. The ZIP is reopened and each file hash is compared with its JSON evidence entry. This detects mismatched encoders and changed downloads, but it does not certify visual quality or color fidelity.
Cancel, inspect failures and download separately
Drag up to 50 images or select them individually; folders are not accepted. Cancel between files to prevent publishing an incomplete result. When some images fail, successful images remain available for individual download, while the ZIP records the rejection reasons. If every image fails, the ZIP contains only the JSON evidence report, never a false successful image.
Reopen a previous batch without processing it again
Import an image ZIP created by this tool to recheck CRC32, each output SHA-256, the image signature and dimensions against the embedded JSON report. You can provide an independently saved SHA-256 to confirm you selected the intended archive. Without that independent hash, the checks establish internal consistency, not authenticity.
Retry only rejected originals
After importing or processing a partial batch, select the original rejected images again. The tool matches their names, byte sizes and SHA-256 values; changed or ambiguous files are refused. Accepted images are preserved byte for byte, while only the rejected selection is reprocessed with the new requirements. Each attempt is recorded in the report, and downloads are verified again.
Inspect images before spending time on conversion
The source inspection reads each image signature, validates PNG CRC32, WebP chunks or JPEG scan envelopes, checks declared MIME and filename extensions, and estimates decoded pixel memory. A rejected source stays visible in the batch report instead of silently disappearing. The inspection JSON and spreadsheet-safe CSV include SHA-256 for each original; rechecking those hashes before conversion prevents a changed original from passing under an old inspection. HEIC requires an available local decoder and is not certified by header inspection alone.