Start here

Preserve the best available files before cropping, annotating or converting copies. Record where each image came from, use the applicable original-export option, retain companion files and check independent copies. Build a short index explaining what each image shows and any uncertainty about dates or file history.

What you can do with this guide

  • Keep the best available files and make separate cropped or annotated sharing copies.
  • Describe what each photo visibly shows; do not turn an image caption into a fault finding.
  • Record file origins, date discrepancies and exactly which version was sent.

The close-up shows the damage. The wider photo shows which vehicle and which side of the road. But the version you texted may be a crop or screenshot, and the original is buried in a phone library with a date you cannot explain.

Make the pictures useful before making them smaller or prettier. Preserve the best available files, keep their sequence and record where they came from. Then make separate sharing copies that a reviewer can open and understand.

This guide is for photos you own or are authorized to access. It covers Apple and Google export examples, file-date differences and a simple submission log. For a camera that continually records video, use the separate dashcam preservation guide.

Give each important photo a job

An album of fifty images can still leave the recipient asking which one matters. Create an index outside the preserved image folder. For each useful image, name the file, describe its visible subject and state the question it helps explain. Keep the description narrower than the conclusion you hope someone will reach.

Illustrative index entries—not findings about a real collision
ImageUseful descriptionKeep separate
Wide viewShows the parked vehicle, its orientation and the surrounding curb after the collision.Your recollection of where it was before impact.
Damage close-upShows the visible condition of the rear passenger door when photographed.A technical conclusion about impact speed or hidden damage.
Document photographShows the reference number on the officer's card.The complete official crash report, if it is a different document.

Use the image's existing filename in the index. If filenames repeat across phones, identify the source folder as well. Record who supplied the file and any known crop, edit or message transfer. This makes it easier to answer “which version did you send?” later without rewriting the preserved file.

Keep injury photographs private and share them only through a verified route when appropriate. A photo index can describe the record without turning your support email or a public post into a medical file. The purpose is a usable handoff, not publishing personal details.

If an injury claim is disputed or someone is questioning what your photos establish, see how an injury case review works. Bring the preserved files, the index and the actual request or objection. Do not alter a picture to make it match an account of the accident.

1. Identify what you actually have

Start with a short inventory before choosing an export button. A picture can look the same on several screens while representing different files. Record which device or account holds each version, who took it if known, and whether you received it from someone else.

Available itemWhat to recordPreservation choice
Photo in the device or library used at captureDevice, app, filename and known editing historyLook for the applicable original-export route; retain the existing library item.
Cloud-library itemAccount, item details, available quality and export settingDownload the available source version and verify the destination files.
Message attachment or shared copySender, received date and how it was savedKeep that copy and ask the photographer for a direct file export if practical.
Screenshot, crop or annotated imageWhich underlying image it represents, if knownPreserve it as a derivative; look separately for the underlying photo.

Use careful labels. “Exported from my Photos library on October 30” describes an action you can document. “Untouched camera original” makes a much stronger claim about the file's entire history. If that history is unknown, say so. An export cannot establish what happened before the file entered the library.

Do not discard the message attachment just because a better version may exist. It can help you track what you received and already sent. Keep different sources in separate folders so identical filenames do not cause one person's image to replace another's. A filename such as IMG_0042 alone does not identify a unique photograph.

Include the relevant sequence, not only the clearest close-up. Adjacent images may show which side of the vehicle appears in a detail shot or where the photographer stood. Keep your explanation in a separate note; do not add arrows or labels to the preserved files.

Several portable storage drives arranged beside an open laptop on a desk
Record where the separate copies are stored and verify that the files open. Illustrative stock photograph; the pictured equipment is not a recommendation or an endorsement. Photo: Jakub Zerdzicki / Pexels · License.

2. Choose the export route that matches the library

Check the device, app and version before following menu instructions. If an option is missing, stop and consult the matching official guide. An operating-system upgrade, account move or storage cleanup is not a preservation step in this workflow. Use a working supported route or seek technical help while leaving the existing material intact.

Where the photos areDocumented routeWhat to watch
iPhone Photos using the current Apple instructionsSelect the items, use Share, then Export Unmodified Originals and choose a Files destination.The destination initially offered is iCloud Drive; deliberately choose and record where you save.
iCloud.com in a browserSelect the items and use More Download Options to choose Unmodified Originals.Most Compatible makes a different format choice. Label a compatible copy separately.
Photos on a MacSelect the items, then File → Export → Export Unmodified Original.Retain filenames and related files; review the optional metadata export described below.
Google Photos on a computerSelect an item at photos.google.com, then More → Download.Inspect the specific item's backup quality and history; downloading does not establish camera provenance.

Apple distinguishes an unmodified download, in the format captured or imported, from its highest-resolution and compatible-format choices. That distinction matters when you are selecting a preservation copy. The browser route can also be useful when the mobile menu differs. See Apple's iCloud download instructions.

For the Mac route, Apple describes the original as the format imported into that photo library. Its export dialog allows a filename choice; keeping the existing filename makes your inventory easier to follow. See the Photos for Mac export guide. A previously edited image imported from elsewhere is not transformed back into a camera original by this command.

