How to Deliver Event Photos So Attendees Find Themselves Fast

A single-day conference with a photographer working the room produces thousands of frames. A gala with a step-and-repeat produces more. A three-day trade show with a booth rotation produces more again. After culling you still publish a number that nobody is going to scroll through looking for themselves.

The people who want those photos are not your client. They are attendees, speakers, sponsors and their marketing teams. Each of them wants a handful of images, wants them quickly, and has no interest in your folder structure. The two manual answers both cost you real hours.

• Folder building. You tag and sort by person, which means you are doing face recognition by hand, at your own hourly rate, on a job that has already been invoiced.
• The inbox. You publish one link and absorb the requests. Every request is a search through thousands of frames for a face you may not recognise by name.

Neither is a delivery workflow. They are both you working for free after the event, and they are the reason event photographers dread the week after a big job.

The alternative is to publish the whole set as one gallery and let each attendee do their own search. On clientgallery.io that feature is called Face Search. It is off by default and you switch it on per gallery, so a corporate job that should not have it simply does not get it.

Here is what happens mechanically, because it matters for what you can promise:

• When your photos go up, numeric face descriptors are computed in your own browser and attached to the gallery's photos. They describe the photos, not any particular person, and they are not linked to a name or an account.
• An attendee opens the gallery link and taps a button to find their photos with a selfie.
• The selfie is processed on the attendee's own device. It is never uploaded, never stored, and never seen by you or by anyone else.
• The comparison runs in the attendee's browser, against the descriptors for that gallery.
• On the server, those stored descriptors are gated by the gallery password, and they are deleted when the photo or the gallery is deleted.

From the attendee's side the whole thing is one link, one button and one selfie. From your side it is a switch. There are no per-person folders to build and no requests to answer, because the search that used to arrive in your inbox now happens on a phone in the lobby.

Corporate work has an organisational shape that wedding and portrait work does not. The person who hired you is the event organiser or the marketing lead. The people who want photos are attendees the organiser does not want to manage individually. What the organiser almost always asks for is one link they can put in the follow-up email.

clientgallery.io has a per-gallery password. It is opt-in and off by default. On the server it gates the gallery page, the whole-gallery ZIP, the full-resolution ZIP, comments, and face search. A section link resolves to its parent gallery, so one password covers every section.

Now be honest with your client about what that means at event scale. A password circulated to five hundred attendees in a mass email is a password in name only. It will be forwarded, pasted into a Slack channel and screenshotted. It raises the floor against a stranger who stumbles on the URL. It does not keep the gallery inside the guest list.

There is a second limit you should state rather than discover later. Individual proof image URLs are public and do not expire. The password stops the gallery page from disclosing those URLs, but it does not protect an image URL that somebody already holds and forwards.

What that adds up to, in practice:

• Set a password anyway on any internal event. It is one setting, it costs the attendee one paste, and it gates face search and the downloads server-side.
• Tell the organiser what it is worth. A circulated password is a speed bump for the public web, not a guest list. Say that in the handoff email so nobody assumes otherwise.
• Keep genuinely sensitive frames out of the circulated gallery. Board photos, unreleased product on a booth or anything under embargo belongs in a separate gallery with a password that goes to three people, not five hundred.

A gallery holds sections. You create them in the studio, or you drag a folder in and get one section per folder, which suits an event where you were already foldering by day or by room. Day 1, Day 2, Gala Dinner, Keynote, Booth is a natural structure.

There is exactly one level. A gallery holds sections, and a section does not hold sections. If you were planning Day 2 inside Track B inside Conference 2026, that shape does not exist here.

The more important constraint for event work is what a section link can do on its own. A section link is view-only. Face search works on the parent gallery link only.

So the link you circulate to attendees is the parent gallery link, every time. Send a section link to a sponsor who only needs their own booth coverage, and they will be able to look but not search or download. That is a genuine constraint, and it is better to plan around it than to find out from a sponsor.

Fair use is stated plainly rather than hidden, because at event volumes you will meet the first line of it. A gallery holds up to 1,000 photos. When you hit that, the upload tells you to split into another gallery, and galleries are unlimited.

