A year later you may remember where a photo was taken and have no idea what number the camera assigned it. A useful name helps you find a file even when it leaves its folder. Use short, consistent fields for the date, subject, and version.

Pick a format that sorts well

A name such as 2026-09-18-north-trail-003 includes the date, topic, and order. If multiple cameras create the same numbers, add a short device suffix or use a shared sequence. When you do not know the day, keep the level of certainty you have. A year and month may be enough.

Include the version’s purpose

When an image has a master, an edit, and a sharing copy, keep the same base name and append its role. Edit-02 might identify a working version and web-1200w an exported file. Details such as colour and cropping decisions can live in a project note.

Check references before renaming

A catalogue, album, or webpage may still look for the old name. Identify files that are in use. Review the proposed names and extensions for collisions. Try it in a copy of one folder and check that running the same rule again will not keep changing names.

Try tomorrow’s search today

Find one photo by subject and another by date. Then locate both a master and its sharing copy. If someone else can infer each file’s purpose from the name, the convention is clear enough. Keep an example in the archive so new imports can follow the same pattern.

Make the name useful outside its folder

If a file already lives in a folder called “2025-06-14”, putting the date in the filename can seem redundant. But the context disappears when the photo is forwarded or moved. A short date, project name and sequence number still make sense after the file leaves its folder. A name like “2025-06-14-coast-003” helps identify the third entry from that day. When delivering a file, consider whether the filename needs a person's full name, an address or other identifying details. You can keep a descriptive name in the archive and a shorter one in the copy you share. The folder and file names need not repeat every detail. A year folder helps with browsing, while a short project name helps when the file is on its own. Send a sample to a different operating system and check that the name displays as expected. Put the most recognisable part near the front, since long names may be clipped in a download panel.

Rehearse a rename on a few files

Before renaming forty originals, try the rule on five copies. Write the old and new names side by side and check that two items do not end up with the same name. Files in different formats can share a root, with a short suffix to distinguish an edit from a share copy. Renaming the extension does not change the format. If you use a photo catalogue, check whether renaming through it keeps references intact. When you rename files outside the catalogue, reopen the editing project and look for missing links. An editor may store settings in a companion file with the same name root. If your workflow requires moving or renaming both, test the pair before changing the whole folder. When everything opens, leave a note describing the naming rules at the top of the archive. Explain whether the numbers indicate capture order, pages or review choices. Future you should be able to name the next file without reconstructing the whole system.