Google's computer download instructions describe creating a local copy of a library item. Record that route honestly. If you know a separate version remains on the capture device, preserve it too and keep the sources distinct.

3. Check the item, not just the backup setting

A general backup setting is not a complete inventory of the photos you need. In Google Photos on a computer, open the particular item and inspect Info. Google documents a backup-status and size display there, and an upload-source field when the source is known. An absent upload-source field is a gap to record, not a reason to invent a device history. See Google's item-level backup guidance.

Quality is a separate question. Google describes Original quality as retaining resolution and quality; Storage saver may compress, resize or change the format of photos. The item's Info details can show backup quality and size. See Google's backup-quality explanation. Record what this item shows, rather than assuming today's setting describes every earlier upload.

If only a reduced-quality version is available, preserve it. Then note which other device, account or photographer might have an earlier file. Do not assume switching the current backup setting recreates detail missing from an existing copy. A larger file found elsewhere also needs its source recorded; size alone does not establish which version came first.

A useful inventory entry might read: “Rear passenger-door photo; downloaded from my Google Photos account; item details show Storage saver; capture-device file not yet located.” This states the limitation without declaring the image useless or certifying it as original.

Hands holding a pen over blank paper beside the edge of a laptop
A copy log can connect original filenames, export settings and later working copies. Illustrative stock photograph, not an actual evidence record. Photo: Artem Podrez / Pexels · License.

4. Keep companion files with the photos

An export can contain more files than the number of pictures you selected. Do not immediately remove files because they lack familiar thumbnails. Some are related media; others hold information outside the image itself.

Export exampleWhat the source describesHow to organize it
Mac Photos: Live Photo originalA still-image file and a video file are exported separately.Keep both in the same source batch and record that they belong together.
Mac Photos: optional XMPThe Export IPTC as XMP option creates a sidecar for assigned IPTC information and keywords.Retain any exported sidecar; it is not a replacement for the image.
Google Takeout: JSON companionAdditional information outside the original file, such as Google Photos comments, is downloaded separately.Keep the JSON with the export's existing structure and filenames.

The first two examples are specific to Apple's Mac export procedure. They do not mean every phone export has the same components. Google's Takeout documentation explains the separate JSON metadata file. Do not apply that description to every individual-item download.

For a broader Google archive, select the relevant product in Takeout and review the available inclusion choices. Preparation can take minutes to days, and a large export can arrive in multiple archives. Download all the parts you requested and retain the archive files as well as a working extracted copy. The download itself does not delete Google's server copy. Recent changes made during preparation may be absent, so verify the needed photos after the export finishes.

Keep any export instructions or index alongside the batch. If you cannot tell which companion belongs to which photo, preserve the structure and mark the relationship as unresolved. Do not rename everything into one sequence or run a metadata-merging tool just to make the folder look tidy.

5. Verify a genuinely separate copy

Seeing a photo on a phone and a laptop may mean both are viewing the same synchronized library. Apple says changes propagate across iCloud Photos devices and deletion removes content from iCloud and the other enabled devices. That is why a second synced view alone is not the independent preservation copy proposed here. See Apple's sync and download explanation.

Choose a private destination you understand, such as a local folder and a separately stored external drive. Check whether the local folder is itself managed by a synchronization service. Merely giving it a new name does not answer that question. Record the actual folder and storage device, and make sure there is room for the selected files and companions.

  1. Finish the transfer. Wait for the export or copy operation to complete and note any warnings. An error or partial batch belongs in the log.
  2. Open the destination. Use the exported folder, not the photo-library thumbnail you started from. Confirm the expected images are there and open the files you intend to rely on.
  3. Check the contents. Look at the whole image and important details. Compare names, extensions, dimensions where available and related-file counts. Play associated video files.
  4. Make and check another copy. Copy the preserved batch to the separate destination, then open its files there. Record where each checked copy lives.

These are practical completeness and readability checks. Matching filenames, sizes or visible pictures do not certify authenticity. A file that will not open may have a compatibility problem or a transfer problem; keep it and record the error while obtaining help. Do not overwrite it with a converted image to make the error disappear.

Keep one folder for preserved exports, one for working copies and one for the versions actually sent. Store the copy log outside the preserved export batch. Leave the original device or library content in place; this checklist is not a recommendation to delete it after making backups.

6. Separate capture, display and download dates

A recent date in a computer folder does not necessarily mean the photograph was recently taken. Google explains that the operating system can assign a new file timestamp when you download an image, while photo metadata is available separately in file details. The path to those details depends on the operating system. See Google's download-date guidance.

Date you seeHow to describe it in your notesWhat not to assume
Capture-related metadataCopy the field label, displayed value and any stated time zone.That the camera clock was accurate or every file contains the field.
Date shown in a photo libraryName the app and record the value as displayed.That it must match the downloaded image's metadata.
Computer file dateRecord whether the field says created, modified or another label.That it is the shutter time or collision time.
Message or submission dateRecord when the particular attachment was received or sent.That transmission establishes when the image was captured.

