Convert WebP to ZIP

No — an archive stores each WebP 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.

Into a document, no: only the first frame is placed, because a page has nowhere to put the remaining ones and no mechanism to play them. Into an archive, yes and entirely, because the file is stored whole and never opened. If the motion is the point and the destination is a document, either export the frames you actually want as separate images, or link out to the animation and place a representative frame in the page.

Barely smaller, and that is expected. A WebP 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. WebP offers both lossy and lossless modes, with alpha transparency and animation available in either.

Because the page is not permanent and the file is. A WebP is a web-delivery format, so the copy in front of you is usually the only one outside somebody else's server, and servers get reorganised without warning. An archive keeps the set together with its filenames, which is most of what you need to work out later where each file came from — and it is worth saving the source addresses in a text file inside the same archive while you still remember them. That is the part nobody does and everybody later wants. WebP is typically 25-35% smaller than an equivalent JPG and far smaller than an animated GIF, with universal browser support since 2020.

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.

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.