How to organise a photo library your whole team can use

Most organisations take far more photographs than they can find again. Images sit on staff laptops, phone galleries, messaging threads and the drives of photographers who have since moved on. When a donor report, a website update or an anniversary campaign comes round, the team searches for hours, or commissions new photos of work that was already documented.

A well-run photo archive for organisations solves three problems at once. People can find the right image quickly. They can see who is in it, where and when it was taken, and whether it may be used. And the archive survives staff changes, because the knowledge lives in the system rather than in one person's memory.

Good photo library management starts with selection, not storage. The Library of Congress advises first finding all your photos, wherever they are, then deciding which ones matter most and, where there are several versions of the same image, keeping the highest-quality copy.¹

For a team, that means agreeing a simple rule after every shoot. Keep the selected images, plus a reasonable set of alternatives, and delete near-duplicates, blurred frames and test shots. A smaller archive of strong, well-described photos is far more useful than an enormous folder nobody can search.

Choose one folder structure and use it everywhere. A reliable pattern for most organisations is year, then project or programme, then a dated event or shoot folder, for example 2026 / Maternal-health / 2026-03-14_Nyamata-clinic-visit. The Library of Congress recommends giving photos descriptive file names, creating a folder structure, and writing a short description of that structure so others can follow it.¹

File names should follow the same rule every time. University of Iowa Libraries advises meaningful names that do not depend on the folder they sit in, dates written as year, month, day so files sort correctly, no spaces or special characters, and leading zeros in sequence numbers, such as 001 rather than 1.²

• 2026-03-14_Nyamata_maternal-health_001.jpg
• 2026-03-14_Nyamata_maternal-health_002.jpg
• 2026-06-02_Kigali_youth-forum_045.jpg

A caption in an email or a spreadsheet is lost the moment the image is downloaded and shared. Instead, write photo captions and metadata into the image file. The IPTC Photo Metadata Standard is described by its publisher as the most widely used standard to describe photos, and it is stored using XMP, an ISO standard, so most professional photo software can read and write it.³

The standard defines a set of fields your team can fill in consistently, from a description that includes the caption to the credit that must appear when the image is published.⁴ Agree in writing which fields are compulsory, who fills them in and when, ideally within a week of each shoot while details are fresh. At a minimum, complete:

• Description: a textual description of the image, including its caption
• Creator: the photographer's name
• Date Created: when the photograph was taken
• Keywords: words that express the subject of the image
• Credit Line: the credit that must be used when the image is published
• Copyright Notice and Rights Usage Terms: who owns the image and how it may be used

Every photo of a recognisable person carries obligations. In Rwanda, the data protection law defines personal data as any information relating to an identified or identifiable natural person, for example by reference to a name or location data.⁵ A captioned photograph that shows a person's face, gives their name and names their village should therefore be handled as personal data, and the law also contains a dedicated article on how long personal data is retained.⁵

In practice, store the signed consent form alongside the shoot, give it a reference number, and record that number in the image metadata. Note any restrictions, such as "no use on social media" or "do not show face", in the usage terms field. The IPTC standard also includes a field for the person shown in the image, which makes it easier to find every photo of someone who later withdraws consent.³

Many small teams can run a good archive on an existing shared drive, provided they follow the folder and naming rules and use software that writes IPTC metadata. The rules matter more than the tool. Keep a read-only master folder for final selections, so colleagues can download images without moving or renaming them by accident.

Digital asset management for an NGO or public body becomes worth considering when several departments and partners need access, when you hold tens of thousands of images, or when you need permission levels, download tracking and expiry dates on usage rights. Before buying any system, check that it reads and writes embedded IPTC metadata, so your captions and credits are not trapped inside one platform if you later move.

An archive is only as safe as its copies. The Library of Congress recommends keeping at least two copies, ideally more, stored in places that are physically apart, checking once a year that the files still open, and creating new copies on fresh media at least every five years.¹

File formats matter too. The Library of Congress lists TIFF, JPEG 2000, PNG and JPEG among its preferred formats for still images, and asks for embedded metadata such as title, creator and creation date using a common schema such as IPTC.⁶ Keep the original camera files for important shoots, and export high-quality JPEGs for everyday use. Name one person as the archive owner, and review the library each quarter.

• Select and keep the best version of each image after every shoot
• One written folder structure, used by everyone
• File names with the date first, no spaces, numbered 001 onwards
• Caption, creator, date, keywords and credit embedded in every file
• Consent form reference recorded for each identifiable person
• Usage restrictions noted in the rights field
• At least two copies, stored in different places
• A named archive owner and a regular review