What's actually inside a .livp file?
A .livp file looks like a single photo, but it is really a small archive. Technically it is a ZIP container that Apple uses to bundle the two pieces that make up a Live Photo: a HEIC still image (the “key photo” you see in your camera roll) and a short MOV video clip (roughly 1.5 seconds before and after you pressed the shutter). When you tap and hold a Live Photo on an iPhone and watch it move, you are watching that MOV. When you just glance at it, you are looking at the HEIC.
Converting LIVP to JPG means reaching into that ZIP, pulling out only the HEIC still frame, and re-encoding it as a JPG. You are deliberately throwing away the motion and keeping the single best frame — exactly what you want when you need a normal, shareable photo. Because the HEIC inside is the full-resolution capture, the JPG you get out is the same quality as any regular iPhone photo, not a blurry video screenshot.
Why convert a Live Photo to a plain JPG at all?
Most of the time you don't need the motion. You need a photo you can email, print, upload to a marketplace listing, attach to a form, or set as a profile picture. A .livp file fails at every one of those because the receiving system has no idea it is secretly an Apple archive — it either rejects the upload or shows a broken thumbnail. A JPG just works, everywhere, with no plugin and no explanation needed.
There is also a size and tidiness benefit. The MOV video inside a Live Photo is often the largest part of the package. If all you want is the picture, carrying the video around is dead weight — it bloats your storage and your backups. Extracting the still as a JPG gives you a clean, lightweight file with nothing attached, which is ideal for archiving the photos you actually care about while leaving the motion behind.
LIVP to JPG vs renaming to .zip — which is better?
Because a .livp is a ZIP underneath, a popular manual trick is to rename the file to .zip and open it with 7-Zip or WinRAR. That works, and it will show you a HEIC file inside. But it leaves you with a new problem: you now have a HEIC, which Windows and Android still struggle to open. You have traded one un-openable format for another, and you still need a second tool to turn that HEIC into a JPG.
This converter collapses both steps into one. It unpacks the LIVP, finds the HEIC still, and decodes that HEIC straight to JPG in a single pass — so you go from an unreadable .livp to a universally readable .jpg without ever touching a file extension or installing archive software. For a single file the difference is convenience; for a batch of fifty Live Photos, the manual route is genuinely painful and this is the obvious choice.
Will the JPG keep the full quality of the original?
Yes, for any normal use. The still inside a LIVP is the full-resolution HEIC your iPhone captured — typically 12 megapixels on most models, more on Pro devices. We decode that original HEIC and export JPG at 92% quality, which is visually indistinguishable from the source on a phone, a monitor, or a print. You are not extracting a low-res preview or a frame grab from the video; you are extracting the actual photo.
The one honest caveat is that JPG is a lossy format, so the output is mathematically not byte-for-byte identical to the HEIC, and the JPG file may be a little larger than the HEIC was (HEIC compresses more efficiently). If you specifically need a lossless copy for heavy editing or archival, extract to PNG instead. For sharing, uploading, and printing — which is why almost everyone converts LIVP to JPG — 92% JPG is exactly right.
Converting a whole album of Live Photos at once
If your iPhone has its camera set to keep Live Photos on, an entire trip or event can be hundreds of .livp packages once exported. Doing those one at a time would be miserable. Drop the whole set in at once: each .livp is unpacked, its HEIC still is pulled out and converted to JPG locally, and you can download the results individually or as a single ZIP archive.
Everything runs on your own device with WebAssembly, so there is no upload queue and no per-file server limit — batch speed is bound only by your hardware, and a modern laptop or phone chews through a large album in seconds. Nothing is sent anywhere, which means even a folder of personal family photos stays entirely on your machine.