Begin with the questions you actually ask when looking for photographs. You may remember a year and a trip, a client's project name, or a family event. Use one primary organising principle for originals. A date-based structure with short descriptive folder names works for many personal collections because every photograph has a place even when its subject is difficult to classify.
For example, a year folder might contain 2026-04-18-river-walk and 2026-04-21-family-lunch. The date sorts consistently, while the description gives a person something recognisable to read. Keep names short enough to scan. A folder name is not a complete caption, and trying to include every person, place and object makes later navigation slower.
Give each original one home
Avoid copying the same original into several subject folders such as travel, trees and favourites. Those copies become difficult to reconcile when one receives edits or a corrected name. Use collections, albums or keywords in your photo software for overlapping categories, while keeping the original file in one documented location. If you do not use cataloguing software, a separate selection folder can contain exported derivatives clearly identified as copies.
Decide where edits and exports belong. They may sit in named subfolders within a project or in a separate output area, but distinguish them from originals. A folder called final is ambiguous once several sizes and revisions exist. Names such as exports-web and prints-selected describe purpose more clearly. Keep the working master, if your editor creates one, connected to the source through a stable filename or project identifier.
For a trip spanning several days, choose between one trip folder with dated subfolders and separate dated event folders. Both can work. The important point is that you can explain the rule and apply it to the next trip. Avoid adding extra levels simply because a hierarchy looks organised. Every level should help you find or manage something.
A weekend project with overlapping subjects
Suppose one weekend includes a garden visit, family lunch and photographs of a new camera. Filing by subject creates three possible homes for a frame of someone using that camera in the garden. A dated event folder avoids that conflict. The frame can then belong to several software collections without multiplying the original. The folder answers where it came from; the collections answer why you want to see it.
Keep incoming material in a clearly marked temporary area until the import is checked, but give that area a regular review point. Otherwise unsorted becomes a permanent parallel archive. Move one completed event into the established structure and confirm that search, edits and backups still work. When a new rule is needed, document the change before applying it to older material. Consistency does not require reorganising every historical folder immediately; a dated note can explain where the newer system begins.
Test awkward cases before migrating
Try the proposed structure with photographs from two cameras, a phone and a scan. Camera dates may be wrong, while a scan's creation date describes digitisation rather than the historical scene. Record uncertainty in a note or metadata field instead of inventing a precise date. An undated family scan can live in a clearly named collection without forcing a false year into the folder hierarchy.
Create a small trial using copies before moving an entire library. Check whether the editing application still knows where the files are. Catalog-based programs may need moves performed through their own interface or links updated afterward. Keep a verified backup of both originals and the relevant catalog before a large reorganisation. A neat folder tree is not worth broken references or lost edit history.
Write a short readme at the top level explaining the naming rule, where originals and exports live, and what remains unsorted. Give it to someone unfamiliar with the archive, or return to it after a week. If the explanation requires many exceptions, simplify the design. A structure is successful when an unfamiliar photograph can be placed correctly and an old one retrieved without reconstructing your past decisions.
