Short answer: not reliably from start to finish. A modern browser can read a video, let you choose a short segment and cover frame, and even prepare the still-and-motion files used by a Live Photo. But a web page does not complete Liveify's native save into your Apple Photos library. In Liveify's current workflow, the website is a private preview tool; the iPhone app performs the actual video-to-Live-Photo conversion and saves the result through Apple's Photos framework. The video conversion still happens on your device, not in the cloud.
That distinction matters because a Live Photo is not simply a video with a different filename.
What is a “real” Live Photo?
Apple's Photos framework represents a Live Photo with separate resources. One is the still photo; another is the pairedVideo, which Apple defines as the original video component of the Live Photo asset. Apple's complete PHAssetResourceType list shows both the photo and paired-video roles.
In practical terms, a valid Live Photo needs three things to agree:
| Component | What it does | What is not enough |
|---|---|---|
| Still image | Becomes the photo and cover frame | An unrelated JPG beside a video |
| Motion file | Holds the short moving moment, usually as a MOV | Renaming an MP4 to .mov |
| Pairing metadata | Links the still and motion as one asset and marks the key-photo moment | Matching filenames alone |
The useful test is not “Do I have two files?” It is “Does Apple Photos recognize one asset as a Live Photo and play its motion?”
What can a browser do without an app?
A browser can do a surprising amount locally. It can:
- Read a video selected from your device.
- Decode frames for a filmstrip and preview.
- Let you choose a short motion window and a cover frame.
- Re-encode media and write metadata using browser-side code.
- Download ordinary files without uploading the source video to a server.
The browser does not, however, provide the same native Photos-library save operation that an iPhone app gets through PhotoKit. Preparing compatible files and committing one recognized Live Photo to Photos are two different stages.
This is why “without an app” can mean two different things:
- Without a desktop editor or cloud converter: yes. A browser can handle the preparation locally.
- Without any native iPhone step: not as a reliable end-to-end Liveify workflow today.
What the current Liveify website actually does
The current Liveify Video to Live Photo tool keeps the browser stage deliberately narrow:
- You choose a browser-readable video of up to 10 seconds and 100 MB.
- Liveify analyzes frames locally and shows a looping preview.
- You choose a 1-to-3-second segment and place the cover-photo marker.
- The site directs you to Liveify on iPhone for creation and saving.
- You select the original video again in the app. The web selection is not transferred to the app.
That last point is intentional and should be visible before you start: the website currently does not download a finished Live Photo ZIP for the Video to Live Photo flow. It is a private planning and preview step.
This also means some older descriptions of “download a JPG and MOV, then AirDrop both” do not describe the current web interaction. A manual paired-file workflow may be technically possible, but it is not the workflow Liveify currently exposes or relies on.
How Liveify creates the Live Photo on iPhone
Once you choose the source video in the iPhone app, the native workflow can complete the steps the website leaves open.
Liveify's current on-device pipeline:
- Trims the video to the selected motion window.
- Extracts a still image at the chosen cover time.
- Creates a shared content identifier for the still and motion.
- Writes the key-photo time into the motion metadata.
- Produces a still image and H.264 MOV as a linked pair.
- Asks Apple Photos to create one asset with a
.photoresource and a.pairedVideoresource.
The native save is the decisive difference. Instead of hoping Photos reconstructs a relationship from two manually transferred files, the app explicitly submits the two resources as one Live Photo asset.
Does Liveify upload the video?
No. The standard Video to Live Photo workflow is local on both surfaces:
- The website reads the selected video in your browser for its preview.
- The iPhone app trims, extracts, packages, and saves the video on the device.
- The website does not transfer your selected clip or cover position to the app, so you choose the original video again.
This statement applies to Liveify's format-conversion tools. The separate AI Photo to Live Photo tool is different: it sends a selected still image to an AI service to generate new motion. Liveify's privacy policy describes that exception explicitly.
Browser preview vs. native conversion
| Question | Browser preview | Liveify iPhone app |
|---|---|---|
| Can it read your source video locally? | Yes | Yes |
| Can it choose a short segment and cover? | Yes, for preview | Yes, for the actual result |
| Does it upload a standard video conversion? | No | No |
| Does the current flow create a downloadable Live Photo? | No | Yes |
| Does it save directly into Apple Photos? | No | Yes, after Photos permission |
| Is the browser selection handed to the app? | No | You reselect the original video |
If your goal is to test which moment looks best, the website is useful. If your goal is to finish with one Live Photo inside Photos, use the native conversion.
How to make the result more reliable
The file format is only half the job. Source choices affect whether the final Live Photo feels natural.
Keep the motion focused
Three seconds is the standard target in Liveify. Choose a moment with one clear action: a smile, a wave, a pet looking toward the camera, or a small camera move. A long scene with several cuts usually feels like a tiny video rather than a photograph that comes alive.
Choose the cover deliberately
The cover is the frame people see before the motion begins. Pick a sharp frame with a readable subject. Avoid the exact start or end when possible; a frame inside the selected motion window gives the animation room on both sides.
Preserve the original video
The web preview does not transfer its edit to the app. Keep the original video available on the iPhone, then reproduce the segment and cover choice in the app.
Verify the asset in Photos
After saving, check all of the following:
- Photos shows one item rather than a separate still and video.
- The item is identified as a Live Photo.
- Its motion plays in Photos.
- The displayed cover matches the moment you selected.
Wallpaper support is a separate compatibility question. Apple's current Live Photo Lock Screen instructions explain the supported device and system behavior; creating a recognized Live Photo does not override those requirements.
Common misconceptions
“Changing .mp4 to .mov creates a Live Photo”
It does not. A filename extension says what container a file appears to use; it does not add the still image, shared identifier, or key-photo timing that links the resources.
“A MOV file is a Live Photo”
A MOV can be the motion resource, but it is only one component. Apple describes the video as the paired video of a Live Photo asset, not the whole asset by itself.
“If processing is local, there cannot be limits”
Local processing uses your device's memory and CPU. Liveify's current web preview limits inputs to 100 MB and 10 seconds to avoid overloading mobile browsers. “No upload” and “unlimited” are unrelated claims.
“No app means no iPhone is needed”
You can preview the clip in a browser on another platform, but Apple Photos is where the Live Photo ultimately lives. The current Liveify workflow finishes that job in its iPhone app.
“The website sends my chosen edit into the app”
It does not. The website keeps the source and selection in the browser. Open the original video again in Liveify on iPhone and make the final selection there.
Frequently asked questions
Can Safari turn a video into a Live Photo by itself?
Safari can support local media processing, but Liveify's current web flow stops at preview and selection. The Liveify iPhone app performs the final conversion and Photos save.
Do I need a cloud service?
No for Video to Live Photo. The website preview and iPhone conversion are both on-device. The AI Photo to Live Photo feature is the separate, cloud-backed workflow.
Can I start on Windows, Mac, or Android?
You can use a modern browser to inspect a short clip and decide which moment and cover you want. To complete the current Liveify workflow as an Apple Live Photo, move or keep the original video on an iPhone and select it in the app.
What source format should I use?
Use a short video your browser and iPhone can decode reliably. MP4, MOV, and M4V are the clearest choices in the current web interface. The final paired motion created by the iPhone workflow is a MOV.
Will audio be preserved?
Not in Liveify's current Video to Live Photo implementation. The native builder rewrites the motion track as H.264 video but does not add an audio track to the final paired MOV.
Can I use the result as an animated wallpaper?
Possibly, after Photos recognizes it as a Live Photo and if your iPhone and iOS version support Apple's current Live Photo wallpaper behavior. Recognition as a Live Photo is necessary, but it is not the only requirement.
The practical answer
You can use a browser without a desktop conversion app to preview a video and plan the Live Photo moment. But for a reliable result saved as one asset in Apple Photos, Liveify's current workflow still uses its iPhone app. That app performs the conversion locally and asks Photos to save the still and paired video together.
Preview your clip with Liveify's Video to Live Photo tool, then complete the native save on your iPhone.
Verification note
This article reflects Liveify's web and iOS implementation reviewed on August 28, 2026, plus Apple's public Photos resource documentation. We verified the code path that creates the linked still and motion resources and submits them to Photos. We did not treat the older browser ZIP path or a manual AirDrop import as the current product workflow, and we do not claim that manual paired-file import behaves identically across every iOS version.