What "public" actually means

A public gallery is open to anyone who has the link. There is no code, no gate — open it and you are in. This is the right call when the photos are low-sensitivity and easy distribution is the whole point: a community fun run, a public festival, a conference where attendees expect coverage. The benefit is zero friction; the trade-off is that the link can be forwarded freely and you lose control of who sees the set.

What "private" adds

A private gallery puts a gate in front of the photos — typically a PIN that guests must enter before they can view or search. Only people you share the code with get in. This is the right default for anything personal or sensitive: weddings, private parties, kids' events, corporate functions where the photos should stay inside the company. You can regenerate the PIN if it leaks, and revoke access by closing the gallery.

A simple decision rule

• Would you mind if this link were posted publicly? If yes, make it private.
• Are children in the photos? Default to private.
• Is this a closed group (a company, a wedding party, a school)? Private, gated to that group.
• Is this a large public event where coverage is expected and easy access is the goal? Public is reasonable.

Consent is separate from access

Access control decides who can open the gallery. Consent is about whether the people in the photos are comfortable being there and being findable by face. They are related but not the same — a private gallery shared with the right group still benefits from people knowing how it works. A few good practices:

• Tell guests how delivery works — a line at the event or in the share message ("photos will be in a gallery you can find yourself in by selfie") sets expectations.
• Offer an opt-out path — if a guest would rather not be searchable, a private gallery and the ability to remove specific photos respects that.
• Be especially careful with minors — gate those galleries and limit them to the relevant families.

Retention: privacy is also about time

A gallery that stays open forever is a standing pool of photos and face data. Good practice is to set a retention window so the gallery closes and its photos and face data are purged after a defined period. This is not just hygiene — it limits how long the data exists to be misused, and it is the kind of policy guests appreciate when they hear it. Galleries can be set to expire on a date or after a window, and renewed if the client needs more time.

The takeaway for photographers and organisers

Public for genuinely public events; private for everything personal — that covers most decisions. Layer on a short explanation of how delivery works, an opt-out for anyone who wants it, extra care around minors, and a sensible retention window, and you have a delivery setup that is both convenient and responsible. Face matching makes finding photos effortless; handling access and consent well is what makes that effortlessness something people trust.

FAQ

Should an event gallery be public or private by default?

Default to private for anything personal — weddings, parties, kids' events, corporate functions. Public is reasonable only for large public events where open access is the point. A private gallery gates entry behind a PIN.

How do private galleries control access?

A private gallery requires a PIN before anyone can view or search it, so only people you share the code with get in. The PIN can be regenerated if it leaks, and access can be revoked by closing the gallery.

What happens to photos and face data over time?

Galleries can be set to expire after a retention window, after which the photos and associated face data are purged. This limits how long the data exists and can be renewed if the client needs the gallery to stay open longer.

First, find the gallery link

Your photos almost always live in a gallery link the photographer or organiser shared — usually over WhatsApp, email, or SMS, sometimes printed on a card at the event. Start by checking those places. If you cannot find a link, the fastest move is to ask the host, the couple, the event organiser, or the photographer directly for their gallery link. There is no public website where event photos of you simply appear; you need the specific link for that event.

If the photographer used face matching

Many event photographers now deliver through a gallery that finds you automatically. If yours did, the process is genuinely a one-minute job:

1. Open the gallery link on your phone — it works in any browser, with no app to install.
2. Take a quick selfie when prompted (or upload one). This is just used to identify you within this gallery.
3. See your matches — every photo you appear in is surfaced instantly, without scrolling past everyone else.
4. Download what you want — save individual photos, or grab all your matches at once if the gallery offers a bulk download.

That selfie is matched only against the photos in that one event. It is not a search across the internet, and you do not need to create an account to use it.

If it is a regular gallery or shared folder

If the link is an ordinary photo gallery or a shared cloud folder, there is no selfie shortcut — you will need to browse. A few tips to make that faster: sort by time if you know roughly when you were photographed, look in folders named for the part of the event you attended, and use any people or search features the gallery offers. It is slower than face matching, but the photos are in there.

Common questions guests have

A few things worth knowing before you go hunting:

• Galleries can expire — if a link no longer works, the gallery may have closed after a retention window. Ask the photographer whether it can be reopened.
• Private galleries need a PIN — if you are asked for a code, get it from whoever shared the link; it keeps the photos limited to invited people.
• You can come back later — a self-service gallery lets you re-open the link and re-download months down the line, as long as it is still active.

The bottom line: your event photos are almost certainly sitting in a gallery link waiting for you. If the photographer used face matching, one selfie gets you all of them. If not, the link still has your photos — it just takes a bit of browsing. Either way, the first step is the same: track down that link.

