Before sorting a folder full of camera originals, edited copies and files called IMG_4821, decide where the originals belong—and make a protected copy. Otherwise, it is easy to move or delete a file before you know whether another intact copy exists.
A household collection needs to make birthdays, trips and ordinary moments easy to find. For an architecture or property team, photos may also document site conditions, construction progress, handover details and completed spaces. The labels and access controls may differ, but neither collection needs hundreds of narrowly named folders.
Choose one home for the originals
Set up a primary library on a computer, external drive or managed cloud service. A photo app may make searching easier, but first find out where it keeps the actual files. Some apps leave them in ordinary folders; others import them into a managed library. Until you know which applies, avoid importing the same collection into several apps.
Gather photos from phones, cameras, old computers, memory cards and shared folders. Copy them into a temporary intake folder inside the primary library, leaving the sources untouched for now. If the collection is large, work in batches. Starting with the current year lets you test the method before tackling older files.
Keep intake separate from the organized archive. New batches then have a predictable place to wait without getting mixed up with originals you have already checked.
Pick a folder structure you can remember
Year folders make a useful first level. Within each year, add a dated folder when an event needs its own space:
- 2025/2025-04-18 Family gathering
- 2025/2025-07-03 Coastal trip
- 2025/2025-09 Everyday photos
The year-month-day pattern sorts chronologically in most file browsers. If you do not know the exact day, use the year and month or a label such as “2020 date uncertain.” An invented date may look tidy, but it makes the record less trustworthy. Keep names short enough to read on a phone.
For project documentation, use an agreed project identifier: “2025/2025-05-14 Project 17 site visit.” Settle on the identifier before several people start importing. Add location or room names in captions, or use a few subfolders if needed. A separate folder for every wall, window and viewpoint usually makes files harder to browse.
Folders show where files live; albums show how you want to view them. If your app supports virtual albums, a single photo can appear under “Summer,” “Grandparents” and “Favorites” without three copies of the original. Check how the app handles albums before relying on them for backup or export.
Keep filenames practical
Camera-generated names are fine when folders and searchable metadata provide enough context. Rename a file when its name will matter outside the photo app—for instance, when sending it to a contractor or adding it to a property record. “Project17_2025-05-14_lobby-east_01.jpg” says more than “final-new-2.jpg.” Keep the original file extension, and avoid “final” if further versions might follow.
For batch renaming, choose a tool that previews the changes and adds sequence numbers. Test the rule on copies of a few files first. Renaming does not generally change the image itself, but a bad rule can erase useful distinctions or create duplicate filenames.
Import first, then remove clutter
Copy a batch into intake, compare the file count with the source and inspect a sample. Open files from the beginning, middle and end of a memory card or export. Check video clips, live-photo components and unusual camera formats too: some transfer methods omit them or save them separately.
Then separate exact duplicates from near-duplicates. Exact duplicates contain identical file data even if their names differ; a reputable duplicate finder may identify them using file hashes. A burst of similar frames, a crop and an edited export are near-duplicates. Those need a person to choose what stays. Before accepting an automated “delete all duplicates” command, check which version it would keep—particularly if one has captions or higher resolution.
Make three passes instead of judging everything at once:
- Remove obvious clutter, such as accidental pocket shots and unreadable images, unless they document something important.
- Compare bursts and keep the frames with the clearest subject or most useful detail.
- Mark favorites for easy viewing without deleting every ordinary photo.
If time runs out, leave the unfinished batch in intake. Moving half-checked files into the archive makes it harder to remember what you reviewed. Be especially careful with construction records: a dim image may still establish where or when a condition appeared.
Use dates and descriptions without overdoing it
Capture timestamps help with sorting, but they are not always right. Camera clocks can be wrong, travel can shift the apparent local date, and a scan of an old print may carry the scanning date rather than the date it was taken. Correct a batch when you know the right date; otherwise, note the uncertainty in the folder name or caption.
Describe photos that would be difficult to identify later. In a project record, “North elevation before cladding, 14 May 2025” is more useful than “site photo.” At home, the names of people and places may be enough. If descriptions matter, put them in a field your software can export or keep a plain-text note with the files. App-only face labels and albums may not transfer cleanly to another service.
Keep tags to a short, useful list—perhaps “site visit,” “completed,” “defect” and “reference” for project work. Before tagging thousands of photos, export a few and reopen them elsewhere to see whether the tags remain visible. Metadata, sidecar files and app databases do not all store information in the same way.
Protect the collection before clearing a device
Sync is not backup. Deleting a synced photo may remove it from every connected device; a backup should allow you to recover an earlier copy. Keep the primary library and at least two separate copies, with one in another location or a suitable cloud backup. The 3-2-1 rule—three copies, on two types of storage, with one off-site—is a useful way to plan, not a guarantee against every failure.
An external drive can hold one copy, but a drive that stays connected may be exposed to the same accidental deletion or malware as the computer. Disconnect it after a completed backup when practical. Check whether your backup includes videos, original-resolution files and recently deleted items; services handle these differently.
Test a restore rather than trusting a backup icon. Restore several files to a separate folder and open them, including an older photo and a recent video. If albums, captions or project labels matter, check those too. Do this before erasing a memory card or removing originals from a phone.
Control access to sensitive images
Photos can expose faces, addresses, floor plans, access points and location data. Check who can open a shared album before inviting others, and consider removing location metadata from public-facing exports. Keep unrestricted originals in the controlled archive; make separate sharing copies when a client, collaborator or family member needs only selected images. Project teams may also have contract, privacy and records-retention requirements to meet before deleting or publishing site photos.
Make new photos easy to file
A monthly routine is easier to maintain than another large sorting session. Copy new photos into intake, verify the transfer, remove clear clutter, file the batch in a dated folder and confirm the backup ran. If several phones feed the library, note which device or person supplied each batch until you have checked for overlap.
Keep edits apart from originals where practical. An “Exports” folder can hold resized sharing copies while the full-resolution source remains in the dated archive. For project photos, record the site-visit date, not the date an edited image was exported. When the next batch arrives, begin with ten images: check their capture dates, name the folder and restore one file from backup before clearing the source device.