
Gather the crowd's view of the day
Festival photo sharing for the moments spread across the site
A festival unfolds across stages, food areas and quiet corners, so no organiser sees every moment. A shared event link gives invited contributors one place to send photographs and clips from the parts of the day they experienced.
A festival is too spread out for one organiser to see and record everything. The crowd notices a set change at the far stage, the volunteers remember a busy entrance, and the performers see the audience from the platform. Those views are often taken on different phones and stay there unless someone gives contributors a simple place to send them. Festival photo sharing works best when it gathers selected images from people who were already present, without asking every attendee to stop enjoying the programme. The organiser needs to decide who can contribute, how the images will be used and whether the collection is intended for a private planning team or a wider group. One link can simplify collection, but clear expectations matter just as much as the upload page.
Decide whose photographs the organiser needs
A public festival can include visitors, volunteers, performers, vendors and a hired photographer. They do not all have the same reason to send pictures or the same rights to share them. Decide whether the event collection is for the organiser's documentation, a volunteer recap, a community album or a display during the festival. A contributor invitation to staff and partners can be more specific than a public call to every visitor. If photographs will be used for future promotion, explain that purpose and make sure the organiser has permission to use the contributions as intended. A collection tool provides a route for files; it does not grant the organiser rights that the contributor has not agreed to.
Large crowds make it especially important to decide where the address will be distributed. A QR code on a volunteer check-in desk reaches a different group from one printed on every public programme. If you only need photographs from a few teams, send the link directly to those contributors instead of opening the request to everyone. If visitors are invited, use a concise sign that explains what the page is and who will see the pictures. Do not ask people to submit images of strangers for a public gallery without considering consent and event policy. The collection should make the organisers' process simpler while respecting the people who appear in the photographs.
Create an event page that is easy to reach on site
Candid Photos lets a host create one event collection with a short address and matching QR code. A contributor opens it in a browser, provides a name and selects photographs or videos to send. Guests do not install an app, create an account or enter a password. For a festival, the organiser can name the event and share the address with the people expected to contribute. Place a printed code at volunteer check-in or include the short link in an organiser message. Keep a written address as a backup for someone scanning from the same phone that displays the digital programme.
A festival can last a day or span several days, and contributors may be working in different shifts. Let them know whether the same event link stays in use across the programme and when submissions should be finished. If the organiser creates an event for one edition of a festival, give it a name and date that can be distinguished from previous editions. Candid creates one collection per event, not a directory of festival days. If teams need separate access and separate archives for each stage or programme block, decide whether a single event collection fits before setup. A clearly named event is easier for volunteers to recognise than a link forwarded without context.
Plan around crowds, signal and staff workload
Crowds can make mobile connections unreliable, especially around a stage or in a rural site. A QR code opens an online page, but the contributor needs an internet connection to submit a file. Ask the venue what Wi-Fi coverage exists and whether staff can use a dedicated network. Test the guest page at the places where a sign will be used, not only in the organiser's office. If the connection cannot support uploads during a performance, tell contributors they can send files later from home. Avoid a plan that depends on every visitor uploading a large video at the same moment. The organiser can still collect a useful set from volunteers with reliable access and send a follow-up link afterwards.
Choose an owner for the collection who is not already carrying too many tasks. Festival organisers may be coordinating safety, transport, vendors and stage schedules. One person should answer upload questions, review submissions if approval is enabled and download the archive after the event. If another person manages a live screen, make that responsibility explicit and test the display address before gates open. A collection that nobody checks can still receive files, but the team needs to know where they are and who can act if a problem occurs. Put the link, host name, closing date and download owner in the organiser's run sheet. That turns a QR idea into an operational plan.
Write contribution guidance that fits the programme
A sign should tell contributors what to send, where it goes and whether sharing is optional. Name the types of moments that help the organiser: the venue before opening, a performance from the audience, volunteer work, food stalls, decorations or a closing scene. If the organiser only needs a small selection, ask for a few strong images instead of every frame. If video is welcome, say so and note any upload limit from the chosen package. Do not promise to feature every submission on a screen or public account. The organiser may need to review files and choose a set appropriate for the audience. Concise guidance helps a contributor send relevant images and understand what will happen afterwards.
Different teams may benefit from different instructions even when they use the same link. A volunteer can send a photograph of site setup, while a performer may want the organiser to know when and where the image was taken. Ask contributors to identify their team or add a short note when that context is useful. Avoid asking for details the host does not need. If names or captions will be used in a public recap, say that in advance and ask contributors to share only material they are comfortable providing. A good instruction saves the organiser time later without turning a quick upload into a lengthy report from every person carrying a camera.
Choose how public the collection should be
Some festival collections are meant only for a small organising team. Others are intended as a gallery attendees can browse. Decide which audience is appropriate and share the address accordingly. Candid guest pages are not indexed as public search pages and are not listed in a public directory. The host can switch off the guest-facing gallery while leaving the upload page available. That lets a team collect first and decide what to show later. If the event needs a public-facing gallery, make sure the organiser wants that outcome and has considered how people in the images will be treated. A link distributed widely can travel beyond the original group, so consider that before printing it on every public surface.
Approval can hold submissions until the host accepts them before they appear in the gallery or slideshow. This can be useful when a room display is visible to a broad audience, but it creates review work. Assign a staff member, decide how often they will check the queue and describe the process to the team. The guestbook is a separate host setting; turn it on only when written messages serve the event's purpose. Candid's slideshow uses a separate token-gated address for a room screen or projector. Test the slideshow, check what plays when approval is on and make sure the person responsible knows how to manage the display before attendees arrive.
Set file limits with a realistic estimate
The right allowance depends on who contributes and what the organiser wants to keep. Candid Preview includes twenty photos, no videos, 500 MB, ten contributing guests and seven days online. Gather includes 200 photos, 30 videos, 5 GB and one month online. Celebrate allows 750 photos, 100 videos, 20 GB and three months. Keepsake allows 2,000 photos, 300 videos, 50 GB and six months. These are per-event packages with fixed allowances; they are not an unlimited account for a whole festival organisation. Estimate the contributors, number of files and storage needs before inviting people, especially if a large volunteer team is expected to upload clips.
A host should also decide whether the collection is a working record or an archive. A short event recap may need a selection of photographs, while a festival team documenting a full programme may expect a larger volume of material. If there are multiple operational teams, one collection may be too broad unless someone can organise what arrives. Candid does not create separate albums within an event, so do not assume that each stage gets its own folder. Use a clear event name, contributor guidance and a download plan. If the organiser needs a formal asset-management system with permissions per team, find out whether the event collection fits before relying on it.
Download and share the files after the site closes
When the programme is over, the organiser should decide whether files will be kept for the team, shared with contributors or selected for a recap. Candid lets the host download individual files or the event archive. Download quality depends on the package: original-quality downloads are available with Celebrate and Keepsake, standard downloads with Gather, and Preview has no downloads. The host should open the archive, confirm that files are readable and store a second copy separately. If contributors expect to receive the collection, explain who will send it, through what channel and when. The upload page gathers material; the organiser still needs to complete the hand-off.
Candid's included retention periods run from seven days on Preview to one month on Gather, three months on Celebrate and six months on Keepsake, measured from the event date. The service sends warning email before the collection is removed, but the organiser should not wait for a reminder to identify who owns the archive. Add the download deadline to the event run sheet and calendar. If the festival returns annually, save the files in a location the organisation controls and label the archive by edition and date. That makes the next year's planning easier and prevents the previous collection from being confused with this year's event.
A practical collection plan for the festival team
Prepare the link before the site opens
Name the collection and owner
Use the festival edition and date in the event name. Choose one organiser to answer questions, manage settings and download files.
Choose contributors and audience
Decide whether the request is for staff, performers, volunteers, attendees or a defined subset. Share the link with that group.
Test the connection and sign
Scan the final print at the site, test the page on venue Wi-Fi and confirm the short link works as a fallback.
Agree on review and display
If submissions need approval or the team plans a slideshow, assign a person to review and test the screen before the event.
Record the archive deadline
Write down the package's closing date, who downloads the collection and where the organisation will keep the files.
Know when a photo collection is not enough
A shared collection does not replace an event photographer, media release process, press workflow or public asset library. It is a way to gather files from contributors through one event page. If the organiser needs editorial review, individual team permissions, high-volume professional delivery or automatic sorting, check those requirements against the product before setup. Candid's documented controls include gallery visibility, the guestbook, approval and package-specific downloads. Do not infer rights-management, team folders or permanent archive features from the word collection. A practical comparison should include the work the organiser still needs to do after files arrive.
For a small community festival, one named event and a clear contributor group may be enough. A large public event with hundreds of attendees may need a more formal policy, a staff review process and a plan for consent and publication. If the collection is for internal use, keep the link within the organisation and turn off guest browsing if that matches the plan. If photographs will be used publicly, explain the intended use and confirm that the organiser has permission. The technology should fit the team's actual responsibilities rather than encouraging an organiser to collect material they cannot review or store safely.
Let the photographs add context to the event record
A useful festival collection includes the details an organiser did not have time to notice: a volunteer solving a problem, a crowd gathering for a performance, the quiet preparation before opening and the parts of the site that were busy while the organiser was elsewhere. Give contributors enough direction to include those moments without demanding a polished campaign. The event team can review the set afterwards and decide what is useful. The strongest process is one people can follow quickly, one that respects attendees and one that ends with a saved archive the organisation can locate next season.
If you use a Candid event collection, start with the contributor list, the media allowance and the retention period. Then create the event, test the guest page and share one simple instruction. Keep the QR sign legible, use the short address as a fallback, and tell contributors if files may appear on a screen. After the festival, download and check the archive before the online period ends. That gives the organiser a workable record without claiming that every visitor will participate or that the platform manages the festival's media rights.
Festival photo collection questions
How can a festival organiser collect photos from volunteers?
Create one named event, send the link to the volunteer team and explain which moments would help the organisers. Choose an owner to review and download the files.
Can a festival use a QR code for photo uploads?
Yes. Candid creates a QR code and short address for an event. Contributors open the page in a browser, provide a name and choose files to send.
Can festival attendees upload without internet access?
No. Scanning the code can open the page, but an active internet connection is needed to send files. Contributors can use the link later when connected.
Can organisers review festival photos before they appear?
Candid has an approval control that holds submissions until the host accepts them. Assign someone to review files if approval is enabled.
Give your contributors one event address
Set a clear contributor group, test the link at the site and name the organiser who will save the files afterwards.
Photo collection by event type
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.