A good photo handoff saves the recipient from guessing which file to use. The editing may be finished, but the delivery still needs a little design: a clear folder, descriptive filenames, and enough context to understand what is inside.
Begin by asking where the images will go. A website, a print project, and a personal archive can require different files. Avoid producing several arbitrary versions before you know what the recipient needs.
Confirm the actual requirements
Ask for the requested file format, dimensions, orientation, and any size limit. If the destination has published upload instructions, use those rather than relying on a rule you remember from another project.
Also clarify whether the recipient expects edited selections, originals, or both. Do not assume that delivering a finished image means handing over every source file. Record the agreed scope in a short note.
Keep exports separate from originals
Create a delivery folder outside your original-image folder. Export into that location and check the result before sharing. This reduces the chance that a smaller version accidentally becomes the only copy you keep.
Use a predictable name such as “garden-01-web” when that label accurately describes the file’s purpose. Avoid an unexplained string of version words. If you revise a delivered set, give the new delivery a clear name and say which earlier version it replaces.
Include a simple contents note
A short text file can answer several questions at once:
- What subject or project does the folder cover?
- Which files are intended for which use?
- What captions or credits have been agreed?
- Are there any instructions the recipient should confirm before publication?
Do not invent rights or permissions. If usage terms are unresolved, resolve them with the relevant people rather than adding a confident label to the folder. Check images and embedded information for private details that are unnecessary to the handoff.
Open the exported files
Review the files from the delivery folder, not just the working versions in your editor. Look for the intended crop, orientation, sequence, and any missing image. Confirm that filenames are readable and that the set contains the number of images you promised.
For a shared link, check the intended access settings. Avoid making a collection publicly accessible merely because a private invitation takes an extra step.
Close the loop
Tell the recipient where the set is, which version it is, and what you need them to confirm. Keep the delivery note with your project records so the next request starts with the same information.
The workflow is easier when you already have a photo library you can browse. If the collection needs a stronger narrative before delivery, try selecting twelve photographs first.