FAQ

I attended an event — where are my photos?

They are almost always in a gallery link the photographer or organiser shared, usually by WhatsApp, email, or SMS. If you do not have it, ask the host or photographer for their event gallery link.

How do I find photos of just myself in a big gallery?

If the photographer used face matching, open the link, take a selfie, and only your photos appear. If it is a regular gallery, you will need to browse — sort by time and check folders for the part of the event you attended.

Do I need an account to get my photos?

With a face-matching gallery, no — you just open the link and take a selfie. Some galleries may ask for an email to send your download, but there is no full sign-up to view your matches.

Upload by day, not by venue

Most weddings span getting-ready, ceremony, and reception across a single calendar day, sometimes in two or three locations. Upload them as one event so face matching crosses the whole day. If you split by venue into separate galleries, a guest who appears at both the ceremony and the reception has to search twice and may assume the first gallery was all there was. One event, one search, every photo of them.

Use folders for browsing, not for matching

The couple will often want a "ceremony only" or "reception only" view to share or relive a moment. Use folders inside the one event for that. The important thing is that face matching still runs across the entire set regardless of folders — so a guest gets every photo of themselves whether it lives in the ceremony folder or the dance-floor folder. Folders are for human browsing; matching is global.

Deliver to guests and the couple from the same gallery

You do not need a separate per-guest export. The single gallery you hand the couple is the same one every guest uses. The couple browses the full set; each guest takes a selfie and sees only their own photos. That collapses what used to be the most thankless part of wedding delivery — repackaging personal galleries for individual guests — into nothing.

What that looks like for each part of the day

• Getting ready and first look — intimate frames scattered across small groups. Matching connects each person to every frame they appear in, even when they show up in only a handful of morning shots.
• Ceremony — wide shots capture dozens of guests at once. Manually tagging all of them is impractical, so historically most of those photos never reached the people in them. Matching surfaces every face automatically.
• Group portraits — the highest-value shots for guests, and the hardest to distribute because each belongs to a dozen people. Every guest gets the formals they are in, plus the candids around them.
• Reception and dance floor — thousands of low-light, fast-moving frames no one is going to sort by hand. Matching handles it even with motion blur and off-axis angles.

Lock sensitive weddings to an invite list

For high-profile couples, interfaith ceremonies, or any wedding where some guests prefer not to be searchable, set the gallery to private. A PIN gate means only people you share the code with can enter and search at all. You can also set the gallery to expire, so it does not stay open indefinitely after the moment has passed.

Brand the gallery to your studio

Every guest who finds their photos passes through your gallery on the way out — that is a referral channel hiding in your delivery. Add your studio logo, website, and Instagram so the gallery carries your brand. The aunt who finds twelve photos of herself in two minutes is exactly the person who books you for her own daughter's wedding, and she now knows your name.

Make downloads self-service — including months later

Weddings generate long-tail requests: a guest comes back at the one-year anniversary wanting that one photo. A self-service gallery means they re-open the link and re-download without emailing you. Offer a "download all my matches" zip so a guest in fifty photos gets one file instead of saving fifty by hand. The gallery keeps serving the couple's entire circle for months, with no further work from you.

The before and after

The traditional version of this workflow is two to six weeks to a single gallery drop, hours of optional and usually-skipped tagging, and a steady trickle of "do you have any photos of me?" messages for months. The face-matching version is: upload the day as one event, share one private link, and let every guest serve themselves from the moment indexing finishes. Your craft — the shooting and the editing — is unchanged. The admin around it largely disappears.

FAQ

Should I upload a wedding as one gallery or split it up?

Upload the whole day as one event so face matching crosses every part of it. Use folders inside that event if the couple wants ceremony-only or reception-only views — matching still runs across the full set.

How do wedding guests find their own photos?

They open the gallery link you share, take a quick selfie, and instantly see every photo they appear in across the whole day — no app and no account required.

Can I keep a wedding gallery private?

Yes. Set the gallery to private and it is locked behind a PIN, so only guests you share the code with can view or search. You can also set it to expire after a chosen window.

Step 1 — Detection: finding faces in every photo

When a photographer uploads an event, each photo is processed by a face-detection model. Its only job is to answer "are there faces here, and where?" It draws a box around each face it finds — one photo of a group dinner might contain twenty. This runs automatically in the background after upload; the photographer does nothing.

Step 2 — Embeddings: turning a face into numbers

For each detected face, the system computes a face embedding — a list of numbers (a vector) that captures the distinctive geometry of that face. The key property is that two photos of the same person produce embeddings that are close together, while different people produce embeddings that are far apart. Crucially, an embedding is not a photo and you cannot reconstruct someone's face from it; it is a mathematical fingerprint used only for comparison.