Google also documents a specific reason for a display mismatch: a date changed in Google Photos appears there, while the image shared elsewhere or downloaded may show the camera's original date. See its date-and-timestamp explanation. This is a possible explanation, not a finding about your file.

Record discrepancies without changing fields to force agreement. If a time zone is not shown, write “not shown.” If you recall a device-clock problem or an earlier date edit, note that recollection and when you made the note. Do not backfill a precise time from memory or change the file to match the police accident report.

A screenshot of the details panel can document what you saw, but keep it as a separate reference image. It does not replace the underlying file or establish that a displayed time is correct. When a discrepancy matters to the claim, explain it to the person evaluating the records rather than silently choosing the most convenient date.

A black pen on a lined notebook page with a blank to-do list and date field
Check the export inventory for still images, videos and any companion files before treating the copy as complete. Illustrative stock photograph, not a completed file checklist. Photo: Rahul Shah / Pexels · License.

A fictional example: three dates for one photograph

This example is invented to illustrate the worksheet; it is not a client story. Maya knows she photographed her parked, damaged vehicle on October 28. On October 30 she downloads an image from Google Photos. The computer's created-date field shows October 30, the embedded capture field shows October 28 at 4:12 p.m., and the library displays October 29 at 4:12 p.m.

She keeps all three observations. The later computer date is consistent with her download, but it does not explain the different library date. She does not remember changing that date, and no time zone is visible in the details she checked. She records both uncertainties instead of adjusting the image.

Her note reads: “Downloaded October 30 from my Google Photos account. File name retained. Capture field displays October 28, 4:12 p.m.; app displays October 29, 4:12 p.m.; time zone not shown. Reason for app difference unknown. Local export and separate drive copy opened.” She labels a later arrow-marked JPEG as a working copy and records exactly which version she submits.

The note explains her handling of the file. It does not independently prove when the crash happened, whether the camera clock was right or what the photograph establishes about responsibility.

7. Use a small copy and submission log

Use one row per source batch, with a separate row when you repeat an export using different settings. You can copy this worksheet into a private document. Use your own labels; it is not an official insurer form.

FieldWhat to enter
Source and photographerDevice or account, app, person who supplied it, and anything unknown
Selected materialOriginal filenames, relevant sequence and expected companions
Export actionDate performed, exact option chosen and any warnings
Quality and datesItem quality where available; each date's field label; discrepancies
Checked destinationsFolder and storage device for each copy; what opened successfully
Working versionNew filename, conversion or annotation made, and source file used
SubmissionRecipient, channel, exact files sent, date and receipt confirmation

When someone asks for a smaller JPEG, preserve your export first and make the requested format in the working folder. Explain any crop, arrow, redaction or conversion. Do not use generative editing to reconstruct missing damage or surroundings. Keep the unannotated source available for an appropriate follow-up request.

Confirm the recipient and upload route through a contact you already trust. Ask which formats and companions they can receive and whether they need the source files as well as convenient viewing copies. Avoid sending your entire personal library to solve a request for a few accident images. Keep the submission confirmation and ask about missing or unreadable items; a progress bar alone does not tell you what the recipient can open.

If the insurer later says photos are missing, use the log to identify the batch, filenames and delivery date. Ask which item or format is still needed. The pending-document guide helps distinguish an unresolved document request from a decision on the claim.

When the files need more help

Stop repeated trial-and-error work if the device is damaged, exports consistently fail, files are missing, or the available copies have conflicting histories you cannot explain. Keep the current material and error notes. Seek appropriate technical assistance for access or recovery questions without assuming recovery is possible.

Preservation does not decide what must be disclosed, whether material can be used in a proceeding or how an insurer should evaluate it. Those questions depend on the circumstances. If a dispute involves the photos' history, a request for your device or an unclear production demand, get individualized advice before changing or supplying material you do not understand.

For questions about an injury claim, review the case-review process and legal options. Bring the source inventory, copy log and correspondence to the conversation. Keep sensitive images private; do not send accident files to Injury Law Advisor's support email.

Your next step

Your photos deserve context. So does your injury claim.

If the dispute goes beyond sending an image, bring the source files and the unanswered questions to a free injury case review. Ask what additional records may be needed before deciding your next step.

See My Case-Review Options →Free initial review through an independent provider. No obligation to hire.

Sources and scope

Core sources checked October 30, 2026; editorial update October 31, 2026. State examples apply only to the named jurisdiction. This guide is editorially researched; it has not been reviewed by an attorney and does not assess your individual claim.

  1. Apple Support: Download iCloud Photos and Videos
  2. Apple Photos User Guide: Export Photos, Videos, Slideshows, and Memories on Mac
  3. Google Photos: Download Photos or Videos to Your Device
  4. Google Photos: Back Up Photos and Videos
  5. Google Photos: Choose the Backup Quality of Your Photos and Videos
  6. Google: How to Download Your Google Data
  7. Google Photos: Edit Your Photos — Date and Timestamps

Spot an error? Contact support@injurylawadvisor.us with the page and source. Please do not email medical records or sensitive case details.