Get Live Photo

What is GetLivePhoto?

GetLivePhoto (https://getlivephoto.com/) is a privacy-first, browser-based utility designed to convert standard video clips (MP4, MOV, WebM) into native Apple iOS Live Photos.

Unlike traditional mobile apps that lock basic features behind expensive subscriptions and intrusive ads, or cloud-based web converters that require you to upload personal videos to remote servers, GetLivePhoto runs 100% locally in your browser. Your private videos and memories never leave your device.

Who is it for?

• iPhone & iPad Users: Anyone who wants to turn memorable video clips, memes, or animations into dynamic Live Photo lock-screen wallpapers.
• Content Creators & Designers: Creators looking to share interactive Live Photos on social platforms (such as Xiaohongshu/RED or iOS ecosystems) without losing quality.
• Privacy-Conscious Users: People who want a quick format conversion tool without exposing personal media to third-party cloud storage.

Tech Stack & Architecture

To achieve zero-server video processing while keeping costs at a minimum, the project relies heavily on modern web capabilities:

• Frontend Framework: Next.js / React with Tailwind CSS for a clean, responsive, and minimalist UI across both desktop and mobile browsers.
• Media Processing: Powered by WebAssembly (FFmpeg.wasm), allowing complex video transcoding, frame extraction, and container muxing to happen entirely on the client side.
• Metadata Injection: Custom client-side binary/EXIF manipulation to pair the image and video assets according to Apple's proprietary specifications.

Challenges & Pitfalls Overcome (踩过的坑)

Building a pure client-side Live Photo generator came with several tricky technical hurdles:

1. Cracking the Apple Live Photo Specification:
   An iOS Live Photo isn't a single file—it is actually a pair of files consisting of a still image (.JPG or .HEIC) and a short QuickTime video (.MOV). For iOS Photos to recognize and merge them as a single Live Photo, both files must share an identical, specifically formatted ContentIdentifier UUID embedded deep inside the image's EXIF/MakerNote metadata and the video's QuickTime metadata atoms. Getting this metadata injection right purely in JavaScript/Wasm took extensive reverse-engineering and testing.

2. Mobile Browser Memory Limits & COOP/COEP Headers:
   Running FFmpeg.wasm inside mobile Safari is notoriously strict. Multi-threaded WebAssembly requires SharedArrayBuffer, which in turn demands strict Cross-Origin Opener Policy (COOP) and Cross-Origin Embedder Policy (COEP) headers. Furthermore, processing high-resolution 4K videos can easily trigger out-of-memory (OOM) crashes in mobile browsers, requiring careful memory cleanup and stream buffer optimization after each conversion.

3. Seamless iOS Saving Workflow:
   Even after generating the correct .JPG + .MOV pair in the browser, simply downloading them via mobile Safari often results in iOS treating them as two separate files instead of merging them into a single Live Photo. Designing an intuitive export and saving workflow so that iPhone users can effortlessly import the merged result directly into their Camera Roll was one of the most important UX refinements.