These embeddings are stored in a database designed for similarity search, so that "find the faces closest to this one" is a fast query even across tens of thousands of faces.

Step 3 — The selfie: your query

When you, as a guest, open the gallery and take a selfie, the exact same process runs on your photo: a face is detected and turned into an embedding. That embedding is your search query. Nothing about the selfie needs to be perfect — the model tolerates everyday variation in lighting, angle, and expression because the embedding captures identity, not a pixel-for-pixel match.

Step 4 — Matching: nearest neighbours

The system compares your selfie embedding against every face embedding in that event and returns the closest matches — the faces most likely to be you. Those photos are surfaced as your results. Because the comparison is numeric similarity rather than exact matching, it works across motion blur, sunglasses, side angles, and the difference between your selfie today and how you looked at the event.

Why it is fast and why it scales

All the expensive work — detecting and embedding every face — happens once, at upload, in the background. By the time you search, the index already exists, so your query is just a similarity lookup. That is why a guest gets results in seconds even for an event with thousands of photos, and why one gallery can serve hundreds of guests searching independently.

What about privacy?

This is the question worth asking of any face-recognition tool. A few principles that a responsible implementation follows:

• Scoped to one event — your selfie is matched only against the photos in that single gallery, not some internet-wide database. It is not a tool for finding someone across the web.
• Access controls — galleries can be locked to an invite list or PIN, so only intended people can search at all.
• Embeddings, not face libraries — the stored vectors are comparison fingerprints, not a reusable photo archive of your face.
• Expiry and deletion — galleries can be set to close and have their photos and face data purged after a retention window, so the data does not live forever.

The short version: face-matching photo sharing is a focused, per-event search tool. It detects faces once when the photographer uploads, turns each into a private numeric fingerprint, and matches your selfie against just that event. That is the entire trick — and why finding your photos can take one selfie instead of an hour of scrolling.

FAQ

Can someone reconstruct my face from a face embedding?

No. An embedding is a list of numbers describing the geometry of a face for comparison purposes. It is not an image and cannot be turned back into a photo of you.

Does the selfie search look for me across the whole internet?

No. Your selfie is matched only against the photos in the one event gallery you opened. It is a per-event search, not an internet-wide face search.

Does it still work if my selfie looks different from the event?

Yes. Matching is based on a similarity score, not an exact match, so it tolerates differences in lighting, angle, expression, and everyday changes in appearance.

1. Email attachments

Fine for sending three photos to one person. Hopeless for an event. Attachment size limits cap you at a handful of compressed images, every recipient needs to be emailed individually, and nobody can easily find the photos again six weeks later. Email is a message channel, not a delivery system.

2. USB drives or prints

Tangible and nice as a premium keepsake, but they do not scale and they do not help guests. You cannot hand a USB drive to two hundred wedding guests, and even the couple has to plug it in and dig through thousands of files to find anything. Treat physical media as an add-on, not your distribution method.

3. Shared cloud folder (Drive, Dropbox, iCloud)

A big step up — one folder, one link, unlimited size. This is where many people stop, and for a small private group it is genuinely fine. The problem is discovery. A shared folder is an undifferentiated pile: every guest sees every photo and has to scroll through hundreds of strangers to find the ones with themselves in them. There is no privacy granularity either — anyone with the link sees everything, including the candids someone might rather not have public.

4. A traditional client gallery

Purpose-built photo galleries solve hosting, presentation, and downloads properly. They look professional, support high-resolution downloads, and can carry your branding. The gap they historically leave is the same one as the shared folder: organisation is by album or folder, not by person. The gallery still expects each guest to find themselves manually. For a portrait session that is fine. For a 2,000-photo event it is the bottleneck.

5. A face-matching gallery

This is the model built specifically for events with lots of people. It is a gallery — one link, proper hosting, high-res downloads, optional branding — with one addition that changes everything: the photos are indexed by face. A guest opens the link, takes a selfie, and instantly sees only the photos they appear in. No scrolling, no app, no account.

That single feature solves the discovery problem that defeats every other method. One hundred guests can open the same link and each walk away with their own personal set in under a minute. And because access is per-gallery, you can keep it private with a PIN so only invited people get in.

So which should you use?

• Sharing a few photos with one person → email or a direct link is fine.
• A small private group where everyone wants everything → a shared cloud folder works.
• A professional handoff to one client → a traditional client gallery looks the part.
• An event with dozens or hundreds of people who each want their own photos → a face-matching gallery is the only option that does not turn into manual sorting.

