How to Deliver Wedding Photos to Clients Without Re-Uploading

The wedding is shot, culled and edited. What's left is the part nobody enjoys: moving 8–20 GB of finished JPEGs somewhere the couple can actually see them, then waiting weeks for album picks that arrive as "the one on the steps where she's laughing".

This is a complete wedding delivery workflow that skips the upload entirely, turns selection into a list of filenames you can paste into Lightroom, and sets the delivery up so it keeps working for you long after the couple has downloaded everything.

Table of Contents

• How do you deliver wedding photos without re-uploading?
• Why the upload step is the real bottleneck
• Step 1: Let folder structure become gallery structure
• Step 2: Publish it, with a password
• Step 3: The sneak peek
• Step 4: Album picks as filenames
• Step 5: Set the delivery up to market you
• How long should a gallery stay online?
• The timeline
• Five delivery mistakes

How do you deliver wedding photos without re-uploading?

Share the wedding's cloud folder — the one you already backed the wedding up to — as "anyone with the link", publish it as a password-protected gallery, and send the couple that single link. Because the gallery reads the folder live rather than copying it, there's no second upload, no storage tier, and photos you add later appear in the link the couple already has.

Why the upload step is the real bottleneck

Most wedding photographers already have the finished set in cloud storage — it's the backup. Uploading that same set again costs an evening of bandwidth and then costs again monthly as a storage tier. It's the one step in the entire workflow that produces nothing the client can perceive: nobody can tell whether their photos were copied to a second server or read from the first.

Removing it changes two things. Delivery goes from "start the upload before bed" to about a minute, and archived weddings stay online at no extra cost — which matters more than it sounds, because anniversaries are when couples come back, order prints and refer you.

Step 1: Let folder structure become gallery structure

A wedding delivered as one undifferentiated wall of 900 thumbnails is exhausting, and the ceremony gets buried under the reception. Use subfolders as chapters:

• Getting Ready
• First Look
• Ceremony
• Portraits
• Reception

Each becomes a named scene the couple can jump between. You're probably organising this way already — the point is that no extra step is needed to carry it across, and reorganising later in the folder updates the gallery.

Two shooters? Prefix filenames on import so the merge is clean and attribution survives — the second-shooter workflow covers it.

Step 2: Publish it, with a password

Share the folder as "Anyone with the link", Viewer. Then create the gallery: the couple's names as the title, a theme and layout (masonry for a wedding — see why), a cover photo, and a password.

Two independent layers protect the work: the gallery URL ends in an unguessable random string, and only a bcrypt hash of the password is stored. Pick something the couple can say out loud, because they'll be relaying it to family — first names and the year is the convention for good reason. Client galleries also carry a noindex, so a wedding never appears in someone's search results. More detail: password-protecting client galleries.

Step 3: The sneak peek

The couple will ask for something to post within 48 hours. Because the gallery reflects the folder, this needs no separate delivery: drop ten finished frames into the folder, send the link, and add the remaining 890 a week later. Same URL, no follow-up email, no confusion about which link is the real one.

This also rescues the awkward cases — you find another card, or re-edit three frames after delivery. Fix it in the folder; the gallery is already correct.

Step 4: Album picks as filenames

Album selection is where wedding delivery stalls. The couple replies with a description, you spend an evening decoding it, and two rounds later you're still unsure.

Turn on album selection with a target count instead — 60 frames for a 40-page album. The couple hearts photos as they browse, sees their running count against the target, and submits a final set with their name attached. What lands in your dashboard is a timestamped list of real filenames you can paste into a filename filter. No accounts were created; favourites are tracked per browser, so each partner can shortlist on their own phone.

The full psychology and settings are in getting album selections back in days, not weeks.

Step 5: Set the delivery up to market you

The gallery will be opened by 100–200 guests — the warmest audience your business will ever have. Three settings turn that into future work:

• Leave client sharing on so the couple can send family a link holding only chosen photos, with your studio credited on every page (how that works).
• Tell them to add it to their home screen — one line in your delivery email, and the gallery gets reopened for months (the app that isn't an app).
• Put your links on the cover — website, Instagram, booking page. Guests who love the photos should be one tap from finding you.

How long should a gallery stay online?

As long as you like — and that's the quiet advantage of delivering from storage you already keep. An archived wedding costs nothing beyond the backup you were already paying for, so there's no reason to expire it at 90 days or charge the couple to reactivate. When they come back on their fifth anniversary, the link still works, and you're the photographer who's still there. The storage math spells out what that actually costs.

The timeline

When	You do	The couple gets
Day 2	Drop 10 edited frames in the folder, publish the gallery	Sneak peek link and password
Week 4–6	Export the full edit into the same folder, in scene subfolders	The full gallery at the same link
Week 6	Enable album selection with a target count	A favourites flow with a finish line
Week 7	Copy filenames → Lightroom → retouch	Album preview built from their picks
Forever	Nothing	A link that still works

Five delivery mistakes

1. One flat gallery of 900 frames. Use scenes; the ceremony deserves to be findable.
2. An expiring link. Guarantees unpaid re-delivery work, usually at an inconvenient moment.
3. No password on a wedding. The couple should decide who sees the whole set, not whoever the link reached.
4. Selection by email. Descriptions instead of filenames costs you an evening per client.
5. Treating delivery as the end. It's the moment 200 guests look at your work — the most valuable marketing surface you own.

The wedding photographers guide covers the wider setup, and the free plan is enough to run one wedding through this workflow end to end.