File Naming and Metadata for Family Photos

Good file naming and metadata for family photos answer two different questions. The filename keeps each item uniquely identifiable even when it leaves your photo app. Metadata records the people, place, date, source, rights, uncertainty, and story that make the image meaningful. Use both, and keep a simple collection index as a third safety net.

You do not need to identify every face before beginning. Start with stable identifiers, preserve the original grouping, and record uncertainty honestly. If you are still capturing the collection, follow the front-and-back workflow in how to scan old photos for a memorial book before renaming a large batch.

Difficulty: Beginner to intermediate
Estimated time: 15–30 minutes to design the system, then 2–5 minutes per described photo
Prerequisites: A small scanned batch, one person responsible for changes, and a backup copy before bulk renaming

What you will need

• A small batch with a known physical source, such as one envelope or album section
• A spreadsheet or comma-separated values (CSV) file for the collection index
• An image application that can write and read standard photo metadata
• A written filename pattern and vocabulary for uncertainty
• A second copy of the files before any bulk operation

Quick overview

Step 1: Preserve the source before renaming files

An envelope, album page, or box can carry context even when it has no formal label. Photograph the container and item order before rearranging anything. Give the source a short identifier such as BOX02 or ALBUM-A-P12.

Assign sequential item identifiers without guessing content:

BOX02-001
BOX02-002
BOX02-003

Use the same base identifier for related captures:

BOX02-001-front.tif
BOX02-001-back.tif
BOX02-001-front-access.jpg

The National Archives recommends simple alphanumeric file identifications, using hyphens or underscores rather than spaces and punctuation. This approach is conservative across operating systems and makes related files easy to find.

Small next step: Assign identifiers to one 10-photo batch. Do not rename the rest of the collection until you have tested sorting and search.

Step 2: Choose a filename pattern that can survive correction

Put stable information first. A source identifier and sequence are usually more durable than a person’s name or an estimated date.

A practical pattern is:

[source]-[sequence]-[side]-[version].[extension]

For example:

ALBUM-A-P12-03-front-master.tif
ALBUM-A-P12-03-front-book.jpg
ALBUM-A-P12-03-back-master.tif

This filename does not need to contain every person, place, and story. Very long descriptive names become awkward, reveal private information in shared links, and must change when an identification is corrected. Put rich description in metadata and the index.

Use these rules consistently:

• choose lowercase or uppercase and keep it consistent;
• use one separator, usually a hyphen or underscore;
• pad sequence numbers (001, 002) so folders sort correctly;
• avoid slashes, colons, quotation marks, emoji, and trailing periods;
• keep the original extension and do not rename .jpg to .tif without converting the file; and
• add version labels such as master, book, or web only when distinct copies exist.

Dates can appear when they are reliable. Use a sortable form such as 1964-07-12. When only a year or decade is known, keep the precise filename identifier and record 1964, circa 1964, or 1950s in description fields rather than inventing a full date.

Step 3: Separate known facts, attributed memories, and estimates

Family identification is collaborative evidence, not a quiz with one permanent answer. Use four confidence states:

• Verified: supported by a dated label, record, or multiple reliable sources.
• Attributed: “Identified as Mei Lin by Rosa Chen, October 2026.”
• Estimated: “Probably late 1940s based on clothing and album position.”
• Unknown: no responsible identification yet.

Never remove the earlier attribution when a relative disagrees. Record both perspectives and the reason for the later decision. Our guide to writing captions when family-photo details are missing gives wording for uncertainty that can also populate a memory-book caption.

Avoid facial-recognition labels as final evidence. They may help generate candidates, but confirm them with people and records before changing metadata. Do not upload sensitive family images to an identification service without reviewing its current privacy, retention, and model-training terms.

Step 4: Add a small, useful metadata set

Metadata can be stored inside an image, in a sidecar file, in a catalog database, or in a spreadsheet. No single method is perfect. Embedded metadata travels with a supported copy; an external index is easier to audit and can describe relationships between files.

Start with these fields:

