Skip to main content
Skip to content
Newsletter
Menu

Preserve Inherited Digital Family Photos Without Erasing the Source

Separate readable files from locked accounts, record each source, copy without moving or erasing, and preserve context before making a family edition.

Begin inherited digital family photos with a source list and a careful copy of healthy, readable files. Keep locked accounts and failing devices on separate paths. Do not format, erase, repair, close accounts, or rename the only source as part of an initial preservation session.

The aim is modest: make one accessible group safer while preserving where it came from. Apple’s guidance for a deceased person’s account and Google’s deceased-user process provide official routes when access is blocked. Neither physical possession of a device nor a family relationship should be treated as automatic account access.

Difficulty: Beginner for healthy ordinary files; locked accounts or damaged devices need a different process
Planning time: Allow 30–60 minutes for an inventory and one small copy, plus transfer time; this is an estimate
You need: Permission to handle the material, an identified source, a separate destination with room, and a source note
Stopping point: One selected accessible folder copied and checked, with other sources safely listed for later

This guide describes a researched procedure. No inherited drive, account request, legal authority, or recovery operation was tested for it.

Step 1: Separate custody, access, and sharing decisions

Write down what you have been asked to do. “Keep these photographs safe,” “make a private family book,” and “publish an online archive” are different instructions. You may be able to preserve material while its later audience remains undecided.

Distinguish three questions:

Question What to record Why it matters
Who holds the source? Custodian, device or drive, and collection origin Prevents confusion about borrowed and inherited material
Who may obtain or copy it? Known permission or the official access process needed Avoids treating a device as proof of account authority
Who may see or redistribute it? Intended audience and unresolved restrictions Keeps preservation separate from publication

Mark unknowns plainly. A photograph can depict living people or contain another person’s work; a family story can reveal private information. Avoid turning uncertainty into a broad permission statement. If rights or estate responsibilities are disputed, keep the material restricted while the appropriate people obtain qualified advice.

You do not need to settle a whole estate to make a source list. Equally, a preservation task is not a reason to bypass a passcode or ignore a stated restriction.

Step 2: Inventory sources before changing them

Give each physical device, drive, or account a temporary source ID. Record the external label, custodian, approximate contents, access state, and next action. Keep passwords and recovery codes out of this general inventory.

Here is a designed example, not a recovered collection:

Source ID What is known Next action
DRIVE-A Healthy readable drive containing ordinary photo folders Copy one defined folder to a separate destination
PHONE-B Locked phone; contents unconfirmed Keep unchanged and identify the official access route
CLOUD-C Known provider, account access unresolved Record provider process and required next contact

Photograph an external label if useful and permitted. Preserve folder names and notes supplied by the custodian. A folder called from-Maya-2012 may carry information that disappears if everything is immediately sorted into years.

Work on one source at a time. That makes it easier to tell which files were copied and prevents two different drives from becoming an unexplained combined folder. If a device is unfamiliar, pause for help identifying it rather than trying random formatting or repair options.

Step 3: Copy healthy, readable ordinary files

Use this path only when the source is readable and behaving normally. Identify the destination by its name and location before copying. Check available capacity, and make sure you can distinguish the source drive from the destination drive in the file manager.

Copy a small defined folder using a copy operation. Do not move it, use a bidirectional synchronization job, or choose an option that deletes files from the source. If a system asks to initialize, format, erase, or repair the source, stop; those are not copy instructions.

Create an intake folder such as:

Family-photo-intake/
  DRIVE-A/
    00-source-note.txt
    01-unchanged-copy/
    02-working-selection/

In the source note, record the original path, copy date, custodian, and any message or missing folder. Retain the supplied structure in the unchanged copy. Put later selections and renamed files in the working area so the source relationship remains recoverable.

The National Archives advises preserving originals and contextual metadata. For this intake, the same practical separation helps: keep the received material intact and make changes on a derivative. Our file-naming guide explains a simple source-to-working-name index.

Stop when the source shows failure

Clicking, repeated disconnection, failure warnings, or an unreadable device containing the only critical copy call for qualified recovery advice. Do not run repeated experiments, write repairs, or format it in the hope that photographs will reappear. Keep a record of what happened and seek help appropriate to that device and its importance.

Step 4: Use the official process for inaccessible accounts

Keep account access separate from copying already readable files. Follow the provider’s current documentation and the process appropriate to your situation; requirements can vary.

For Apple, start with the deceased-family-member account guidance, including the applicable Legacy Contact or documentation route. Preserve existing information while the request is considered. Erasing a device for reuse destroys its contents and is not a way to recover the photographs on it.

For Google, use the official deceased-user request. Google says it does not provide passwords, and closing an account prevents a later contents request. Do not choose closure as a preliminary preservation step.

Record the provider, request state, person responsible, and next follow-up in the intake list. Do not mark a locked source as “backed up” because a request has been filed. A refusal or an unresolved request is also part of the honest collection record.

When lawful access or a contributor-supplied export becomes available, follow the source-specific method: export iCloud Photos or retain a complete Google Photos Takeout set. Those guides address originals, edits, motion, and supplemental metadata that a generic folder copy may not capture.

Step 5: Verify before organizing or deduplicating

Check the selected copied folder against its defined source. Record relative paths, file counts, and byte sizes where available. Open a range of images at a useful size, play selected videos, and inspect a caption or other companion document.

File counts alone do not prove fidelity. A count can include extra sidecars or miss a relationship between a photo and its description. Check the material that makes the collection intelligible: names, dates, album groupings, back scans, and source notes.

Keep apparent duplicates during intake. The same image may arrive from different relatives with different information, or an edited version may have a purpose that its filename does not explain. Deduplication belongs on working copies after you understand the differences.

If checks fail, preserve the source and the copy as they are, record the gap, and stop expanding the operation. Do not delete the received files simply because a destination folder exists.

Step 6: Protect a small, understandable family selection

Make another independent copy of the checked intake and notes. Follow the 3-2-1 backup method for separate locations and a recovery check. A second folder on the same drive does not remove that drive’s failure risk.

Then choose a small working selection for the memory book. Record what can be shared, what remains private, and who may review an uncertain description. It is acceptable for some inherited material to remain restricted or omitted indefinitely.

Name a steward and a backup steward rather than leaving a pile of devices to “the family.” The archive handoff guide provides a README, permissions record, and findability check. Begin with one source note and one checked folder; more elaborate organization can wait.

Troubleshooting common situations

The computer asks to format the inherited drive

Cancel and stop the copy attempt. Confirm that you selected the intended source and obtain qualified help if the files are not readable. Formatting is not an intake step.

Nobody knows whether a folder is complete

Describe it as the received folder, not the complete family archive. Record the custodian and known gaps. A bounded, accurately described collection is more useful than an unsupported completeness claim.

Relatives want immediate access to everything

Keep the preservation copy restricted while you prepare a permissioned selection. Ask for help identifying people and places through a suitable sharing copy, rather than distributing an entire unreviewed drive.

Frequently asked questions

Should I start by renaming every photograph?

No. Preserve an unchanged intake copy and its original paths first. Rename a working selection with an index connecting new names to the received files.

Can I close a cloud account once I know it exists?

Existence is not a verified export. Keep closure separate from preservation, and follow the provider’s current process. In particular, Google warns that closing an account prevents a subsequent contents request.

Must I finish the entire collection now?

No. An inventory, one safely copied folder, and a clear next action for locked or damaged sources are useful progress. You can stop there and return when the necessary access, help, or energy is available.