Home Wi-Fi question

How should I name scanned legacy photographs?

Questions with the same meaning and scope are grouped here; questions with different scope stay separate.

Quick answer

Current answer

Use a consistent filename that identifies the group, an approximate date or date range, and a unique sequence number. Add only stable, useful details; filenames should sort well and remain understandable if the files leave your photo application. Put richer stories, uncertain identifications, and search terms in captions or metadata rather than trying to fit everything into the name.

Use one simple pattern

A practical pattern is YYYY-MM-DD_description_sequence, with a date range or “undated” when needed. Examples include “1958-07-00_lake-trip_001.jpg,” “c-1970s_hughes-family-portrait_014.tif,” and “undated_miller-album_page-03_002.jpg.” Use leading zeros in the sequence number so files sort in order. Keep the same base name for related files, adding a clear ending for front, back, or a working copy. Choose ordinary letters, numbers, hyphens, and underscores to reduce problems when files move between services or devices.

Name what you know, not what you hope

Use a precise date only when you have a reliable reason for it. For an estimated year, use a convention such as “c-1965” or “1960s” and use the same convention throughout the collection. If the people are uncertain, avoid turning a possibility into the filename’s main fact; “possibly-ellen-and-child” is clearer than naming it simply “ellen.” A filename can be revised later, but a cautious first name reduces the chance that a mistaken label spreads through shared copies.

Keep descriptions and identifiers separate

Give each photo a unique sequence number even when several show the same event. Store longer captions, names, places, source group, and uncertainty in your photo software’s description or keyword fields. That makes the library easier to search without producing very long filenames. If you scan pages from an album, include a page identifier so the original context is visible, for example “1974_coastal-trip_album-p05_001.” Keep a small note explaining your naming pattern for future you or a family member.

Rename carefully and preserve links

Do a trial with a handful of files before renaming a large batch. Rename within the photo application when it manages its own library, or use one controlled folder if you work with ordinary files. After a batch rename, open several images, confirm front-and-back pairs remain together, and check whether captions, albums, or backups still point to the right items. Make a separate copy before a major rename, since interrupted or duplicate renames can make matching files difficult.

Sources

These official sources can help you check the next step for your equipment.

  1. Adobe: Photo Metadata Basics — Adobe: Photo Metadata Basics
  2. Library of Congress: Personal Digital Archiving — Library of Congress: Personal Digital Archiving

Before making disruptive changes

  • Avoid names such as “scan001” or “new photo” without a group or sequence clue; they become ambiguous quickly when collections are combined.
  • Do not overwrite an existing filename during a rename. Confirm the destination has unique names and retain a separate copy until you have checked the result.
Scope & boundaries
Applies when
Personal digital photo organization and preservation question limited to: How should I name scanned legacy photographs?
Does not apply when
Excluded when: account recovery device hardware repair photo copyright or ownership decisions irreversible deletion operations repairing damaged physical originals guaranteed data recovery legal, insurance, or professional custody conclusions.
Check first
  • Check first

    Does your situation match the recorded scope and exclusions?

    A scope or exclusion mismatch can mean that a different canonical question is needed.

Not the question you meant?

Find another question

This does not submit feedback or change this question.

Technical question record
Canonical question ID
1e638d30-7231-7e37-a38b-4188989a570a
Identity revision
1
Source language
en