You have just finished scanning a box of old family photographs. The files sit on your hard drive as a mixture of generic names like IMG_4422.jpg, Scan001.tif, and a few vague labels such as “Birthday”. Without a clear system, finding a specific picture later becomes a time‑consuming search. A practical naming approach can turn a chaotic folder into a searchable archive that works for anyone who accesses it.
Common naming mistakes
The most frequent error is relying on the camera or scanner default names—strings such as IMG_4422.jpg or Scan001.tif. These identifiers convey nothing about the content, the people shown, or the occasion. Vague descriptions like “Family” or “Event” are only marginally better because they repeat across many files and offer no way to distinguish one image from another. When you later need a picture of your grandmother’s wedding, you end up scrolling through hundreds of similarly named files, which defeats the purpose of digitising the collection. A quick audit of the current filenames often reveals patterns that can be replaced with a more informative scheme.
Checklist:
1. Identify all files with default or vague names.
2. Group them by obvious content (e.g., same event or person).
3. Mark the groups for renaming in the next step.
Date‑first naming convention
A simple, software‑free convention starts with the date in ISO format (YYYYMMDD), followed by a brief subject and, if needed, the event name. For example, 20230704_Graduation_JohnDoe.jpg tells you the exact day, the occasion, and the primary individual. Keeping the date first ensures chronological sorting in most file browsers, while the subject and event provide immediate context. Use only alphanumeric characters and underscores to avoid compatibility issues across operating systems. Keep the subject short—typically a single name or a pair of names—so the filename remains readable.
Steps to apply the convention:
1. Determine the exact date of each photo.
2. Write the subject (person or group) using standard spelling.
3. Add the event or location if it adds clarity.
4. Combine the parts with underscores, ending with the appropriate file extension.
Handling unknown dates
When the precise day is missing, use an approximate date placeholder while preserving the sortable order. Replace the unknown portion with “00” or “??”; for example, 1975_00_00_Christmas_Grandparents.jpg indicates a year‑only date, while 1975_06_00_Graduation_Emily.jpg signals a known month but unknown day. If only a decade is known, the format “1970s_00_00” can be used. This approach keeps the files in the correct chronological bucket without forcing inaccurate specifics. Document the meaning of the placeholders in a short reference file so future users understand the convention.
Quick guide for approximate dates:
– Year only: YYYY_00_00
– Year and month: YYYY_MM_00
– Decade: YYYYs_00_00
Batch‑renaming with free tools
Renaming dozens or hundreds of scans manually is impractical. Free utilities such as Bulk Rename Utility (Windows), PowerRename (part of PowerToys), or the command‑line tool exiftool can apply the date‑first pattern in bulk. First, create a spreadsheet that maps each original filename to the new name following the convention. Then, import the list into the chosen tool and let it rename the files automatically. Most tools allow previewing the changes before they are written, reducing the risk of accidental overwrites. Keep a copy of the original filenames in a separate log for reference.
Typical workflow:
1. Export the current filenames to a CSV.
2. Add columns for date, subject, and event.
3. Concatenate the columns into the new filename format.
4. Run the batch rename tool with the CSV as input.
5. Verify a sample of renamed files before committing.
Storing names: filename, metadata, and log
Names can be stored directly in the filename, embedded in the file’s metadata (EXIF/XMP), or recorded in an external log. Filenames are the most portable and are visible in any file manager, making them reliable for quick searches. Metadata provides richer information—such as multiple people’s names or detailed captions—without lengthening the filename, but it requires compatible software to view. An external log (e.g., a spreadsheet) can capture additional context like relationships or stories that do not fit neatly into a filename. Choose a primary method (usually the filename) and supplement it with metadata or a log when extra detail is needed.
Recommendation:
– Use the date‑first filename as the primary identifier.
– Add the most important name(s) to the filename.
– Store secondary names and notes in EXIF/XMP tags.
– Keep a master spreadsheet for any narrative details.
Reconciling duplicate names across archives
Different family branches may have scanned the same image and given it distinct filenames. When consolidating archives, avoid overwriting by adding a source tag or a numeric suffix. For instance, 20210715_Wedding_AnnaDoe_ABC.jpg and 20210715_Wedding_AnnaDoe_DEF.jpg preserve both copies while indicating their origin. If the content is truly identical, keep the higher‑resolution version and delete the duplicate, noting the decision in the log. Consistent naming across the combined collection prevents confusion and makes future merges smoother.
Practical steps:
1. Compare filenames for exact matches.
2. If a match exists, examine file sizes or resolutions.
3. Rename one copy with a source identifier (e.g., _ABC or _DEF).
4. Record the merge decision in the master log.
Testing and sharing the convention
A good system should still be intelligible after a couple of years. After naming the batch, set a reminder to review the folder in two years. If you can locate a specific event or person without consulting the log, the convention works. Share the naming rules with relatives who also maintain digital photo collections. Provide a one‑page cheat sheet that lists the date format, subject placement, and placeholder rules. When everyone follows the same pattern, cross‑family searches become straightforward, and new scans can be added without re‑organising existing files.
Checklist for long‑term viability:
– Verify that each filename contains a sortable date.
– Confirm that the subject name is present.
– Test a search for a random person or event.
– Distribute the cheat sheet to all contributors.
Worth remembering: Use a date‑first filename (YYYYMMDD_subject_event) as the primary identifier, add approximate date placeholders when needed, and keep a simple log for extra details; this creates a searchable, portable archive that survives years of use and can be shared across family members.
Common questions
What format or settings should I use?
Save the scans as lossless JPEG or PNG files, using a resolution of at least 300 dpi for printed photos; this preserves detail while keeping file sizes manageable.
How should I label the files or items?
Apply the date‑first convention (YYYYMMDD_subject_event) directly to the filename, embed secondary names in EXIF/XMP tags, and record any narrative notes in a separate spreadsheet.
How many backup copies should I keep?
Maintain at least two independent backups: one on an external hard drive kept in a different location, and another in a cloud storage service that offers versioning.