One photo album the whole event fills
The shared album is a single event-wide gallery that any attendee can add to from their camera or their camera roll, viewed full screen inside the app. The organizer decides in advance whether photos appear immediately, wait for approval, or come only from the team.
What this looks like in the product
One album for the event, not one per session, which is why it fills up instead of sitting empty in fourteen places.
- One album per event
- Everyone adds to the same album from camera or library, in a full-screen viewer for the whole event.
- Three moderation modes
- Open, moderated, or admin-only, chosen per event rather than per photo.
- Auto-hide on report
- A reported photo disappears from the album immediately and waits for a human, rather than staying up during the review.
- Approvals queue
- A console page where held and reported photos are approved or removed.
- End-of-event archive
- The Reports page keeps the album with the rest of the event record.
The Photos tab
- Add from camera
- Add from your library
- The event album, newest first
- Full-screen viewer
- Report a photo
Why one album and not a gallery per session
The instinct is to give every session its own gallery, and it is the wrong instinct. A conference with forty sessions gets forty empty albums and one that has eleven photos in it, because contributing requires the attendee to first decide where the photo belongs.
One album removes that decision. The attendee taps add, the photo is in the event, and the album is full by the coffee break because the friction is gone. What you lose is per-session organisation, and in practice organizers who ask for it are usually trying to solve a different problem: they want the photos afterwards, which the end-of-event archive gives them anyway.
The QR route matters for the same reason. An attendee who has the app already has the album. Someone who has not installed anything reaches the event through the link in their invite, which is the same claim link that gets them everything else. There is no separate album URL to print, no second account, and no upload page that asks a stranger for an email address.
Three moderation settings, and how to choose
This is the only decision worth making carefully before the event opens, because changing it halfway through is confusing for attendees who have already learned what happens when they post.
| Mode | When a photo appears | Use it when |
|---|---|---|
| Open | Immediately | Internal events and audiences who know each other. Highest volume, lowest overhead. |
| Moderated | After an admin approves it | Public or press-facing events, and anything with a client in the room. |
| Admin only | Only the team can post | Formal events, regulated industries, and anywhere an attendee photo is a problem in itself. |
Independently of the mode, any attendee can report a photo, and a reported photo is hidden from the album straight away rather than staying up while somebody decides. That ordering is deliberate: the cost of briefly hiding an innocent photo is an apology, and the cost of leaving a genuinely bad one up for twenty minutes at a conference is considerably more than that. Approvals and removals record the photo's new state, but not which admin made the call.
What the organizer controls
- Whether the album exists at all
- Photos are a per-event switch. A board offsite that wants a schedule and nothing else turns it off and the tab disappears.
- The moderation mode
- Set before the doors open, applied to every photo in the event.
- The approvals queue
- A console page holding everything waiting or reported, with approve and remove.
- What leaves with you
- The end-of-event report archives the album alongside the Q&A and poll record, so the photos are not stranded behind a login you stop paying for.
What this is not
Most searches for event photo sharing are looking for a wedding product, and the differences are worth being blunt about.
- No physical photo wall, no mosaic display and no photo-booth hardware. This is an album in an app.
- No face recognition, no automatic tagging and no per-person galleries assembled by matching faces.
- No printing, no photo products and no downloads-for-sale.
- No public web gallery. The album lives inside the event, which is the point for a corporate audience and a limitation for a public festival.
- No unlimited video. This is a photo album.
Where a shared album is worth switching on
Multi-day conferences, where the album becomes the thing people scroll on the flight home. Internal sales kickoffs and all-hands events, where photography by staff is a genuine part of how the event is remembered and there is no reason to moderate it. Association annual meetings, where the album quietly does the job a paid photographer used to do for the members' magazine.
It is worth switching off for anything regulated, anything under NDA, and any event where a photograph of who was in the room is itself sensitive.
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
Do attendees need the app to add photos?
To add a photo, yes, because the flow uses the phone's camera and library from inside the app. Viewing works wherever the attendee is, and the invite claim link is the same one that gets them into everything else, so there is no separate album sign-up.
Can we require approval before photos appear?
Yes. Moderated mode holds every photo in the console approvals queue until an admin releases it. Admin-only mode goes further and lets nobody but the team post at all. Both are set per event before the doors open.
What happens when someone reports a photo?
It is hidden from the album immediately and waits in the approvals queue for a person. Hiding first and reviewing second is deliberate, because the two mistakes are not symmetrical: briefly hiding a fine photo costs an apology, and leaving a bad one up during a keynote costs considerably more.
Do we get the photos afterwards?
The end-of-event report archives the album along with the Q&A and poll record. Attendee content is retained for the event plus one year, or until the attendee asks for deletion, whichever is sooner.
Is there a limit on how many photos an event can hold?
There is no per-event photo cap in the product. The practical limits are the venue's uplink on the busiest afternoon and the moderation effort if you have chosen moderated mode for a three-hundred-person event, which is a staffing question rather than a storage one.
Keep reading
Features that pair with this
Event types that lean on this
See it in your own event
Your first 50 attendees are free on every event, so the smallest version of this costs nothing to try.