How to Deliver Photos to Clients the Right Way
Learn how to deliver photos to clients with confidence — galleries, Drive links, prints, and USBs covered, plus branding, permissions, and automation tips.
The last frame is still on the camera, the couple is hugging, and you're already thinking about the 1,200 RAW files waiting on your card. That's usually the start of delivery, not the moment you send a link. The photographers who stay sane treat photo handoff as a small system, not a one-off upload, because the decisions made in the next day or two shape every client question that follows.
Table of Contents
- The Moment After the Shoot
- Preparing the Files Before Anything Leaves Your Drive
- Choosing the Right Delivery Method for the Job
- Turning Your Drive Into a Client Gallery
- Permissions, Copyright, and What the Client Can Do
- Branding, Sneak Peeks, and the Pre-Delivery Routine
- Automating Delivery So It Runs Without You
The Moment After the Shoot
The shoot ends, but delivery has already started. When I'm standing in the parking lot with a full card and a tired couple, the first decision is not which gallery tool to use. It is what happens to the files before a client ever sees them.
What matters in the first 48 hours
The cleanest workflows begin with one rule, final images only. That means culling, editing, and packaging happen before anything is shared, because clients should never be handed working files and asked to sort it out themselves. Private online galleries work better than email attachments or a loose folder share because they let you set password protection, expiration dates, view-only access, download access, and download tracking. Gallery-based delivery is also usually kept live for a limited review window, which gives clients time to download without leaving files open forever.
Practical rule: if you have not decided who can see the photos, how long they can access them, and what they can do with them, you are not ready to send a delivery link.
The fastest way to create headaches is to import everything, edit later, and send a link before the folder is stable. That is how version drift starts. A client downloads one set, you tweak a few images, and suddenly the gallery no longer matches the folder you have archived. If you want a cleaner handoff, keep the process tied to one source folder and one client gallery workflow, like the kind described in this guide to sending large photo files to clients, so you are not rebuilding the same set in two places.
Why the first choice affects everything else
What happens at import time controls the rest of the job. If you keep a clear separation between raw captures, selects, edited finals, and the delivery folder, you will not waste time untangling files when a client asks for a re-download or a print version later. If you do not, the gallery tool becomes the place where you discover your own disorganization.
That is why delivery should feel like the last mile of a workflow, not a rescue mission. The client experience begins long before they click a link, because the photographer has already decided whether the folder is curated, secure, and simple enough to support.
Preparing the Files Before Anything Leaves Your Drive
The least glamorous part of photo delivery saves the most time. Culling, editing, exporting, and naming do not feel exciting, but they decide whether the handoff looks organized or messy. The order matters, and once you set it, delivery becomes much easier to repeat for every client.
Cull before you edit, not after
Start by narrowing the shoot to the frames worth finishing. Guidance for photographers warns that delivering oversized sets can hurt client satisfaction, while a tighter gallery usually lands better, and one professional article recommends a 5-10 photo sneak peek within 48 hours followed by a curated final set. That same guidance notes that a wedding gallery is often 300-400 strong images rather than a bloated folder full of duplicates. The point is simple, clients remember the experience, not the file count.
From there, edit the selected images in your normal pipeline. Do not bounce between versions or save “almost final” files into the delivery folder. A delivery folder should contain only the images you are willing to stand behind.
Export for screen and print the right way
A solid delivery export usually means final JPEGs in sRGB for screen viewing, full-resolution files for print, and an optional web-sized set around 2048 px on the long edge for social sharing, as described in the client delivery guidance from Picur Photo. That same workflow recommends delivering the edited set instead of RAW files, because clients normally expect finished images, not camera originals. RAW is still reserved for special commercial contracts where the usage terms call for it.
My working rule: if a client cannot open it easily on a phone or send it to a printer without asking questions, it is not packaged yet.
Make naming and folder structure boring on purpose
The last step is naming. Keep one consistent folder structure and file naming system so gallery links, print orders, and archiving all point to the same set of finals. If you ever need to resend a gallery, that consistency saves you from hunting through exports to figure out which version was the correct one.
The payoff shows up after delivery, because a clean Drive-to-gallery workflow prevents re-uploads and version drift. A shared folder can stay as your source of truth while the client-facing gallery stays fixed, so you do not rebuild the same set in two places or wonder which file set the client is looking at. If you are building that routine now, a practical guide to sending large photo files to clients is a useful reference, and the same logic applies whether the folder ends up in a gallery or a shared download set.
Choosing the Right Delivery Method for the Job
There isn't one delivery channel that wins every time. Weddings, portrait sessions, headshots, commercial handoffs, and legacy clients all need slightly different treatment, and the best method is the one that matches what the client is trying to do with the files. A gallery is great when presentation matters, a drive link is useful when speed matters, and a print or USB handoff still makes sense in some packages.
| Method | Best For | Control | Client Friction |
|---|---|---|---|
| Private online gallery | Weddings, portraits, repeat client work | High, with passwords and download rules | Low once the link is live |
| Drive-style link | Quick turnaround, internal review, collaborative work | Moderate, depends on shared permissions | Low for tech-comfortable clients |
| Direct download set | Corporate handoff, agencies, large file transfers | Moderate to high if packaged well | Medium, because files still need sorting |
| Prints | Clients who want something tangible right away | High over the physical product | Low for the client, higher for fulfillment |
| USB | Legacy clients, luxury packages, physical delivery expectations | High on the object, low on updates | Medium, because it can be lost or out of date |
Private galleries for client experience
A private gallery is usually the most natural fit for weddings and portraits because it presents the work as a finished experience. A comparison of client photo delivery methods points out the trade-off well, file tools move data, but client galleries present the photos the way you want them seen. That matters when the gallery itself is part of your brand.
Drive links for speed and internal work
A Google Drive link or similar share link works when the priority is fast access, especially for internal approvals or quick client review. The downside is that Drive is designed for folders and documents, not for image curation. You get thumbnails, not a polished presentation, and the client has to do more work to understand what's included.
Direct downloads, prints, and USBs
Direct download sets are useful when the client needs files for a handoff, especially in corporate or agency settings where the brief is simple and the end user is comfortable managing assets. Prints are different, they solve the “I want this on my wall” problem, not the “I need a link” problem. USBs still show up in premium packages and archival handoffs, but they're a physical object that can't update after delivery, which is exactly why they're less flexible than a gallery.
The right channel follows intent. If the goal is curation, branding, and ongoing access, use a gallery. If the goal is speed, use the simplest link that gets the files where they need to go.
Turning Your Drive Into a Client Gallery
Most photographers already have a Google Drive habit, and that's useful because it avoids a second storage system. The problem with many re-upload gallery platforms is that they make you copy files into their storage, which doubles your work and creates version drift the moment you replace a JPEG. A Drive-based gallery layer keeps the originals where they already live and turns the folder into something client-facing.
A cleaner workflow from folder to gallery
The basic flow is simple. Connect the Drive folder, choose a visual theme like Editorial or Minimal, pick a layout such as Masonry, Grid, or Large, then set the access rules before sharing the link. If you need privacy, add a password. If you want a cleaner client handoff, configure download controls so the gallery behaves the way the job requires.
A tool like GalleryLink does this by reading directly from Google Drive, so the original files stay in your account and the gallery reflects folder changes automatically. That live sync matters more than it sounds, because it removes the re-upload step and cuts down on those awkward moments when a client is looking at an outdated gallery. It also supports mixed photo and video delivery in the same view, which is useful for hybrid shoots and event work.
Why live sync changes the maintenance burden
The win is not just faster publishing. It's less cleanup later. If you change a JPEG after delivery, the updated file appears in the gallery without you rebuilding the whole set, which is the opposite of version drift.
That's where browser-based galleries beat raw file dumps. A client can open the gallery without an account or app, move through the images, and download what they need from a single place. For photographers who want a more complete studio setup, the Pro plan also adds a studio subdomain with portfolio, services, FAQ, testimonials, and inquiry forms managed from the same dashboard.
The useful question is not “How do I send the files?” It's “How do I keep the client in the same experience from first view to final download?”
What to do once the gallery is live
Once the folder is connected and the gallery is ready, send one link and let the gallery handle the rest. If the client needs to revisit it later, the same link still works. If you need to update the set, the Drive folder updates the view without another upload cycle.
For photographers who want the technical bridge between Drive and a client-facing gallery, this guide to sharing client galleries from Google Drive is the cleanest place to start. It fits the way most studios already store files, which is why it avoids so many of the re-export problems that come from switching platforms midstream.
Permissions, Copyright, and What the Client Can Do
A lot of delivery friction has nothing to do with storage. It comes from the gap between what a client assumes and what the photographer meant to allow. Can they post the images? Can they print them anywhere? Can they pass the gallery to a vendor, a friend, or a marketing team? If those answers aren't explicit, delivery turns into email cleanup.
Separate viewing, printing, and commercial use
Keep the permissions in plain language. Viewing rights mean the client can open and look at the gallery. Printing rights mean they can order or make prints for personal use. Commercial use means the images can be used for business, advertising, or marketing, which is a different conversation entirely and should be handled separately.
A one-page readme or a short note inside the delivery message helps more than most photographers expect. The brief should say what's included, what's not included, and what the client can do with the files. That matters even more when the delivery contains edited JPEGs or TIFFs but not RAW files, because the client needs to know which format serves which purpose and what they are not receiving.
Make expiration and access rules obvious
Gallery expiration should be spelled out in the delivery note. If the gallery has a password, say so. If downloads are limited or view-only access is part of the setup, say that too. Clients rarely complain about a rule they can see up front, but they do complain when access changes without warning.
Passwords and unique links reduce casual forwarding, and download tracking gives you visibility if a client asks whether anyone else has accessed the files. That kind of clarity prevents the most common dispute, which is not usually about copyright law itself, but about the client not understanding what the gallery was meant to do.
Plain-language rule: if a client has to guess whether something is allowed, the delivery note didn't do its job.
Put the rights in the message, not in your head
The cleanest delivery messages answer the same questions every time. What's in the gallery. How long it stays up. Whether the client can download. Whether prints are included or only digital files. If the job is commercial, the usage terms should be even clearer, because the same gallery can serve both web-ready and print-ready workflows, but only if the usage boundaries are visible.
That is the part most photographers leave until after the misunderstanding. It is also the part that prevents the headache.
Branding, Sneak Peeks, and the Pre-Delivery Routine
A polished delivery feels like a small brand interaction, not a file dump. The client should recognize your tone, your timing, and your sense of order the moment the first sneak peek arrives. If the gallery looks intentional, the whole handoff feels more valuable.
Send the preview before the full gallery
A 5-10 photo sneak peek within 48 hours keeps the energy up while the client waits for the full edit. As noted earlier, that kind of early preview gives the client something to post, share, or forward while the rest of the gallery is being finished.
The key is to make the preview feel deliberate. Don't throw random selects into a folder and call it a teaser. Choose images that carry the story of the session, then use the sneak peek to point toward the full delivery.
Keep the gallery branded and easy to understand
Use the same cover image style, title format, and message template across jobs so the client knows the gallery came from you even before they open it. A short thank-you note works better than a long email. The note should tell them what they're seeing, what happens next, and where to click.
That consistency saves time on delivery day. Pull the gallery title from the folder name, keep the message template ready, and set follow-ups for clients who have not downloaded yet. If the platform supports reminders, use them. If it doesn't, keep your own checklist so the gallery does not expire with files still waiting to be saved.
Double-check before you send
A quick review catches the stupid mistakes that become customer service issues. Open the link, test the password, confirm the downloads, and make sure the preview and the final gallery still match. That last check matters because version drift usually happens when a final edit gets replaced after the message was already sent.
The more repeatable the routine, the less mental energy delivery takes. A branded workflow keeps the client experience steady, and it gives you a cleaner handoff every time.
Automating Delivery So It Runs Without You
Once the gallery and the Drive folder are connected, delivery stops being a one-time transfer and becomes an ongoing client experience. Live sync keeps the gallery current, favorites and selection tools make feedback easier, and features like QR access, guest uploads, and mixed media galleries turn a static folder into something clients return to. That's especially useful for events and weddings, where the gallery is often still working after the first delivery email goes out.
A Drive-based gallery also cuts down on duplicate storage and the maintenance burden that comes with uploading the same files twice. One dashboard can handle the gallery, the studio site, and the inquiry flow, which keeps the delivery system from fragmenting into five different tools. In practice, that means fewer re-uploads, fewer version mistakes, and fewer emails asking for the “latest” file.
The best delivery workflow doesn't end when the link is sent. It creates the next interaction, the next favorite, the next print order, and often the next booking. If you want a setup that turns a Google Drive folder into a client-facing gallery with live sync, optional passwords, and a clean delivery flow, take a look at GalleryLink and see how it fits into the way you already work.
Generated with Outrank