Two files can represent one memory
Do not delete a short video just because a nearby image appears to show the same scene. Apple’s Mac Photos export guide says an original-format Live Photo export produces separate still-image and video files. In that route, seeing two files is expected—not evidence of a duplicate.
The useful question is whether you retained the parts and behavior you wanted. A still picture that opens successfully does not demonstrate that the motion survived. Conversely, a video and an image sitting in a folder do not, by themselves, demonstrate that your next photo app will treat them as a single Live Photo.
The concrete export steps below concern Photos on Mac. If you use an iPhone, Windows or iCloud.com, record that route separately; do not assume its files or importer behavior match the Mac example.
Choose what you want to preserve before exporting
| Your goal | What to keep or inspect | What would not establish success |
|---|---|---|
| Original media | The original-format export and all components delivered for each item. | A screenshot, thumbnail or a separately converted sharing copy. |
| A favorite edited appearance | A separate viewing copy showing the crop, color or effect you want; compare it with the source view. | Assuming an unmodified original must look like your latest edit. |
| Motion in a new app | A sample import into the intended app and an observed motion playback result. | Finding a video file, without checking how the destination handles it. |
| A complete Photos library experience | A library-backup plan that also addresses organization and other app-specific information. | A small folder export treated as proof of complete library restoration. |
These goals can coexist. Keep preservation copies and convenience copies distinguishable instead of asking one export to prove everything. A folder called “sharing copies” is a useful organizational label; it is not a reason to remove the originals.
For a library-backup plan rather than a file export, follow Apple’s linked library-backup guidance from its iCloud Photos documentation. That page also explains that iCloud Photos content is not duplicated inside iCloud Backup. Do not count those two labels as independent copies of the same photo collection.
Make a small original-format export on Mac
Pick three non-sensitive Live Photos you recognize, including one whose edited appearance matters to you. Keep the source library intact. Before starting, allow room for the exported media and a second working copy; our space-planning guide explains why the number of thumbnails is not a capacity measurement.
- In Photos on Mac, select the sample and use File → Export → Export Unmodified Original. This is the original-file route described by Apple, not a drag-and-drop test.
- Record the app and macOS versions, selected items, export date and naming options. If you need assigned IPTC information and keywords, Apple provides an Export IPTC as XMP option. Keep any resulting sidecar files with the export.
- Use a new destination folder. If a name collision or replacement prompt appears, stop rather than overwrite an earlier export. Wait for the operation to finish and record any error.
- Keep that delivered set unchanged. Make a working copy for inspection, preserving its folder arrangement. Do not rename individual components or flatten several exports into one folder during this first review.
On iCloud.com, Apple documents separate original-format, high-resolution and compatibility-oriented download choices. Those labels answer different needs; “highest” does not make a choice interchangeable with an unmodified-original export. See the official download instructions for that route. Keep each route’s outputs separate until you understand the differences.
A download is not automatically independent of your everyday storage setup. Identify whether its destination is synchronized and which account or device is needed to retrieve it. The copy-map guide helps you record those dependencies without changing any settings.
Worked example: six files, but one component is missing
Fictional inventory, not an observed Apple export: you choose three Live Photos, labelled A, B and C for this example. Assume this particular original-format export should give you one still and one motion component for each. Excluding sidecars and extra versions, the expected media count is 3 × 2 = 6.
| Item | Files found in this example | Count | Review decision |
|---|---|---|---|
| A | still + motion | 2 | Both components found; opening and destination playback still need checking. |
| B | still | 1 | Motion component not found in this example. Investigate the export route before cleanup. |
| C | still + motion + edited still | 3 | Keep the edited version distinct. It does not replace B’s missing motion component. |
The observed total is also 2 + 1 + 3 = 6. Yet only five of the six expected original components are accounted for. C’s extra edited still conceals B’s missing motion file in the total.
The lesson is not that every export must have twice as many files as thumbnails. Sidecars, other media types and export choices change that arithmetic. It is that a total is not an item-by-item inventory. Record which components belong to each selected item, then investigate gaps. Similar names or adjacent positions are clues, not sufficient proof of a match when several exports are mixed.
If B is unresolved, keep both the source and the current export. Repeating only B into a fresh sample folder can help isolate what that route delivers. Do not “balance” the numbers by deleting an extra file or renaming a different video to match.
Check three different things: presence, contents and behavior
- Presence: identify the source item and record every delivered component’s relative path. If you cannot establish the association, write “unresolved.” Do not invent a pair from filenames alone.
- Contents: open the still in a trusted local viewer and play the video. Check that the scene is the expected one and note whether wanted motion and any expected audio are present. If a viewer cannot read a format, record that limitation; one app’s failure is not a diagnosis of file corruption.
- Destination behavior: if the goal is to use another organizer, test working copies in a separate test library where the app supports that. Record whether it shows one motion-enabled item, two separate media items, or another result. Keep originals untouched if the result is not what you need.
A byte-for-byte copy check answers a fourth, narrower question. You can compare a delivered file with its plain copy using the local file checker, within its 32 MiB limit per file. Compare still to still and video to video—not still to video. A match cannot establish that both files belong to the same Live Photo or that an app will reconstruct it.
Do not rename extensions, convert the only copy or upload private media to an unknown repair website to make a failed test appear successful. Preserve the files and record the actual limitation first.
Keep a component ledger, not a “backup complete” badge
One row per source item
Source item reference and wanted behavior: ____________________
Export route / app version / options: ____________________
Still path and opening result: ____________________
Motion path and playback result: ____________________
Sidecars / extra versions, kept separately identified: ____________________
Association evidence / destination test / unresolved items: ____________________
Download the blank component ledger
This original KYD text template is free to save, adapt and print for your own archive. Fill it out locally; the website does not receive your notes. Use private labels rather than sharing personal filenames, locations or account details in a public support request.
A useful conclusion is specific: “Still and motion components for A were retained; both opened locally; destination pairing not yet tested.” That record tells you what to do next. “Everything is backed up” hides the unfinished step.
Stop before deletion; finish the recovery route
This session is complete when the sample’s components and limitations are recorded—not when the phone has been emptied. A sample cannot establish that the rest of the library is complete. If a component is missing, an export fails or a destination drops behavior you need, retain the source and investigate that gap.
Apple documents that deleting from iCloud Photos is reflected across devices using that library. Do not use deletion as an experiment to prove independence. Continue with our non-destructive recovery drill to check retrieval from your intended backup location. If your next task concerns the JSON companions in a Google Photos export, use the Takeout context guide; its file relationships are a separate case, not a substitute for this Live Photo review.
Sources & scope
Source pages checked October 12, 2026. Provider behavior is source-based; examples and the planning method are KYD’s own synthesis, not a hands-on cloud-service test.