Photo collection
How to Collect Photos From a Group of People
The practical options for gathering photos from multiple people at a birthday, wedding, reunion or any group event. Each approach works differently, and which one you choose depends on the size of the group, the type of event and what you plan to do with the photographs afterward.
How-to walkthroughs and honest comparisons of the options.

Every group event produces photographs, and those photographs end up on a dozen different phones. The person organising the event will spend the following weeks asking for them, receiving them through various channels in various formats at various times, and eventually assembling something that is never quite the full record of what happened. The problem is not a shortage of photographs. The problem is a shortage of a system for collecting them.
There are several practical approaches to group photo collection, and they differ significantly in how much work they put on the organiser versus the contributors, how much quality they preserve, and what happens to the photographs once they are collected. This guide works through each one honestly.
Option one: a shared album on a phone platform
The first tool most people reach for, and the one with the most familiar failure modes.
Apple's Shared Albums feature and Google Photos' shared albums both let one person create an album and invite others to contribute. The invite goes out by name, email or phone number, and contributors can add their photographs directly from the same app they already use. For small groups where everyone uses the same phone ecosystem, this works well.
Where it works
A group of ten to fifteen people who all use iPhones, or all use Android phones, and who are already comfortable with photo apps. A family trip, a small birthday dinner, an office outing. The organiser sends one invite; contributions arrive without further effort.
Where it breaks down
A mixed group of iPhone and Android users, or anyone who does not have the right app, or anyone who is not comfortable managing settings on their phone. An invite that arrives in an unfamiliar app will be ignored by a significant portion of contributors. At a large event — a wedding, a reunion of fifty people — the failure rate on shared album invites is high enough to make the approach unreliable.
Quality
Shared albums often compress photographs. iCloud Shared Albums, for example, do not preserve original quality. If original-quality files matter — for printing, for giving to a photographer — a shared album may not deliver them.
Option two: a WhatsApp or messaging group
The simplest possible approach: a group chat where people send their photographs. It works because the tool is already in everyone's hand and nobody needs to install anything or accept an invite to a new service.
What group chats are good and not good for
Group chats work for
- Small groups (under twenty) who already share a chat.
- Events where the photographs are for immediate sharing, not archiving.
- Situations where quality is not a priority.
- Situations where the photographs do not need to be organised by contributor.
Group chats break down for
- Large events where dozens or hundreds of people are contributing.
- Events where the photographs need to be archived and found later.
- Situations where original quality matters — WhatsApp compresses images significantly.
- Events where photographs from different contributors need to be distinguished.
WhatsApp compresses photographs on send, by default. The file that arrives in a chat is smaller and lower quality than the file that left the sender's phone.
Option three: a file request via Google Drive or Dropbox
Google Drive and Dropbox both have file request features that let the organiser create a folder and send a link. Contributors upload their files to the folder without needing to have an account of their own (for Dropbox file requests) or by uploading to a shared folder (for Google Drive). The files arrive at original quality, in one place, without compression.
File request features compared
- Dropbox file request
- The organiser creates a file request link and shares it. Contributors click the link, choose their files, and upload without having a Dropbox account. Files arrive in the organiser's Dropbox at original quality. The limitation is that there is no contributor identification built in — files arrive with whatever name the contributor's device gave them, which may be a string of numbers.
- Google Drive shared folder
- The organiser creates a folder and sets it to allow anyone with the link to upload. Contributors who have a Google account can add files; those who do not need a workaround. Files arrive at original quality. The same limitation applies: file names are whatever the device generated, and contributor names are only visible if the contributor was logged into a Google account.
- Who this works for
- Groups where the organiser is comfortable with these tools and the contributors are likely to follow a link and upload files. The lack of contributor identification is a real limitation for large groups where knowing who sent what matters.
Option four: a dedicated event photo collection platform
A platform built specifically for collecting photographs from event guests handles the things that the other options handle poorly: contributor identification, original-quality uploads, large-group reliability and no requirement for contributors to have an account.
How a dedicated collection works
The organiser creates a collection
Takes a few minutes. The collection gets a short web address and a matching QR code. The organiser chooses the plan that fits the number of guests and the type of event.
Contributors scan or click
The QR code on a table card or the link in a message opens a browser page. No app download, no account creation. The contributor types their name, selects their photographs or videos, and uploads. That is the whole experience from their side.
Photographs arrive with contributor names
Every submission is tagged with the name the contributor typed. The organiser can see who sent what, which makes the archive useful in a way that an unnamed folder of files is not.
The organiser downloads the full archive
When the collection has finished collecting, the organiser downloads all the photographs and videos at original quality. The archive is theirs to keep, share and store.
The best collection method is the one your contributors will actually use. That matters more than any other technical property.
Choosing the right approach for the size and type of event
Matching the method to the event
- Small gathering (under 20 people)
- A shared album or a group chat is probably enough. Everyone can be invited personally, the volume of photographs is manageable, and the overhead of a dedicated platform may not be justified.
- Medium event (20-100 people)
- A file request or a dedicated collection platform. File requests work if you are comfortable with Drive or Dropbox and do not need contributor names. A dedicated platform is better if contributor identification matters and if you want guests to be able to contribute without navigating a cloud service.
- Large event (100+ people)
- A dedicated collection platform with QR codes on tables. At this scale, shared album invites will fail for a significant portion of guests. A browser-based upload with a QR code is the approach most likely to work for a large mixed audience.
- Events with guests who are not confident with apps
- A browser-based approach requires only a camera app to scan a QR code, and no app download. That is a significantly lower barrier than any approach that requires installing something or logging into an account.
Questions about collecting photos from a group
What is the simplest way to collect photos from a large group?
A QR code that opens a browser page, with no app or account required. At a table of ten, most guests will scan out of curiosity. At a reception with two hundred guests, a QR code on each table is more reliable than any approach that requires a personal invite or an account creation.
How do I know which contributor sent which photograph?
On a dedicated photo collection platform, every submission is tagged with the contributor's name. On a shared album or file request, the file name is usually a device-generated string. If contributor identification matters, a dedicated platform is the approach that provides it.
Do WhatsApp or iMessage photos arrive at original quality?
Not by default. WhatsApp compresses images significantly on send. iMessage sends at reduced quality unless the sender specifically enables the full-quality option. For original-quality photographs, ask contributors to use a file transfer method that does not compress, or use an upload tool that accepts full-resolution files.
Can I collect photographs from contributors who are not at the event?
Yes, if the collection method is accessible remotely. A link shared by message or email works from anywhere. A QR code at the venue works only for people who are there. For events where remote contributors matter, share the link directly in addition to printing codes for the venue.
What is the best way to store the collected photographs afterward?
Download the full archive in the week or two after the event and store it in at least two places: a local copy on your device and a cloud copy on Google Drive or similar. Original-quality files from a large event can be large; check that your storage has enough space before downloading.
One collection for everyone's photographs
Create a guest photo collection for your next event and let everyone contribute through a simple browser page, with no app required.
Guides and comparisons
Put one link on the tables and let everyone contribute.
Create a collection, print the table stands, and the photographs your guests took are waiting for you the morning after. Guests never install anything and never make an account.