Hand out your event photos with a single link

A wedding is a private distribution to a known list of relatives. An event is the opposite: a public-ish distribution to a crowd whose contact details you mostly do not have. You cannot email the photos to people whose emails you never collected, and you should not be collecting them just to send a gallery.

• ·That single difference decides everything else on this page. Your distribution channel is not a message thread, it is signage, a Slack channel, a class group, a newsletter, or a slide at the end of the closing talk. So the link needs to survive being read off a wall by a stranger, on a phone, on venue wifi, without a sign-in step in the way.
• ·It also means your link is effectively semi-public from the moment you print it. Plan for that rather than pretending otherwise, the consent section below is not boilerplate, it is the part organisers most often wish they had read first.

The printed code is the highest-yield thing on this page, because it reaches the people no digital channel does. It is also the easiest thing to get wrong, and you only find out after the print run.

• ·Size to distance, roughly 1:10. A code people scan from arm's length (about 30 cm) wants to be around 3 cm across; a code on a sign read from three metres away needs to be about 30 cm. Codes are almost always printed too small.
• ·Leave the quiet zone. A blank margin about four modules wide around the code. Printing it hard against a coloured border is the single most common scan failure.
• ·Contrast beats branding. Dark code on a light background. A code printed in your brand's mid-tone teal on a photo background will fail on half the phones in the room.
• ·Test the real print, not the screen mock. Scan the proof at final size, in dim venue lighting, at an angle, with an iPhone and an Android.
• ·Put the URL underneath in readable text. Some people will never scan anything, and some venue wifi captive portals break the in-app scanner.
• ·Because the code encodes the link and not the files, a sign you printed in March still works after you have replaced every photo behind it. That is what makes signage worth paying to print.

Attendees do not want the whole event. They want the three photos they are in, and they want them now, standing in a corridor on congested conference wifi. A gallery that forces a single bulk ZIP is exactly the wrong shape for that: it is the largest possible download to get the smallest possible thing.

• ·Every photo in the album also has its own link, so someone can open one frame, save it, and be done, a few megabytes rather than a few gigabytes. And what they save is the original file, not a recompressed preview, which matters when the marketing team wants the keynote shot for a post.
• ·Practical tip for conferences and school events: upload a web-resolution set (long edge around 2,500px) for the public album and keep the full-size originals for the two or three people who ask. It cuts the storage bill, loads faster on bad wifi, and nobody notices the difference on a phone.

Sooner or later one attendee will ask you to remove one photo. Sometimes it is vanity, sometimes it is a safeguarding or domestic-safety reason and you will not be told which. Plan the mechanism now so the answer can be 'done' rather than 'I'll look into it'.

• ·One photo: delete that file from the album. The album link is unchanged and the per-photo link stops working immediately.
• ·The whole set, urgently: disable the link from your dashboard. It goes offline at once and you can re-enable it after you have edited the set.
• ·For anything involving children, do not use an open link. A school or youth-club event should sit behind a password shared through the same channel you would use for any other restricted information.
• ·Say up front where the photos will go. A line on the sign, 'photos from tonight will be posted at this link', is both good manners and your best defence when someone objects later.
• ·We are honest about the limit here: once a photo has been open on the internet, taking it down stops future access but cannot recall what somebody already saved. That is true of every sharing tool. It is an argument for curating before you publish, not for a different platform.

A running club, a monthly meetup, a school with a termly newsletter, a market stall that does the same fair four times a year, all of them print or publish something once and then need it to stay correct. Because you replace the contents rather than the address, one printed sign or one pinned Slack message can carry a whole season.

• ·Two ways to run it, and they suit different groups. One rolling album, 'club photos', that you keep adding to and occasionally prune, so there is exactly one link anyone ever needs. Or one album per event, with the pinned message updated each time, which keeps each set findable and small. Rolling is better for signage; per-event is better for anything you want to reference later.
• ·Either way you get a view count per link, which over a season is genuinely useful: it tells you whether the sign by the exit is being scanned at all, or whether everybody comes in through Slack.

This is a distribution surface, not an event-photography platform, and the gap matters most for organisers.

• ·No attendee uploads. There is no guest-contribution feature at all. If you want a shared pool everyone drops into, you need a tool built for that, we will not fake it with a submission form we do not have.
• ·No face recognition and no per-attendee filtering. Everyone who opens the link sees the same album; nobody gets a personalised 'photos of you' view.
• ·No print sales, no photographer storefront, no galleries gated behind a purchase.
• ·No automatic RSVP, ticketing or attendee-list integration. You are pasting a URL into whatever you already use.
• ·What we are good at is the last mile: getting a curated set in front of a crowd, on a phone, in one tap, without an account. If that is the part that keeps failing for you, this fixes it. If your problem is collecting photos from a hundred people, it does not.