Samsung Motion Photo vs. Google Pixel Motion Photo
The practical file-structure differences between Samsung Galaxy and Google Pixel Motion Photos and how device detection should work.
Updated August 11, 2026
Standards-based and legacy layouts
Current Android Motion Photos can use a common XMP container directory for JPEG or a final mpvd box in HEIC and AVIF. Pixel files also exist with the older GCamera MicroVideoOffset field, where the number counts backward from the end of the file to the embedded movie.
Older Samsung Galaxy Motion Photos can use Samsung Extended Format data with a MotionPhoto_Data field and a trailer index. A complete extractor checks both the common Android layout and Samsung’s older structure, then validates the resulting media boxes.
How device-specific detection stays honest
A PXL_ or Samsung-style filename is only a hint. Strong identification comes from consistent Motion Photo structure plus camera Make and Model metadata, or the distinctive Samsung SEF layout. Editing can remove camera metadata while leaving a valid video, so a device-specific tool should sometimes say that extraction succeeded but the device could not be confirmed.
Conversely, a file that says Google or Samsung in Exif is not necessarily a Motion Photo. The video range and track structure still need to pass validation before a download is offered.
Output quality
Extracting the embedded MP4 is normally a byte-for-byte slice, not a video transcode. The output therefore keeps the camera’s resolution, frame rate, audio, and codec. If a service cannot play the extracted codec, that is a compatibility issue rather than evidence that extraction lowered quality.
Keep the original Motion Photo until the MP4 has been played and backed up. Extraction creates a separate video; it does not add motion back to a metadata-stripped still.