Organize the photo library to prevent loss.

A brand image collection is lost not just due to accidental deletion. Most often, it is because images are scattered across too many locations, making it impossible to remember which version is the final one, which has been retouched, and where the original file is located. Just three simple things can solve this: a central repository, a naming convention, and information directly embedded in the image file.

The directory tree in the search team way.

The folder should be organized in a way that users think when looking for images, not based on how the images were created. Typically, there are three common directions:

• By project or campaign: Suitable when the photo set is tied to specific shooting events, such as product launches, Tet season, or advertising campaigns.
• By usage channel: suitable when the content team needs to differentiate images for websites, social media, and print materials due to varying sizes and requirements.
• By type of image: product, space, staff portraits, behind-the-scenes, brand documentation.

In practice, many repositories combine two layers: an outer layer by project or year, and an inner layer by type of image. It is important to choose one structure and document it internally so that anyone who joins later can understand and follow it.

Naming conventions: readable without opening the file

File name as IMG_2931.jpg not filterable, not organized, and does not convey anything when copied to another machine. A practical file naming convention typically includes: project or brand name, image type, date, and sequence number. For example: banhmi-brand_product_20260510_001.jpg.

The specific conventions are not as important as having the entire team agree on a single convention and document it. When new team members join or external parties receive the repository, they need to read that documentation and be able to follow it immediately.

Embedded metadata in files: information accompanying images

Metadata is information embedded within an image file according to technical standards, not external notes. The IPTC (International Press Telecommunications Council, an international standard for image metadata) allows for direct embedding into the file: the author's name, copyright notice, usage terms, descriptive keywords, and creation date.

The advantage of this method is that ownership information travels with the image when the file is copied or sent. Note: many social media platforms and image compression tools automatically delete metadata upon upload, so this serves as documentation rather than the sole proof of rights. When you need to determine usage rights or trace the author, the information is readily available in the file instead of having to sift through emails or ask the photographer.

At a minimum, a brand image should include: a clear file name, asset type, creation date, project or campaign name, and usage rights. Descriptive keywords should also be included for future retrieval.

Common errors when managing the image library

• Images are scattered across personal devices, chat frames, and emails: losing one device means losing everything, with no way to recover.
• No one knows which version has been retouched and which is a draft, leading to the use of unedited images.
• Copyright information is lost when images leave the original file because metadata is not embedded.
• Creating a directory structure that is too complex on the first day, causing the team to struggle and abandon it, resulting in everything being saved in a common folder.

Metadata is the most powerful organizational tool for an image repository. Information embedded in the file travels with the image everywhere. Information written externally will sooner or later become lost.

Summary from IPTC Photo Metadata Standard and DAM (Digital Asset Management) practices of Bynder and Canto

This article is for reference. The scope, pricing, and specific commitments of Sinh Vũ are detailed in the proposal and signed contract.