Give the collection a structure

Map locations before moving files

Begin with a written inventory rather than a mass import. List every phone, memory card, computer, external drive and cloud account that might contain photos. For each location, record its approximate size, earliest and latest dates, whether it contains originals, and whether another independent copy exists. A synced phone and its cloud account may represent one connected system, not two independent safety copies.

Include application libraries such as Apple Photos or Adobe Lightroom Classic. These can contain databases, previews and editing instructions as well as image files. Do not rearrange the contents of a managed library in a file browser. Use the application's supported export or relocation process and keep its catalog or library backup where appropriate.

Mark unclear locations as “not reviewed.” This small distinction prevents a folder named “old backup” from being treated as expendable before you have checked what is actually inside.

Choose a first session you can finish

Pick one event, one month or one memory card. Avoid starting with the entire family archive. Write down the source location, the intended destination and a stopping point. Before renaming or deleting anything, confirm that an independent copy of the source is readable.

1. Inventory: identify the batch and note where it came from.
2. Protect: copy it to a separate destination and open several files there.
3. Describe: give the event a clear name and add only useful labels.
4. Verify: find a known photo using the new structure.
5. Record: note unfinished decisions and the next batch.

Stop after the chosen batch, even if other folders remain untidy. The goal is to prove a repeatable process, not to create an exhausting one-time project.

Give originals one stable home

A date-led folder structure is straightforward to browse without specialist software. Use the ISO 8601 year-month-day order when the date is known. Add a short event description so the folder remains understandable at a glance. If the date is uncertain, use an explicitly approximate label rather than inventing precision.

Renaming every image is optional. If original filenames are already referenced in editing projects or captions, preserve them or keep a mapping. If you rename, use a collision-safe sequence and retain file extensions. Avoid names that differ only by capitalization, because operating systems handle those differences inconsistently.

Use tags for meaning, albums for purpose

Start with a short controlled vocabulary. Choose “garden” or “gardens,” not both. Separate subject labels from workflow labels so you can tell what an image depicts and what you intend to do with it. A useful initial set might cover subject, event and intended use. Add people tags only with an understanding of who can see them and how your chosen service handles face recognition.

An album is usually a selection or reference, not another independent copy. Removing an image from an album may leave it in the library; deleting it from the library may remove it everywhere. Read the actual command before confirming. Google Photos albums, Apple Photos albums and file-system folders do not have identical behavior.

Test the structure with real questions

Choose three photos you know exist and try to locate them without browsing everything. Search by a date range, event word or descriptive tag. If a search fails, ask which missing clue would have helped. Add that clue consistently rather than creating a new category for every exception.

Smart albums can save criteria, but availability and export behavior vary by application. Keep a short note describing important rules, such as “reviewed images tagged print candidate.” Do not assume face labels, favorites or automatically recognized objects will survive a move to another provider.

Leave a trail for your future self

Maintain a plain-text archive note alongside your working files. Record your folder conventions, tag spellings, export settings and the last reviewed batch. Once a month, check incoming files, resolve a small review queue and test a known search. When your circumstances change, adjust the system gradually instead of reorganizing everything at once.

Structure is successful when you can explain it, use it and recover it. A modest archive with clear decisions is more durable than an elaborate one that depends on perfect memory.