A multi-photographer event — 4 photographers covering different areas of a wedding, or 3 photographers covering a multi-stage activation — multiplies output and overlap in the same step. The Instant feature that makes this work is cloud sync: a project lives in the cloud, every shooter's App and the Web Portal see the same project, AI Culling runs across all shooters' frames as one set, and guests get one Global gallery instead of 4 fragmented ones.
How to do it
Create the Instant project once, in the Web Portal — that's where the project, AI settings, export preferences, and branding live. Every shooter's App will pick up the same project from cloud sync.
Have every shooter sign in to the same Instant account or be invited as project members. Mixing personal and project accounts is what causes the "where did my frames go" symptom on multi-shooter events.
Turn AI Culling on at the project level. With 4 shooters firing during the same ceremony or speech, you'll have 3-5x duplicate-moment frames. AI Culling runs across the merged set, not per-shooter, so duplicates are kept or rejected as one decision.
Use the Web Portal as the live monitoring surface — it's where you can see all 4 shooters' captures landing in real time, the AI processing queue, and the gallery as guests will see it. Each shooter focuses on their App; one person watches the Web Portal as the merge view.
Set Auto export at the project level. Every shooter's frames go through the same export pipeline into the same gallery — no manual collation, no merging galleries after the event.
Try it
On your next 2-photographer event, set up a single Instant project in the Web Portal and have both photographers sign in to it from their Apps. Compare against your previous workflow of two parallel projects + post-event merge: time-to-gallery and duplicate count are usually 3-5x better with the single shared cloud project.
Watch out for
Switching projects on the App mid-event. The active project is the only one Auto export runs on — switching away pauses the workflow for that shooter.
Forgetting that all watermark and branding settings sync via cloud — if one shooter "fixes" a watermark, it changes for everyone on the project. Designate one person to own branding changes.
Trying to run 4-shooter projects on slow venue Wi-Fi. Cloud sync needs bandwidth; if the venue's connection is unreliable, plan for staggered upload bursts rather than continuous sync.
Source: Onboarding with Instant