Name customer media with a stable asset identifier, then use a few agreed tags to describe what is actually in the file. Keep the original upload separate from edited exports. The aim is to retrieve the right item without opening every image, not to fit every possible detail into a filename.
Start with the questions your team actually asks
Before reorganizing the whole library, choose a small set of real requests: a photo of a particular product, an upright image for a particular layout, or an asset that is still awaiting review. These are different questions. Product identity describes the subject; orientation describes the file; review status describes a decision.
Write down the fields needed to answer those requests. A useful starting set is asset ID, product or variant when known, media type, orientation, receipt date and review status. Leave unknown details unknown. Guessing a product variant from a similar package makes a tidy library less trustworthy.
Give the original one lasting identity
As a fictional example, a customer sends a photo of a travel cup. Your team assigns asset C042 and keeps the uploaded file under that identity. A square crop can be C042-square-v1; a later corrected export can be C042-square-v2. The identifier connects the files even when their descriptive labels change.
A name such as final-final-new does not establish which version is approved. Record that decision in the asset entry. Avoid putting private customer details into filenames that may travel into public downloads or shared folders.
Use controlled tags rather than everyone's synonyms
Choose one label for each recurring concept. If one person uses upright, another vertical and a third portrait, a search can miss valid results. Agree a preferred term and document it beside the library. Keep tags small enough that reviewers can apply them consistently.
- Can another reviewer find the original from an export?
- Are product details confirmed rather than inferred?
- Does each status mean one clear review state?
- Can the same search be repeated by someone else?
Test the system on a handful of assets before moving a large collection. Ask a teammate to retrieve an item using only the recorded fields. If they need your memory to finish, improve the entry rather than adding more decorative tags.
Keep file history and eligibility separate
A well-named asset is not automatically cleared for reuse. Keep unresolved permission and publication checks visible. If you store uploads in Drive, consult Google's file-version guidance: uploaded images have different history controls from Google Docs, and older versions are not necessarily retained indefinitely.
For a broader collection and cataloguing workflow, explore 7-Day UGC Collection System Setup, especially its asset-organization section. Continue through Content Creation in Creator & Marketing. The useful result is a library someone else can search accurately, not a promise of higher conversion.
