Handing Over a Client's Image Library Cleanly

Structure the library while you are still using it

Nobody reorganises a two-year library at handover time. Whatever structure you worked in is what the client receives, so the structure has to be built for a stranger from the start. The reliable test is whether someone who has never worked on the account can find last October's product shots in under a minute.

A shoot-based hierarchy usually beats a channel-based one, because a single shoot feeds many channels and the source is the stable fact. Within each shoot, separate originals, selects, edited masters and channel exports. Keep the shoot reference in the folder name and in every filename inside it.

Avoid folders named after people, campaigns nobody remembers, or dates in ambiguous formats. And avoid the folder called Misc, which is where the images somebody will urgently need in two years always end up.

• Shoot or source folder with a reference code and an ISO-style date
• Originals, unmodified, kept separately and never overwritten
• Selects, the frames chosen for work
• Edited masters at full resolution
• Channel exports, in clearly named subfolders per placement
• Documents: releases, licences, the brief, the look guide

Include the originals, not just the finished files

Handing over only edited JPEGs leaves the client unable to redo anything. The next agency will re-edit, badly, from a compressed export, and the work will drift immediately. Include the original captures and the highest-quality masters you have.

Working files are a separate question. Layered files and raw developer settings represent real craft, and whether they transfer depends on your contract. Decide it deliberately rather than discovering the expectation at handover: many clients assume everything means everything, and the conversation is much easier before the relationship ends.

Whatever you include, say what it is. A short readme explaining which folder holds what, what format each is in, and what colour profile the masters use saves the receiving team a week of guessing.

The rights manifest is the valuable part

The images are easy to copy. What cannot be reconstructed is where each one came from and what may be done with it. A manifest listing each shoot or image set with its source, rights position, any expiry date, and whether releases exist is the single most useful thing you can hand over, and the thing that protects you afterwards.

Flag the four categories separately: created by you, supplied by the client, licensed from a library, produced by a subcontractor. Note licence restrictions in plain language, including editorial-only material and anything with a term that ends. An image whose licence expires next year is a liability the client needs to know about while there is still time to relicense it.

Attach the releases to the relevant shoot folders and index them by subject and shoot reference, so a specific image can be matched to a specific signed form years later. This is the request that arrives long after everyone involved has moved on.

Formats, resolutions and colour

Deliver masters in a high-quality format with the colour profile embedded and stated. Half of what a receiving team experiences as your work looking wrong is a profile mismatch, and it is trivially avoidable by saying which profile you used.

Include the resolutions that are actually in use rather than one master and a note saying resize as needed. If a client has been publishing at five defined sizes, hand over those five, because the person receiving them may not have the tools or the judgement to recreate them.

Do not hand over platform-specific exports as if they were permanent specifications. Requirements change regularly, so the readme should point the client at each platform's current documentation rather than baking last year's numbers in as fact.

The transfer itself

Large libraries fail to transfer over email and expiring share links. Agree a mechanism in advance: a direct transfer into storage the client controls, a physical drive, or a shared bucket with permissions handed over. Confirm receipt in writing and confirm they can open the files, because a corrupted archive discovered in six months is your problem in practice even if not in contract.

Agree a retention period for your own copies rather than deleting immediately or keeping everything forever. Clients frequently come back within a few months for something they cannot find. Keeping a copy for an agreed period, stated in writing, is helpful and also has data protection implications where images of identifiable people are involved, so set a defined period rather than an indefinite one.

Do a final pass for things that should not travel: internal notes in filenames, unreleased concepts, another client's assets that ended up in the wrong folder, and any personal data you should not be transferring.

Why a good handover pays

An agency that hands over cleanly is remembered as professional by exactly the people who recommend agencies. The marketing manager who receives a tidy, documented library will say so when someone asks them for a recommendation, and they will call you first if the next agency disappoints.

A bad handover produces the opposite in a more energetic form. Missing originals, no licence records and a folder nobody can navigate turn a neutral departure into a grievance, and licensing questions that cannot be answered can turn a grievance into a legal one.

Since the whole thing is decided by decisions made during the engagement, treat the manifest and the folder structure as ongoing deliverables rather than an exit task. Ten minutes a month for two years is a day of work spread out, which is less than the fortnight it will otherwise take under pressure.

Frequently asked