H.264 MP4 input
The most reliable source choice on common desktop and mobile browsers.
Choose a cover frame and a short motion window from a browser-playable MP4. Download the paired still, motion clip, manifest, and ZIP without uploading the source.
A native Apple Live Photo relies on paired media plus platform-specific metadata. A web page cannot install that pair directly into the iOS Photos database, but it can create the cover image and nearby motion asset for an import workflow.
FramesFromVideo keeps the process honest: it produces a Live Photo-style bundle and documents the source, selected key frame, duration, and generated filenames in a manifest.

Use a short H.264 MP4 for the broadest browser compatibility.
Choose a local file and wait for the duration and dimensions.
Move the key frame slider to the strongest still image.
Choose a short clip and let Auto select a supported encoder.
Save the ZIP containing still, motion, manifest, and readme files.
The source must decode and the browser must expose a MediaRecorder video encoder.
The most reliable source choice on common desktop and mobile browsers.
Depends on browser, operating system, and device codec support.
Used when the browser exposes a compatible MP4 MediaRecorder type.
Auto may choose WebM when MP4 recording is unavailable.
Short motion feels focused and is faster to render.
The cover should be sharp and meaningful even before motion plays.
It avoids requesting an encoder the browser cannot provide.
Pairing behavior differs between devices and third-party photo applications.
The output is a paired asset bundle, not an automatic native iPhone Photos entry.
You can create the still and motion assets online; native import depends on the target app.
No. The file is decoded and recorded locally.
Yes. Use the key frame slider.
Auto uses WebM when the browser does not expose MP4 recording.
A still image, motion clip, JSON manifest, and readme.