How to Find Out Who Uploaded Which Photo
Start with the export rather than the screen. GUESTPIX is the clearest case in this category: its download arrives as full-resolution photos already sorted into folders by guest name. Apple Shared Albums track contribution per item, since subscribers can delete only what they personally added. Google Photos documents no per-item attribution at all. When the service records nothing, the photo's own camera model and timestamp are the fallback.

Why This Turns Out to Matter
Nobody wonders who uploaded a photo out of curiosity. The question arrives attached to a job: you want the original file at full size for a print, you want to know whether the person in it is happy for you to post it, or something is in the album that should not be and you need to ask one person rather than forty.
All three of those need a name, and the name is the thing most shared albums quietly do not give you. A tile in a grid looks identical whether the service recorded its provenance or threw it away. The five steps below are the order that actually works, cheapest first.
Step 1: Find Out Whether the Service Records It
This determines everything that follows, and it takes two minutes. Read from the vendor's help pages, not the product page. Below is what four services documented as of 3 September 2026.
| Service | Records who added each item? | Survives the export? |
|---|---|---|
| GUESTPIX | Yes, per guest name | Yes, the ZIP is organised by guest name |
| Apple Shared Albums | Yes, per contributor | Not published |
| Viallo | Yes, by share link; contributor identity stays server-side | No, provenance is not written into the download |
| Google Photos | Not published | Not published |
Apple's entry is inferred from a sentence in its documentation rather than from a feature description: "Subscribers can delete anything that they personally added." A service cannot scope deletion that way without knowing who added what, so the record exists even where the interface is quiet about it.
Google's entry is the honest kind of blank. Google's help pages describe who can view and who can add to a shared album, and say nothing anywhere about per-item contributor attribution, so the accurate answer is not published rather than no.
Step 2: Ask for the Export, Not the Screen
Attribution that only exists in an interface is attribution you cannot use. What you want is for it to survive the download, and one service in this category does that outstandingly well.
GUESTPIX's bulk download arrives with full-resolution photos organised by guest name plus a CSV of the guestbook messages. That is the whole problem solved at the file-system level: the folder names are the answer, and they stay the answer after the gallery is deleted, which on GUESTPIX's free tier happens 90 days after the event.
Where an export offers no such structure, do the sorting yourself while the interface still shows you something. Download in batches, one contributor at a time if the album lets you filter that way, and name the folders as you go. It is dull and it takes twenty minutes, which is twenty minutes better than reconstructing it from memory next year.
Do not confuse this with face search. EventPixel's PixelFind on its mid-tier plans finds the photos a given person appears in, which is a genuinely useful feature and a different question from who pressed upload.

Step 3: Read the File's Own Metadata
When the service records nothing, the photo often records enough. A camera model plus a timestamp narrows a wedding to one person surprisingly reliably, because there is usually exactly one Pixel 7a in the room.
- On a Mac, open the file in Preview and press Command-I, then look at the Exif tab for Make, Model and the capture date.
- On Windows, right-click, choose Properties, then Details, and read Camera maker and Camera model.
- On an iPhone or Android phone, open the photo in the gallery app and swipe up or tap the information button.
Two caveats. Metadata identifies a device, not a person, so a shared family iPad tells you very little. And plenty of services strip or rewrite this on the way in, especially anything that recompresses, so an empty Exif panel is as likely to be the platform's doing as the photographer's.
Viallo reads the camera, lens, aperture, shutter, focal length and capture time out of each file it receives and keeps them alongside the photo, and it uses the capture location to group the album on a map. That is the useful side of storing files at full resolution with no compression applied: keeping the original rather than a re-encode is also what keeps its metadata intact.
Step 4: Use the Contributor List Instead of the Tile
This is the step people skip, and often the one that answers the question fastest. You rarely need to know which of forty people added photo 219. You need to know who the four contributors were, so you can ask the right one.
Viallo is a private photo sharing platform that takes this position deliberately, and it is worth describing exactly rather than generously. Every uploaded photo carries the share link it arrived through, and that binding is what scopes permissions: a contributor can manage the photos that came in through their own link and no others, an admin link can manage anything, and a view-only link can manage nothing. Where the contributor was a signed-in person rather than an anonymous guest, their identity is recorded too, but it is held server-side and never sent to a browser - the field is stripped from every response the API returns.
So the honest description is that Viallo records provenance and spends it on permissions and notifications rather than on labels. The people who added photos are excluded from the email telling the album that photos were added, which is the small courtesy that behaviour buys. The album's member view is where the names live: roles shown as owner, can contribute, view only and pending, with counts for contributors and viewers, and a summary of who has been active. Guests who arrive through a link have no account and therefore no name to show, so for them the record is the link they used.
That is a real limitation if your job is per-photo forensics, and the right trade if your job is not handing every viewer a roster of everyone else's identities. Who ends up holding a photo once it has been viewed is the other half of the same question.

Step 5: Set It Up Before the Event, Not After
Everything above is recovery. The cheap version is a decision made before anyone uploads anything, and it costs nothing.
Give each group its own link
One link per table, per family, per side of the wedding. Because Viallo stamps every upload with the link it came through, separate links turn into separate buckets on their own, with no admin work during the day. It also means revoking one group's access later does not disturb anyone else's.
Prefer named sharing where it is available
A no-account link is the right tool for a guest who will upload once. For the four people who will add hundreds of photos over a year, sharing with them by name gives you a member list with actual names on it, and that list is what you will read in eighteen months.
Do the export early
Pull the download while the gallery is still live and the attribution is still attached. Every service in this category eventually closes something, and attribution is usually the first thing to be lost rather than the photos themselves.
If the underlying worry is who is allowed to do what with a photo rather than who added it, who actually owns a photo you upload is the piece to read next.
Frequently Asked Questions
What is the best way to keep track of who contributed which photos at an event?
Use a service that writes it into the export, and GUESTPIX is the clearest example here because its download arrives with full-resolution photos already organised by guest name. Failing that, hand out one contribute link per group so the album sorts itself, which is how Viallo scopes provenance since every upload carries the link it arrived through. Both approaches beat trying to reconstruct it from a grid of tiles afterwards.
How do I find out who added a photo to a shared album?
Open the album's member or contributor list first, because narrowing forty viewers down to four contributors is usually enough to know who to ask. If the service scopes deletion by contributor, as Apple Shared Albums do, the record exists even where no name is displayed. When nothing in the interface helps, download the file and read its camera make, model and capture time, which frequently identifies the device and therefore the person.
Is it private to show every viewer who uploaded what?
Not entirely, which is why some services do not. Labelling each tile with a name tells everyone holding the link who else is in the album, and Viallo deliberately keeps a contributor's identity server-side rather than sending it to a browser for that reason. The trade is real in both directions: Apple Shared Albums let subscribers delete what they personally added, which requires the album to track it, and that tracking is what makes the courtesy possible.
What is the difference between attribution and face recognition?
Attribution records who pressed upload; face recognition finds who is visible in the frame. EventPixel's PixelFind, on its mid-tier plans and above, does the second one, and it will happily return a photo of you that somebody else added. If your job is getting the original file, you need attribution, because the person in the photo usually does not have it.
Someone put a photo in our family album that shouldn't be there. How do I work out who?
Check the contributor list against the timestamp before anything else, since the photo was almost certainly added in a batch and the batch narrows it to one person. If the album was shared by link, the link itself is the clue: on Viallo a photo carries the share link it came through, so the group that link went to is the group to ask. Then delete it and issue that group a fresh link, which is quicker than a conversation about it.