Why batch conversion exists — the one-at-a-time problem
Apple's Photos app can convert a Live Photo, but only one at a time, and only through a fiddly path: open the photo, tap share or duplicate, choose a format, save, repeat. That's tolerable for a single image. It becomes genuinely painful the moment you have a folder of forty vacation Live Photos to prepare for a print order, a hundred product shots to flatten for a website, or an entire trip's worth of moments to back up to a Windows PC. Doing that one by one can eat an afternoon.
Batch conversion collapses all of that into a single action. You drop the whole pile in, choose what you want out, and walk away while the queue churns through every file automatically. Instead of dozens of repetitive taps, it's one drag, one click, and one download. For anyone who shoots a lot of Live Photos, the batch workflow is the difference between a chore and a non-event.
Mixed inputs, multiple outputs
Real camera rolls are messy, so the batch converter is built to handle a mix. You can drop .livp Live Photo packages, standalone .heic stills, .mov motion clips, and even ordinary .jpg files all into the same queue. Each file is auto-detected, so you don't have to sort them first — the tool recognizes what each one is and offers the output formats that make sense for it.
Outputs are just as flexible. For each file, or across the whole batch, you can target JPG for universal sharing, PNG for lossless editing masters, WebP for fast-loading web images, GIF for animated loops, or MP4 for the full motion clip. Need every Live Photo as both a shareable JPG and a web-ready WebP? Select both and the batch produces each version. This turns one upload of raw iPhone files into exactly the set of deliverables a project needs.
How a large queue actually processes
When you start a batch, each file enters a queue and is processed in turn, with the tool taking advantage of your device's CPU to convert in parallel where it can. The motion is decoded, the still extracted, and each requested format encoded — all using WebAssembly running inside the browser tab. A live progress view shows you which files are done, which are in flight, and which are waiting, so a big job is never a black box.
Because the work runs on your own hardware rather than a shared server, there is no queue behind other users and no per-job rate limit. Speed scales with your machine: a modern laptop or phone rips through dozens of files in seconds to a couple of minutes depending on the output formats (GIF and MP4 take longer than a still JPG). The only real ceiling is your device's memory, which is why there's no artificial cap on file count.
Why everything ends up in a single ZIP
Downloading thirty separate files one click at a time would defeat the purpose of batching, and most browsers would interrupt you with a “this site wants to download multiple files” prompt anyway. So once the queue finishes, the batch converter bundles all the results into one ZIP archive that you download in a single action. Unzip it and your converted images and clips are right there, neatly together.
The ZIP also keeps things organized. Your outputs arrive grouped and clearly named, so a batch destined for a print shop, a client handoff, or a backup folder stays tidy instead of scattering across your Downloads directory. If you only want a couple of files, you can still grab those individually — the ZIP is there for when volume makes it worth it.
Privacy at scale — even 100 files never touch a server
The privacy guarantee doesn't weaken just because you're converting in bulk. Every single file in the batch is opened, decoded, and re-encoded entirely inside your browser. Whether you drop in five files or five hundred, none of them is ever uploaded — there is no server in the loop receiving your images, which means we physically cannot see, store, scan, or leak them.
That local-first design is also what makes the no-limit promise honest. Many online batch tools cap file count or total size precisely because they're paying to upload and process your data on their servers. Here, your own device does the work, so the only limits are your hardware's, and the tool keeps running offline once the page has loaded. No account, no email, no watermark on any of the output.