A three-day conference at 900 delivered frames a day is three galleries, one per day, each with its own sections for tracks or rooms. Each of those parent links carries its own face search. That is a slightly worse attendee experience than one link, so cull to fit a single gallery where you honestly can, and split by day where you cannot.

One more thing worth saying to an organiser who asks about archiving: clientgallery.io hosts proof JPEGs sized for fast viewing, and hosted galleries never expire. It does not warehouse RAW files or master video. That is what keeps the price flat, and your masters still live on your own drives and backups.

Attendees want photos while the event is still the thing they are talking about. An organiser wants something to post before the hashtag goes cold. Nobody wants the gallery three weeks later, which is often when a full edit is realistically done.

The thing that actually helps is not a faster edit. It is publishing in batches as you cull, instead of holding everything back for one finished delivery.

• Create the gallery before the event. Set the password, switch face search on, and give the organiser the link on day one so it can go into the closing slide and the follow-up email.
• Publish a first batch the same night. A hundred strong frames from the keynote and the reception is enough for attendees to start searching.
• Add to the same gallery as you work. The link does not change, so the organiser never has to send a correction, and descriptors are computed for each new batch as it goes up.
• Tell people it is a first batch. One line in the handoff email stops the "where are the rest" emails you were trying to avoid.

Galleries are unlimited and hosted for as long as the account exists, so there is no cost to publishing early and topping up. The full-resolution ZIP is the one piece with a clock on it: three days per handoff, re-uploadable whenever the organiser asks again.

Face matching is a similarity search, not an identification. It is very good at surfacing a candidate set and it is not a filing system. On event work specifically, these are the conditions that break it.

• Shade and mixed lighting. A face lit by a window on one side and a stage wash on the other matches poorly.
• Angle. Profiles, three-quarter turns and heads tipped down over a phone are weaker than a face toward the camera.
• Motion blur. Dance floors, walk-and-talks and handshake grabs at a slow shutter often will not match.
• Sunglasses. An outdoor reception in sun costs you matches, and so do heavy hats and masks.

A false match is also possible. Someone will occasionally be shown a photo of a stranger who resembles them. At an event with hundreds of faces this will happen at least once, so do not tell an organiser that the results are a verified list of a given person's photos. They are candidates the attendee then eyeballs.

The consent question matters more than the accuracy question. At an event where attendees have not been told that face matching will be available, the organiser should leave the feature off. You are not the right person to make that call alone. Ask the organiser, put it in writing, and let them decide whether it is announced in the registration terms or the closing email.

Be accurate about what the product does and does not give you here. There is no separate attendee-facing control to delete face data, and there is no consent checkbox beyond the explanation an attendee reads on screen before giving a selfie. Switching face search off for a gallery stops the feature, but that switch is not itself a purge of descriptors that were already computed. Deleting the photo or the gallery deletes them.

clientgallery.io is one plan at $10 a month, or $100 a year, which works out to $8.33 a month. Face search is included and off by default. There is no print store, no commission, no per-gallery fee and no storage tier to climb.

The comparison that matters for this feature is Pic-Time, because face search sits on their top plan. Their pricing page lists Smart Search as "People search, keyword search, selfie search" on Advanced, and describes face recognition as letting visitors click a face to find all related images.

Now the honest half. Pic-Time documents its biometric handling in its privacy policy in a way we do not match. It states that the feature is disabled by default and that enabling it requires the photographer's explicit opt-in consent, that what is stored is an abstract numerical vector used only for clustering and search within that gallery, and that a guest's face data is deleted once the guest leaves the gallery. If your legal or client review needs a written consent flow and a published policy to point at, that is a real reason to choose Pic-Time.

The same goes for a studio whose business runs through a print store, an album designer or a sales workflow attached to the gallery. clientgallery.io does not sell prints and takes no commission, which means it also does not replace the sales side of those platforms. If that is where your revenue comes from, stay.

Where this fits is the volume event shooter whose gallery is a delivery surface, not a store. One flat price, unlimited galleries under fair use, your own branding and your own subdomain on the client-facing pages, and face search on the plan you are already paying for.

• Pic-Time pricing. https://www.pic-time.com/pricing. Fetched 8 September 2026.
• Pic-Time privacy policy. https://www.pic-time.com/privacypolicy. Fetched 8 September 2026.