Same-Day Event Photo Delivery: A Practical Workflow
Event clients want photos while people are still talking about the event. Here's how to deliver in stages from a single link — selects tonight, the full set later, no second upload.
Event photography has a shelf life measured in hours. The recap post goes out tomorrow, the press release needs an image tonight, and a gallery that lands next Tuesday is a gallery nobody uses. The trick isn't shooting faster — it's making delivery something that happens continuously rather than at the end.
How do I deliver event photos the same day?
Deliver in stages from one link. Export your first pass of selects into the event's Google Drive folder and publish that folder as a gallery while you're still culling. Because the gallery reads the folder live, the client can open the link during the event and see the rest of the set appear as your exports finish — no second upload, and no separate "here's the full gallery" delivery two days later.
Set the folder up before the event
Create the Drive folder and the gallery the day before, while you have time to think about it. Title it properly, pick the theme, decide on a password. Then on the day, the delivery step is just exporting into a folder that already has a live link pointing at it.
For a multi-day conference, one subfolder per day (or per session) keeps two thousand frames navigable — each becomes a named scene the client can jump between instead of scrolling to find the keynote.
Deliver in three passes
- The hero pass, during the event. Ten to fifteen frames the comms team can post immediately — the keynote wide shot, the room full, the CEO mid-gesture. Export on a break, send the link.
- The selects pass, that night. A hundred or so edited frames covering every part of the day. This is the delivery the client will actually use for their recap.
- The full set, within a few days. Everything, in scene subfolders. Same link, no new email.
The point is that all three are the same URL. The client bookmarks it once, forwards it to their team once, and it keeps getting better.
Why the whole team can open it
Event galleries get forwarded — to marketing, to comms, to the agency, to the speakers, to the sponsor who wants their logo shot. If your delivery requires accounts or per-viewer seats, that forwarding is where it breaks and where you start fielding emails. One link, no account, optional password shared once with the team is the setup that survives contact with a real organization.
Getting the shots they actually want
Turn on favorites and let the comms team heart the frames they want for the recap and social posts, then submit the set. What you get back is a list of filenames rather than a screenshot captioned "the one with the CEO laughing" — which matters when the request arrives at 11pm and the post goes out at 8am.
Keeping hundreds of frames fast
A big event gallery is only useful if it opens quickly on a phone with conference-center wifi. Previews are served resized from Google's CDN and lazy-loaded as the client scrolls, so an 800-frame gallery behaves like a feed rather than like 800 full-size JPEGs. The originals are still one tap away in the lightbox when someone needs the print-resolution file.
Video from the same link
Sizzle reels, speaker clips, and the highlight edit go in the same folder and play inline, with a Photos/Videos filter for people who only want one or the other. The client gets the entire event package from one URL instead of a gallery plus an expiring video transfer.
After the event
Don't take the gallery down. Event clients come back a year later planning the next one and want last year's photos for the deck — and that request is often how the rebooking conversation starts. Since the files live in your own Drive, keeping it up costs nothing.
The event-specific setup, including confidential and embargoed events, is on the event photographers page.