iPhone Live Photos vs Google & Samsung Motion Photos

If you've ever AirDropped a "living" photo to an Android friend and watched it arrive as a flat still — or received a Samsung Motion Photo that your iPhone refuses to animate — you've hit the core problem: Apple Live Photos and Google/Samsung Motion Photos solve the same idea with incompatible plumbing. Both capture a moment of motion plus audio around a still frame, but they store it in fundamentally different ways, which is exactly why they don't travel well between ecosystems. This guide breaks down how each format actually works, where compatibility breaks, and the one reliable way to make either one play everywhere.

The short version: same concept, opposite engineering

A Live Photo and a Motion Photo both pair a high-resolution still with a short clip (roughly 1.5 seconds before and after the shutter) plus sound. The difference is structural. Apple keeps the still and the video as two separate files that the OS links together. Google and Samsung hide a video inside a single image file, so it looks like an ordinary photo until software knows to look deeper.

That one decision — two files vs. one file with a hidden payload — explains almost every compatibility headache below.

How each format is stored

Apple Live Photo: a paired HEIC + MOV (or a .livp ZIP)

On an iPhone, a Live Photo is really two assets the Photos app treats as one:

• A still frame, normally a HEIC (HEVC-intra) image, sometimes JPEG.
• A short HEVC .MOV video clip, around 3 seconds with audio.

Inside iOS these share a metadata identifier so Photos knows they belong together. When you export or share a Live Photo as a single file, iOS bundles them into a .livp — which is simply a ZIP container holding the still and the .MOV side by side. If you rename a .livp to .zip and unzip it, you'll see both files. For a deeper breakdown of this container and its metadata, see our Live Photo format reference.

Google/Samsung Motion Photo: an MP4 embedded inside a JPG

Motion Photos take the opposite approach. The file is a normal, fully-valid JPEG that any viewer can open as a static image — but appended after the JPEG data is a complete MP4 video stream. Metadata (Google's MotionPhoto/MicroVideo XMP tags, or Samsung's trailer markers) tells compatible apps where the video begins inside the file.

This is clever: a Motion Photo degrades gracefully. Send it anywhere and you at least get a working still image. The trade-off is that the motion is invisible to anything that doesn't specifically parse Google's or Samsung's embedding scheme.

	Apple Live Photo	Google/Samsung Motion Photo
File structure	Two files (still + video), or a .livp ZIP holding both	One JPEG with an MP4 appended inside it
Still format	HEIC (HEVC-intra), sometimes JPEG	JPEG
Video codec	HEVC in .MOV	H.264/HEVC in MP4
Clip length	~3s (1.5s before + after)	~3s (varies by device)
Audio	Yes	Yes
Opens as a plain photo anywhere?	No (HEIC needs a codec; .livp needs an unzipper)	Yes (valid JPEG)
Motion visible cross-platform?	No	No (needs Google/Samsung parsing)

Are Live Photos and Motion Photos cross-platform compatible?

No — not as living images. The still frame can usually be salvaged on the other platform, but the motion almost never survives the trip. Apple and Google use different file structures, different metadata, and (for Apple) the HEIC format that many non-Apple systems can't even decode without an added codec.

A few specific failure points worth knowing:

• HEIC on Windows: Windows has no HEIC/HEVC codec by default. Until you install the HEVC/HEIF extensions, even the still frame of a Live Photo may not open. (If you're stuck here, you can convert HEIC to JPG in your browser instead.)
• .livp anywhere but iOS: Android, Windows, and most web apps see a .livp as an unknown ZIP. They won't animate it; at best you extract the still and video manually.
• Motion Photos on iPhone: iOS shows the embedded JPEG fine but ignores the appended MP4, so the photo just sits still.

📸 [LivePhotoKit: insert your own screenshot — same Motion Photo opening flat on an iPhone vs. animating on a Pixel]

Can you send a Live Photo to Android (or a Motion Photo to iPhone)?

You can send the file, but the receiving platform won't replay the motion natively. AirDrop is iPhone-to-iPhone; cross-platform you're using messaging apps, email, or cloud links — and most of those strip the live component during transfer, delivering only a still or a re-encoded clip.

Live Photo → Android

When you share a Live Photo through a non-Apple channel, iOS typically hands over just the HEIC/JPEG still or a flattened version. The Android device has no concept of Apple's paired-file linkage, so even if both files arrive, nothing stitches them back into a living image. The dependable workaround is to convert the motion into a standard video before sending — covered in the next section.

Motion Photo → iPhone

Send a Samsung or Pixel Motion Photo to an iPhone and it arrives as a static JPEG. The MP4 is still physically inside the file, but iOS doesn't read Google's embedding, so it never animates. To get it living on iOS you'd need to extract the embedded MP4 and re-author it as a true Live Photo — and importantly, actually installing a working Live Photo into the iOS photo library requires iOS itself. A browser or PWA can generate the paired files, but it can't register them as a system Live Photo. If you do extract the MP4, our video-to-Live-Photo tool can build the paired files for you to import on an iPhone.

How to convert either format to a universal video

This is the genuinely reliable answer for cross-platform sharing: stop fighting the formats and turn the motion into a plain MP4/H.264 video that plays on every phone, browser, and chat app.

• From an Apple Live Photo: drop the .livp (or the HEIC + MOV pair) into our Live Photo to video converter. It runs entirely in your browser using FFmpeg compiled to WebAssembly — nothing is uploaded, there's no watermark, and you can batch multiple files at once. You can verify the no-upload claim yourself in your browser's DevTools Network tab.
• From a Motion Photo: the embedded MP4 needs to be split out of the JPEG first. Some tools can read the trailer directly; otherwise extract the MP4, then run it through a standard converter to normalize the codec and orientation.

A universal video also sidesteps the HEIC problem entirely — recipients don't need any special codec, and the file behaves predictably in social uploads that would otherwise re-compress or reject HEIC.

What you lose by flattening to video

Honesty matters here: a flat MP4 is not a Live Photo. You lose the still/motion duality, the tap-and-hold playback, and the ability to set it as a Live wallpaper. If your goal is an animated share, a video (or a GIF) is perfect. If your goal is a working Live Photo on someone's iPhone, video is the wrong target — you need the paired-file route and an iOS device to finish the install.

Bottom line

Live Photos and Motion Photos are the same idea built on opposite foundations: Apple links two files (and zips them into .livp), while Google and Samsung smuggle an MP4 inside a JPEG. Neither replays its motion natively on the other platform, and HEIC adds a decoding wrinkle on Windows and some browsers. When you need a moment to play everywhere, converting to a standard video is the one move that works in every direction — and doing it in-browser keeps your photos on your own device.