Convert JPG to ZIP

No — an archive stores each JPG byte for byte, so EXIF, GPS coordinates and colour profiles all travel inside it unchanged and come back out identical when it is unpacked. That is exactly right for a backup and exactly wrong for a file you are sending to someone. Strip the metadata before packing if the ZIP is going anywhere public.

Barely smaller, and that is expected. A JPG already holds its contents in compressed form, so general-purpose compression has almost nothing left to find and the archive lands within a few per cent of the total it was given. Pack it anyway for the reasons that have nothing to do with size: one file to send instead of forty, one download, one checksum, and the folder layout preserved on the way out. JPG is lossy: the image is transformed with a DCT, quantised, and entropy-coded, with a quality knob controlling how much is discarded.

It is, when they need the files themselves. The images arrive at full resolution with their filenames and folders intact, and each one can be pulled out on its own. The alternative — laying them into a single document — is better when the recipient only wants to look through them, because it opens without a step in between; it is worse the moment they need to edit or re-use one, because the picture has been placed into a page rather than handed over. JPG compresses natural photographs superbly and is readable by literally every device, browser and printer in existence.

Free conversions have a size limit per file, set by the type of file, and the page tells you when a file is over it. A paid plan removes that limit, so much larger files can be converted.

Several files in one job need a paid plan. Free use is one file per conversion, one conversion an hour. On a paid plan you can add several files to one job, then download each result on its own or all of them in one ZIP.

Yes — the UI is responsive and the conversion pipeline runs server-side, so mobile devices upload-then-download just like desktops. iOS and Android browser file pickers (camera roll, Files app) work end-to-end.

Chrome, Firefox, Safari (15+), Edge, and Opera. The converter uses standard `<input type="file">` upload — no WebAssembly or PWA dependencies — so even older browsers work.

Yes. Uploaded JPG files are processed on our own servers and are never viewed or shared. Uploads and results are deleted automatically about 24 hours after conversion. See /privacy/ for the full policy.

Disable any pop-up blocker, then click the download button manually. The result link stays active for 24 hours, so if your network fails mid-download, you can re-trigger from the result page without re-uploading the JPG.