Build the collection
Put your shared event album together before the invitations go out
Before you print a code or send a request, assemble the place where the pictures will arrive. This guide explains how to make a shared event photo album from the host's side: define the occasion, create the collection, choose its behaviour, test it and publish one dependable address.
Collecting everyone's pictures into one place, whatever the occasion.

Think of the album as a small hosting project rather than a folder you happen to share. Someone needs to recognise it, understand what belongs in it and know what will happen to their contribution. A little assembly work prevents a familiar sequence of fixes: renaming the occasion after the sign is printed, explaining that the gallery is hidden after people ask where their pictures went, or discovering that the chosen package cannot provide the download you planned to keep. You do not need a finished guest list to start. You do need a clear purpose and a responsible host.
Write the album's boundaries in one sentence
Decide which occasion the collection represents. A family reunion album might include the afternoon picnic and the evening meal because they belong to the same gathering. It need not become the destination for every family photograph from the last decade. Write a sentence such as: this collection is for pictures taken during our Saturday reunion, including the people setting up and travelling home together. That sentence becomes a useful test when somebody asks whether an older photograph, an unrelated holiday clip or a commercial image belongs in the collection.
Candid Photos provides one collection per event. Calling it an album does not mean that you can create separate internal albums for each activity. If you want a detailed structure for a future printed book, record that idea separately and arrange downloaded copies later. At this stage, the important boundary is social: what are you inviting people to contribute, and who will receive it? Decide whether absent relatives may send relevant messages, whether videos are welcome and whether pictures of children need additional care. The narrower brief is easier to communicate, easier to size and easier to review. It also gives the eventual archive a clear identity rather than leaving a future reader to guess why unrelated files are together.
Create the host account and name the occasion
Choose a durable organiser identity
Create the host account using an address you can access after the event. This account manages the collection; it is not something guests borrow to contribute. If a friend is helping with invitations, send them the guest link once it is ready, not the account password. Decide who will remain responsible after the celebration is over.
Enter a recognisable event name and date
Use words a guest will recognise from the invitation. Include enough context to distinguish this occasion from another event held by the same group. Check the date carefully because the included online period is tied to the event date. A test date left in place can undermine the timing you thought you had planned.
Pick the nearest honest event type
The creation options include wedding, birthday, graduation, baby shower, anniversary, corporate event, conference, family reunion and other. For an occasion outside that list, use other and name it clearly yourself. A neighbourhood supper does not need to pretend to be a conference to have a collection.
Keep the setup notes with the organiser
Record the chosen name, the person managing the account and the intended collection deadline in your own event notes. These are planning records, not extra fields you must find in the product. They make it possible to check the finished album against the original brief before sharing its address.
Size the collection before adding decorations
Estimate from likely contributions rather than attendance alone. For example, 30 people sending five photographs each would produce 150 photos. That is only a planning example, not a prediction of what your guests will do. Add a separate estimate for clips and allow headroom. Ten long videos can matter more to storage than many ordinary photographs. The photo count, video count and storage allowance are separate limits, so a collection can meet one ceiling before reaching another. Do not treat a generous contributor allowance as unlimited media capacity.
- A rehearsal collection
- Preview allows 20 photos from up to 10 contributors, with 500 MB and seven days online. It accepts no video and has no downloads. Use it to learn the setup and guest experience, with test material whose absence from a downloadable archive will not matter.
- A modest event album
- Gather is $19 per event for 200 photos, 30 videos, 5 GB and one month online. It includes a written guestbook and standard downloads. It is a reasonable starting point when those limits and that download quality match the collection you have actually planned.
- A larger or longer project
- Celebrate is $39 for 750 photos, 100 videos, 20 GB and three months, with original-quality downloads, a video guestbook and a slideshow. Keepsake is $69 for 2,000 photos, 300 videos, 50 GB and six months, with two extra managers. These are one-off US-dollar prices per event.
Set receiving and viewing as separate decisions
Choose whether contributors should also browse the shared collection. With the public gallery switched off, the guest page is upload-only. That can suit a host who wants to collect first and decide later which pictures to share. It can also surprise people who expected to see everyone else's images, so explain the choice in the invitation wording. With guest viewing enabled, remember that the unlisted link can be forwarded. It is not an authenticated guest list, and a supplied contributor name does not establish who is looking at the gallery.
Approval is another host switch: turn it on if submissions should wait for acceptance. Decide who will do that review and at what times. Do not turn on a queue and then assume a screen or gallery will fill while nobody checks it. Guestbook availability is a separate consideration again. Gather includes written messages; Celebrate and Keepsake include written and video messages. Preview can add a written guestbook for $9, and Gather can add a video guestbook for $9. Buy and enable only the experience you intend to invite. A photo-only request needs less explanation than a page asking guests to choose between pictures, written wishes and recorded messages.
Prepare the words that make the album usable
Give the collection a purpose
In your guest-facing introduction or accompanying message, say what you hope to receive. For the reunion example, ask for pictures of the picnic, the meal and the helpers who made the day possible. This gives people something concrete to find in their camera library without prescribing a long shot list or turning attendance into photography work.
Describe the audience
Tell contributors whether other link holders can browse or whether only the host is receiving submissions through an upload-only page. Ask people not to send pictures they know another person would object to sharing. Include a simple way to contact you about removal, especially when different families have different expectations about children's images.
State a useful deadline
Choose a date earlier than the collection's closing date, leaving time for late replies and your download checks. Put the exact day in the message rather than saying soon. This is your collection request deadline, not a claim that the software will close uploads on that day or automatically remind everyone.
Keep the opening request short
Put the longer explanations in a follow-up message only where needed. The first instruction should fit comfortably beside the link: choose a few favourites from this occasion and send them here by the stated date. A guest arriving from an invitation should recognise the name, understand the purpose and know the next action without reading your planning notes.
Rehearse the complete album, including its ending
Use an independent guest view
Open the guest address on a phone that is not signed into the host account. Ask someone to provide their name and submit an expendable picture. Guests do not need an app, account or password. If the person needs your credentials, stop and check that you copied the guest address rather than a management link.
Check what your settings actually show
Look for the submitted item in the host view. If approval is enabled, make the intended decision, then examine the guest page again. Check that an upload-only arrangement really behaves as the words in your invitation suggest. The test should catch mismatches in your explanation as well as technical problems.
Test any promised extra
If you intend to show a slideshow, test the display separately rather than treating a successful upload as proof the venue screen is ready. A slideshow is included with Celebrate and Keepsake and is an optional $9 add-on for Preview or Gather. If no display is planned, skip this purchase and this test.
Verify the retrieval route
On a paid collection, check the available download workflow and open a downloaded test file on the computer you expect to use later. Preview cannot supply that test because it has no downloads. Confirm that you have disk space and an independent destination for the final archive before relying on the gallery as your only copy.
Launch one address in a deliberate order
Before broad sharing
Send a small proof
Give the finished link and your proposed wording to one helper. Ask them to check the event name, date, purpose and guest journey. Correct the setup before copying the address into invitations and printed material. One calm proof is cheaper than telling several groups that the first message contained the wrong link.
At launch
Use matching digital and printed routes
Send the same guest link through your chosen invitation channel and use its matching QR code on signs. The dashboard can print four table stands on one A4 sheet. Scan a finished stand, not only the code on your monitor, to verify the exact paper guests will use.
During the event
Invite without taking over
Make one brief announcement and place the code where someone has time to act. Do not repeatedly interrupt conversation to check who has uploaded. A helper can explain the process, but the album should support the occasion rather than become another scheduled activity everybody must complete.
After the first contributions
Watch the practical limits
Check receipt, any review queue and remaining capacity. If people are sending more clips than you expected, adjust the request or review the available capacity options before promising space for everything. Keep later reminders on the same destination so guests do not wonder whether a newer message means a different collection.
Finish with an archive rather than an abandoned tab
When the request deadline arrives, look for missing moments rather than simply counting files. You may have plenty of pictures from dinner and none of the group arriving. Ask the person likely to have the missing view with a specific, polite message. Avoid asking everybody to resend everything. If a guest has already supplied a good set, thank them without converting your wish for completeness into a new obligation. A finished album is a useful representation of the occasion, not proof that every camera has been emptied.
Retrieve the collection before its online period ends. Paid plans offer whole-collection and individual downloads, with quality depending on the package. Rejected submissions are excluded from the archive, so review intentional exclusions before deciding what your saved collection contains. Extract the download, open representative photos and videos, then copy the files to a second storage destination. Save a short description in your own archive records with the event name, date and who organised it. You can later create a favourites folder on your computer without altering the complete downloaded set. That is the point at which the hosting task becomes a finished keepsake rather than an active website you are hoping somebody will remember.
Album assembly questions, answered directly
Do I have to collect pictures before creating the album?
No. You can prepare the event collection and test it with a harmless sample before inviting contributions. Keep your scope, event date and online period in mind so the test does not become an unmanaged store for important files.
Can I build a separate section for each part of the day?
The product provides one collection per event, not internal albums for separate activities. Invite the relevant moments into that collection, then arrange downloaded copies into your preferred folder structure on your own computer if you need a more detailed archive.
Will guests need the account I used to create it?
No. The host account is for management, while guests use the event link or QR code without an app, account or password. Never put the host sign-in or credentials on a table card.
When should I consider the album finished?
When you have checked the received material, made any necessary review decisions and verified an independent saved copy. The date the online collection closes is a deadline, not a substitute for that finishing work. Leave time to resolve a failed download or ask for a missing original.
Build the destination before asking for pictures
Start with the event name and one sentence describing what belongs in the album. Create the host account, choose the viewing arrangement and test a contribution before sharing widely. You can then invite guests into a collection that is ready for them, with a clear plan for keeping what arrives.
Event photo sharing
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.