Organise a shared image library for content production

A file called image-final.jpg is a poor starting point for a colleague searching for a particular product view. A library becomes useful when the team can find the right image, understand its permitted use and distinguish the original from a prepared export. Organisation should support those decisions rather than merely make the folder tree look tidy.

Separate originals from prepared versions

Keep the original asset identifiable and preserve it when making crops or exports. A small thumbnail should not quietly replace the source somebody later needs for a larger layout. Give related versions a recognisable connection, such as a shared asset identifier followed by the destination or crop. Avoid creating a new unrelated name every time a file is resized.

Choose a small set of descriptive fields that reflect how people search. Subject, project, orientation and relevant product or location can be useful. ‘Beautiful’ and ‘professional’ rarely narrow a search meaningfully. Include a short factual description when filenames alone cannot distinguish similar shots. Do not identify an unnamed person as an employee or customer simply because the picture looks suitable for a business page.

Make the permitted use clear to the people choosing images

Do not treat everything in the shared folder as automatically available for every purpose. Keep the applicable usage instructions accessible where a restriction or approval affects selection, and consult the original licence or responsible owner when the intended use changes. If permission is uncertain, resolve it before publication or select another asset. The library should not encourage colleagues to infer rights from the presence of a file.

Create a simple distinction between assets ready to use and those awaiting a decision. A draft collection from a photo search is different from a set chosen for publication. Where a customer or staff member has supplied a photograph, confirm the intended context through the appropriate process instead of assuming that receiving the file means unlimited reuse.

Retire ambiguity, not useful history

Review duplicates and near-duplicates as a group. Keep the strongest or most useful versions and mark genuine alternatives clearly, rather than forcing every slightly different crop into search results. If an old asset is still used on a live page, track that dependency before removing it. A tidy folder is not worth a broken image on the website.

Ask a colleague unfamiliar with the collection to find a suitable image for a real brief. Observe the terms they use and the questions they ask. Adjust the naming and descriptions accordingly. Once a structure works, make adding these few details part of the upload process so the library does not depend on occasional large cleanup projects.