The deciding factor is almost always headcount. The more people are in the photos, the more the value shifts from "where do I host this" to "how does each person find themselves." Past a couple of dozen faces, automatic face matching stops being a nice-to-have and becomes the whole point.

FAQ

What is the easiest way for guests to get their own photos?

Share one gallery link and let each guest take a selfie to pull their own matches. It needs no app and no account, and one link serves everyone at the event at once.

Is a shared Google Drive folder good enough for event photos?

For a small private group, yes. For a large event it falls down on discovery and privacy: everyone sees everything and has to scroll to find themselves. A face-matching gallery solves both.

Can I keep an event gallery private?

Yes. A gallery can be locked behind a PIN so only people you share the code with can view or download photos, and access can be set to expire.

This guide walks through a delivery workflow built for speed, and shows where AI face matching collapses the slowest step — getting each individual person their own photos — from hours of manual work down to nothing.

Step 1 — Cull once, decisively

The fastest delivery starts with a fast cull. Do a single pass: reject the obvious technical misses (blinks, missed focus, accidental frames) and flag the keepers. Resist the urge to grade every photo on the first pass — a binary keep/cut decision is faster and you can refine favourites later. For a large event, your goal is to leave culling with one clean set of delivered images, not three tiers you still have to reconcile.

Step 2 — Export at delivery resolution, in a consistent batch

Export your edited set in one batch with consistent settings. A few decisions to make once and reuse on every event:

• Resolution — decide whether guests get web-sized previews, full-resolution originals, or both. Offering a smaller preview plus an optional original download keeps galleries fast without limiting what clients can keep.
• Format — standard JPEGs are the safe default for delivery; everything renders them and they upload quickly.
• Naming — keep a consistent filename scheme. It makes folders predictable and your archive searchable later.

Step 3 — Upload into one gallery per event

Upload the full edited set into a single gallery for the event. Bulk drag-and-drop is the norm; the gallery does the heavy lifting of hosting, thumbnailing, and serving. If you want browsable sections — "ceremony", "reception", "day two" — use folders inside the one event rather than spinning up separate galleries. Keeping everything under one event matters for the next step: face matching should run across the whole take, so a guest who appears in two folders still finds every photo of themselves in one search.

A practical tip: turn on duplicate detection if your platform offers it. Re-uploading the same files (a common accident when a batch is interrupted) then gets skipped automatically instead of cluttering the gallery and counting against your storage.

Step 4 — Share one link, not many files

The old model — emailing albums, mailing USB drives, or sending one zip per person — does not scale past a handful of recipients. Modern delivery is a single shareable gallery link. You send one link over WhatsApp, email, or SMS, and every recipient opens the same gallery on any device. No app install, no per-person export.

Decide on access at this point too. A public link is frictionless for a casual party; a private, PIN-gated gallery is the right call for anything sensitive, where only people with the code get in.

Step 5 — Let guests find themselves (this is the big one)

Here is where traditional delivery breaks down. In a wedding or conference gallery of thousands of photos, no individual wants to scroll past hundreds of strangers to find the dozen frames they are actually in. And you definitely do not want to hand-sort the gallery into a personal folder for each of two hundred guests.

AI face matching removes that step entirely. When you upload, the system detects and indexes every face. A guest opens the link, takes a quick selfie, and instantly sees only the photos they appear in — usually within seconds. You did zero tagging. They did zero scrolling. The "do you have any photos of me?" email never gets sent because the answer is already self-service.

Step 6 — Make repeat downloads self-service

Delivery is not finished at the first handoff — guests come back weeks later wanting that one shot again. A self-service gallery means they re-open the link and re-download without involving you. Offer a bulk "download all my matches" option so someone who appears in fifty photos gets a single zip instead of saving fifty files by hand.

The time math

On a typical large event, the per-guest delivery layer — sorting, tagging, packaging, and fielding follow-up requests — is the part measured in hours. Culling and editing remain your craft and your call. But the distribution layer is pure admin, and it is exactly the part that automates cleanly. Upload once, share one link, and let face matching do the sorting. That is the difference between delivery taking an afternoon and delivery taking the rest of your week.

FAQ

What is the fastest way to deliver photos to a large group?

Upload the full set into one gallery and share a single link. With AI face matching, each person takes a selfie and instantly gets only their own photos — so one link serves hundreds of people with no per-person packaging on your end.

Do clients need an app or account to view their photos?

No. A modern gallery is a web link that opens in any mobile browser. Guests find and download their own photos without installing anything or creating an account.

How do I avoid manually tagging who is in each photo?

Face detection and matching run automatically when you upload. There is no manual tagging step — the system indexes every face and lets each guest self-identify with a selfie.