A sensible image file naming system makes large photo projects easier to search, review and hand off. It also reduces confusion when multiple editors work on similar products or revisions.
Build names around useful identifiers
Use stable identifiers such as product SKU, shoot date, angle or version where they help the team. A filename like SKU123-blue-front-v02 is easier to understand than a string of generic names. Keep the structure consistent across related products and document the convention for everyone involved.
Separate masters from delivery exports
Avoid overwriting the only editable original with a compressed delivery file. Keep source captures, working files and final exports in clearly labeled folders or use a naming suffix that distinguishes them. Version numbers should reflect meaningful revisions, not every minor save.
Make the system easy to maintain
- Use a predictable order for identifiers.
- Avoid names such as final-final-new.
- Keep filenames readable and reasonably short.
- Document abbreviations used by the team.
- Check that exported files match the intended SKU.
Consistent naming saves time during corrections, re-exports and future catalog updates.
Related reading
Continue with our guide to organizing photo editing project folders. For more on organizing files, see Adobe’s guide to organizing files in Bridge. For expert help, explore our product image editing services.
Frequently asked questions
Should file names use spaces?
Hyphens or underscores are safer. Spaces can be converted to odd characters in web addresses and some software.
What should I put first in a file name?
Start with the identifier you search by most, usually the SKU or project code, then add color, angle and version in a fixed order.
Do I need to rename files that are already in use?
Not necessarily. Apply the new convention to new work, and rename older files only when you re-export or reorganize them.
