What the platform actually does.

01 — Search by Selfie

Nobody scrolls ten thousand photos.

The reason guests never download their photos isn't that they don't want them. It's the scroll. Selfie search removes it: a guest takes one photo of their own face and gets back every frame they appear in, ranked by confidence, in under half a second.

1. Embeddings are computed on uploadAs frames land, faces are detected and turned into vectors. This happens once, in the background, while you're still uploading.
2. The selfie never leaves as a fileThe guest's camera frame is embedded in the browser, sent as a vector, matched, and discarded. There's no selfie sitting in your bucket.
3. Results come back rankedMatches are ordered by cosine distance, with a confidence cut you can tune per event — tighter for a corporate shoot, looser for a low-light sangeet.

Edge cases handled: side profiles, veils and dupattas, sunglasses, and groups of thirty. Frames below the confidence cut land in a “maybe” tray the guest can open, instead of being silently dropped.

SnapSync — direct-from-camera upload

Skip the laptop. The camera uploads itself.

Most cameras built for professional work (Canon, Nikon and Sony bodies with built-in or add-on FTP/wireless transfer) can push images straight off the card over FTP as they're shot. SnapSync turns that into a direct line to the gallery — no laptop, no card swap, no end-of-night upload queue.

1. Apply it per eventTurn SnapSync on for a specific event from the dashboard — it's scoped to that one gallery, not your whole account.
2. We issue an FTP user for that eventA host, a username and a password, generated the moment you enable it — valid for that event only.
3. Punch it into the camera's FTP settingsStandard camera FTP transfer setup — host, port, username, password, and a destination folder.
4. Shoot. It lands in the gallery.Every frame the camera transfers shows up in that event's gallery within moments — derivatives generate the same way a browser upload would.

03 — Galleries that load

Ten thousand frames that scroll like ten.

The guest gallery is a virtualized React grid: only the rows in view exist in the DOM, and images are requested from an AVIF→WebP→JPEG ladder sized to the device's actual pixel ratio. A 10,000-frame gallery holds about 60 nodes at any moment.

1. Windowed renderingRows are recycled as you scroll, so memory stays flat whether the event has 400 frames or 40,000.
2. Correct format, correct sizeA 6.1" phone never downloads a 45-megapixel file. Blur-up placeholders hold layout so nothing jumps.
3. Works on bad wifiThumbnails are prefetched a screen ahead; a failed request retries without losing scroll position.

Ten minutes from registrar to live.

1. Pick the addressA subdomain of a domain you already own — photos.yourname.com — or a new domain pointed at us entirely.
2. Add one CNAMEWe give you the exact record. Paste it at your registrar and hit verify.
3. Certificate issues itselfUsually inside ten minutes, renewed automatically every sixty days. Clients never see a certificate warning.
4. Everything moves acrossPortfolio, galleries, download pages and notification emails all serve from your address. SnapUp's name appears nowhere a client can see.

06 — Rights, downloads & watermarks

Delivered, not leaked.

You decide what leaves the gallery and at what size. Each event carries its own rules, and the client's contract terms travel with the files.

1. Resolution tiersSocial-sized free, full-resolution behind a PIN, print files on request — set per gallery or per sub-gallery.
2. Watermarked previewsYour mark, your opacity and placement, applied on the fly to preview derivatives only.
3. Licence travels with the fileUsage terms written into IPTC metadata on download, so credit survives the family group chat.
4. Takedown in one clickPull a frame, a person, or the whole gallery — including anything already served from the CDN.