How to Deliver Photo Galleries to Clients (Without Losing Quality): A Photographer’s Step-by-Step Workflow

Delivering a gallery should feel like the final, confident step in your shoot, not a week of “the link won’t download” messages and mystery compression. The best client delivery workflow balances four things:

• Quality (no accidental resizing or re-compression)
• Simplicity (clients can download without learning a new tool)
• Organisation (clear folders, filenames, and versions)
• Control (expiry dates, access, and privacy)

Quick delivery checklist (copy and reuse)

• Choose your deliverables: finals (JPG), print set (JPG/TIFF), and optional RAWs.
• Export with intent: correct colour space, resolution, and sharpening for the use case.
• Name files consistently: “Client_Project_001.jpg” style, no camera defaults.
• Package smartly: keep folders tidy, zip only when it helps the client.
• Send with control: expiring link, optional password, download-friendly.
• Include a one-paragraph ‘How to download’ note for non-technical clients.
• Archive your master delivery (the exact set you sent) for later requests.

Delivery methods at a glance (what to use when)

The workflow: from export to a clean, client-proof delivery

1) Decide what you’re delivering (and what you are not)

Before exporting anything, define the deliverables in plain language. Clients often assume they will receive “everything”, which can mean very different things.

• Final edited set: the main gallery, usually high-quality JPEGs in full resolution.
• Print-ready set (optional): if you provide this, make it explicit. Many clients do not know the difference between web and print exports.
• RAW files (optional): only if it’s part of your agreement. If you do deliver RAWs, treat them as a separate product with its own folder and naming.

Tip: If you deliver multiple sets, make the folder names self-explanatory so clients do not accidentally send web-sized images to a printer.

2) Export settings that avoid “why do these look different?”

Most delivery problems are not actually “file transfer” problems, they are expectation problems. A few export choices prevent a lot of back-and-forth:

• Colour space: use what your clients and their tools expect. If you are not sure, prioritise compatibility.
• Resolution: if you promise full resolution, export full resolution. If you provide web images, label them clearly as web.
• Sharpening: apply output sharpening appropriate to the intended use, rather than one-size-fits-all.
• Metadata: keep or remove metadata deliberately, especially for sensitive shoots. Delivery is part of privacy.

3) Name files like the client will search for them later

Camera filenames (like DSC_1042) are fine during culling, but not for delivery. A client-friendly naming pattern:

• ClientOrBrand_Project_Date_###.jpg
• Example: Acme_Campaign_2026-07_001.jpg

This helps when clients download on different devices, share with their team, or come back months later asking for “that one image with the red wall”.

4) Decide whether to zip the gallery (and when not to)

Zipping is useful when you want to preserve folder structure, reduce the chance of partial downloads, and keep everything together. It is less helpful when your client is not confident extracting zip files or is on a locked-down work computer.

• Zip it when you have multiple folders (for example, “Web” and “Print”), or when you are delivering RAWs alongside finals.
• Do not zip when the client needs to quickly grab just a couple of images, or when you know they struggle with unzipping.

If you are unsure, you can deliver a simple structure with two clear folders and send as-is using a transfer link.

5) Choose the right delivery tool for the moment

For most final deliveries, a dedicated transfer link is the simplest client experience: upload once, send one link, client downloads. It also keeps your long-term cloud storage from becoming a graveyard of old client folders.

With LetsSend you can create a clean transfer link that’s designed for large file delivery, then manage the basics from one place. If you want to try that workflow, you can send a file free, or create a free account to keep transfers organised.

If your job needs ongoing access and back-and-forth (for example, a brand team pulling assets over months), a shared cloud folder can be better. Just be aware that permissions, sign-in, and “which version is current?” can become the real time cost.

6) Add control: expiry, access, and client-friendly guardrails

Clients rarely want permanent access forever, they want easy access until the project is done. That makes expiring links a practical default for many shoots.

• Expiry: choose an expiry window that matches your revision period. You can always resend later if needed.
• Password (optional): useful for sensitive shoots, celebrities, interiors, or anything under embargo.
• One clear destination: avoid sending multiple links in different emails. Put the latest link in the latest email with a short note.

If you want a detailed, click-by-click approach to expiry links, see How to Create an Expiring Download Link (Auto-Expires in 10 Steps).

To understand what control options are available in your account, you can also see all features or compare Free and Pro.

7) Send a “download instructions” paragraph that prevents support emails

Copy and paste this into your delivery email (adjust wording as needed):

Download note: “Use the link below to download the full-resolution gallery. For best results, download on a computer using Chrome or Safari, and save the files to your desktop before moving them into your photo library. If you see a preview, make sure you choose Download rather than saving the preview image.”

This one paragraph prevents the most common issue: clients saving preview versions or partial downloads and thinking the files are “low quality”.

8) Keep a master ‘sent set’ archive

Even if you keep your Lightroom catalog forever, it helps to keep a copy of the exact exported delivery (the same filenames and structure you sent). When a client asks for a resend, you can re-upload the same package with confidence rather than re-exporting and creating a new “version”.

If you run into upload issues, your fastest fix is usually to stabilise the connection, keep the browser tab open, and try uploading at a quieter time. If you need troubleshooting steps specific to your setup, visit the Help Center or read the FAQs.

Common gallery delivery problems (and how to avoid them)

“The images look worse than what you showed me”

• Confirm the client downloaded the actual files, not a preview.
• Deliver a clearly named “Web” and “Print” set to avoid misuse.
• Remind clients not to re-upload to messaging apps if they want quality.

“I only got some of the files”

• Encourage downloading on desktop rather than mobile where possible.
• Use a single organised folder structure (or a zip) to reduce missed items.
• Ask them to confirm available disk space before retrying.

“My company laptop won’t let me access it”

• Some workplaces restrict certain file-sharing domains or downloads.
• Offer an alternate delivery link, or suggest downloading from a personal device.
• If necessary, provide smaller grouped deliveries (by scene, day, or location).

A simple folder structure that works for most shoots

• 01_FINALS_JPEG_FULLRES
• 02_WEB_JPEG (optional)
• 03_PRINT (optional)
• 04_RAW (only if included)
• README.txt (optional, 5 lines max: what’s in each folder)

This structure reduces questions, prevents misprints, and makes it obvious what to deliver to a designer, a printer, or a social media manager.

When a transfer link is the best choice for photographers

Use a transfer link when you want the handoff to be:

• Fast (one upload, one link, no folder permissions)
• Clean (clients download without navigating your cloud drive)
• Controlled (expiry windows and optional access limits)

If that matches your delivery style, you can send a file free today and keep the workflow consistent from shoot to shoot.