The current IPTC Photo Metadata User Guide documents widely used fields including Creator, Description, Date Created, locations, Copyright Notice, rights, and people shown. Use the standard fields your software exposes, but do not force uncertain family knowledge into a field that implies certainty.

Metadata does not establish copyright ownership. The U.S. Copyright Office explains that the photographer is generally the initial copyright owner, subject to exceptions such as qualifying work made for hire. Write “photographer unknown” rather than assigning rights to the person who happens to possess the print. Seek legal advice for public or commercial reuse when ownership is unclear.

Step 5: Build an index that does not depend on one photo app

Create a spreadsheet with one row per stable identifier. At minimum, include:

identifier
master_filename
related_filename
source_container
people
place
date_display
date_confidence
description
contributor
rights_or_privacy
notes
last_updated

Export a CSV copy after major editing sessions. CSV cannot preserve every spreadsheet feature, but plain tabular data is readable by many programs. Keep the working spreadsheet too, especially if it contains validation lists or multiple sheets.

Add a short README explaining the columns, date conventions, confidence terms, and who may update the index. The Library of Congress personal-archiving guidance recommends descriptive filenames, a folder structure, and a brief description of that structure. The README turns your local habits into a system another person can understand.

Do not place live passwords, government identification numbers, private medical details, or contact information in ordinary photo metadata. Embedded fields may travel into public exports. Keep sensitive administrative notes in a restricted location and put only the minimum useful context in shareable files.

Step 6: Test whether context survives

Select three files: one with a known person, one uncertain image, and one front/back pair. Test the system:

1. Copy the files to another folder or device.
2. Open them in a second current application.
3. Search by identifier and a person or place.
4. Export an access JPEG and inspect its metadata.
5. Confirm that the CSV index still points to the correct filenames.
6. Restore the test files from a separate backup.

Applications may strip or remap metadata during export. Messaging services and social platforms often remove fields. Treat any shared derivative as expendable and keep masters plus the index under your control.

Warning: Run bulk rename and metadata tools only on copies first. One incorrect rule can separate hundreds of files from their index.

Folder structure for a small family archive

Keep masters, working files, and exports distinct:

family-photo-archive/
  00-readme-and-index/
  01-masters/
    box02/
  02-working-edits/
  03-memory-book-exports/
  04-sharing-copies/

Do not duplicate masters across many subject folders. Let the index carry multiple people, places, and themes. Duplicate working copies only when a project requires them.

Troubleshooting common problems

Two files now have the same name

Stop the rename process. Restore from the pre-rename backup, then add the stable source identifier or a padded sequence. Do not solve collisions with random suffixes you cannot explain.

A relative disputes an identification

Keep both attributions with names and dates. Mark the display caption uncertain until evidence supports a change. The archive can preserve disagreement without presenting one memory as verified fact.

Metadata disappears after export

Check the export dialog for an option to include copyright or descriptive metadata. If the destination strips fields, rely on the stable filename and share an accompanying index or caption sheet.

The filename reveals private information

Rename access copies with neutral identifiers before sharing. Keep rich private description in the restricted index, not in public URLs or downloadable filenames.

Frequently asked questions

Should names go in family-photo filenames?

They can, but stable source and sequence identifiers are safer. Names change when people are identified or corrected, and long filenames may disclose information. Put full names in metadata and the index.

Is embedded metadata enough?

No. Some software and sharing services strip metadata. Keep a collection index and README so context does not depend on one format or application.

What if the exact date is unknown?

Record the precision you actually know: a year, decade, range, or unknown. Add who supplied the estimate and why. Do not replace uncertainty with a made-up day or month.

Can I put private family stories in photo metadata?

Only if you understand where the file may travel and who can read the fields. Use a restricted index for sensitive context and a smaller public description for sharing copies.

Your next manageable step

Take one 10-photo batch. Assign stable identifiers, pair fronts and backs, create the index columns, and describe only what you know. Export a CSV, test three files in another application, and back up the batch before moving on.