Gather the views along the route
Race day photo sharing for runners, families and volunteers
Race photographs come from many places: the start, the route, the finish and the people waiting along the way. Give participants and supporters one event link to contribute selected photos, with a clear plan for consent, downloads and access.
Conferences, corporate days, schools, churches, sport and community.

A race day can produce photographs from far more than the official finish line. Participants take pictures before the start, relatives wait at a turn, volunteers work at a water station and friends meet after the last runner crosses. When those images stay on separate phones, the club or organiser may see only a small part of the day. A shared collection offers a place for willing participants to contribute selected photographs and short clips. The organiser can then download the event archive and decide what to share with the group. It is a simple idea, but a successful race-day collection still needs clear ownership, sensible privacy expectations and a plan for guests who cannot upload while the event is happening.
Decide whose photographs belong in the collection
A race can include registered participants, spectators, volunteers, families and people who happen to be in a public space. Decide who the collection is for before making a link. A club might want photographs from its members and the supporters they invite. A community organiser may want a private archive for the organising team. These are different audiences and should not be collapsed into a single public call for images. Write down who will receive the link, who can view contributions and who will decide whether selected photographs can be used in a newsletter or social post.
A guest contribution does not automatically grant permission to publish every person shown in the photograph. Be especially careful with children, identifiable people who did not choose to take part and images that show a participant in a vulnerable moment. Tell contributors how the organiser intends to use the collection and ask before moving images to a wider audience. If a person asks for a photograph to be removed, name the organiser who will handle the request. This is not a substitute for the event's own consent and photography policy; make sure the collection follows the organiser's rules and local requirements.
Give the event one clear owner
The person who starts a photo collection should be able to manage it after the finish banner comes down. Name one organiser to create the event, share its guest route, download the files and store the archive. If a club or committee is involved, agree which person controls the account and where the backup will be kept. Do not rely on a volunteer who is only available on race morning unless someone else has accepted the follow-up work. A clearly named owner prevents the collection from being forgotten in a private account after the event.
Candid creates one event collection with a browser guest page, a short address and a matching QR code. Guests do not need an app, account or password: they open the link, provide a name and select the files they want to send. The event can be named by the organiser, so a club or race can use an appropriate title without being a preset event category. Send the link in the race information or volunteer message, and display the QR code at a place where people can stop safely. Do not ask someone to scan and upload while running, cycling or crossing a course.
Choose the moments to invite people to capture
A broad request to photograph everything can overwhelm the organiser and distract participants. Offer a few useful prompts instead: the start area before the event, a club group portrait, the volunteer team, a supporter greeting, a finish celebration or the gathering afterward. Participants can contribute their own chosen images without trying to photograph every person on the route. Volunteers should not be asked to stop doing safety work in order to take pictures. If a dedicated photographer has been hired, let that person know how the guest collection will work and where guests should stand.
A prompt should not reveal private information or encourage unsafe behaviour. Do not publish a runner's bib number alongside sensitive details, ask spectators to step into the course or instruct people to photograph a medical incident. The organisers should say whether photographs of participants may appear in the shared gallery and what to do if a participant does not want to be included. A collection is optional; no runner owes the organiser a photo, and no volunteer should feel that picture-taking is part of their safety role.
Place the link where people can use it safely
A QR code belongs at a stationary point: a welcome table, club tent, finish-area notice board or post-race gathering space. Make sure the sign does not obstruct walkways, queueing or event notices. Include a short written address as an alternative for someone whose phone cannot scan a code. If the event has multiple start waves, send the link in the relevant group message rather than expecting everybody to find the same sign. Ask a volunteer to keep the sign in place and bring it back after the event, especially if it contains the organiser's event address.
Before printing, scan the final code from a phone that is not logged in as the organiser. Upload one sample image and check that the event title and guest instructions are clear. If the event is outdoors, test mobile coverage near the finish and at the gathering point. A code can open a web page only when the device can reach the internet. If the network is congested or unavailable, tell people they can save the link and upload later rather than retrying during the event or assuming their pictures have arrived.
Plan for race-day connectivity
A crowded finish area may place unusual demand on a venue's mobile network. The organiser can ask the venue or race team whether guest Wi-Fi exists, but should not promise reliable service until someone tests it. Mobile data, device settings and network load differ between people. One short photograph might upload where a large video stalls. Encourage supporters to keep their selected files and use the link after the event if the first attempt does not finish. Avoid setting up a live display that depends on instant uploads unless the connection and playback have been tried in the actual location.
Participants who travel to the event may have limited data or be conserving battery for navigation and emergency calls. Keep the request brief and make later submission acceptable. A volunteer can share the event link with a club group after the race, when people are back on a stable connection. A reminder should include the deadline and explain who will receive the archive. Do not make the QR sign the only route: a short address is useful for people who receive the message later or whose camera does not scan the printed code.
Separate event photographs from official race records
A guest photo collection is not timing, registration, results or safety infrastructure. Keep the event's official information on its established channels and do not put critical instructions behind the photo link. If a photograph shows an incident or a participant who needs help, notify event staff through the proper route rather than relying on an album submission. The collection serves the memory-sharing purpose; it should never distract from course management, first aid, stewarding or the organiser's official record keeping.
Use a separate upload invitation for the volunteer team if its photographs include operational details or people who should not be in the general event gallery. Tell contributors not to send medical information, documents or unrelated files. If a host turns on approval, submissions wait until accepted before they appear in the gallery. Assign an organiser who can review the queue, but do not describe that control as a replacement for a clear photography policy or moderation decision. The organiser remains responsible for what is shared beyond the collection.
Estimate the photo and video allowance
Think about the number of likely contributors and the kinds of files they will send. A small club race with a few dozen volunteers has different needs from a community event with several groups and spectators. Candid Preview is free and includes 20 photos, 10 contributing guests, 500 MB and seven days online. Gather is $19 once per event for 200 photos, 30 videos, 5 GB, unlimited contributors and one month online. Celebrate costs $39 with 750 photos, 100 videos, 20 GB and three months online. Keepsake costs $69 with 2,000 photos, 300 videos, 50 GB and six months online. Confirm current plan details and prices before selecting a package.
Photos and video use different portions of an event allowance, and video files can take longer to upload on a busy network. Decide whether you need video at all or whether a small set of still images will meet the purpose. Extra photo or video capacity is available as one-off add-ons. If the organiser only needs to collect images briefly and can download them promptly, a shorter online period may be sufficient. If participants will contribute over several days, choose a period that covers the follow-up and set a date for the archive owner to download the files.
Set the collection's audience and moderation
A race collection can include participants who are comfortable sharing images with the club but not with the general public. Keep the link among the intended group and state who will receive the photographs. The host can switch off the guest-facing gallery when contributions should be upload-only, and can enable approval so new submissions wait for review. If the host expects to show photographs on a screen at the finish gathering, decide who will review them and how to keep unsuitable or unintended images from being displayed. The screen should be optional and should not show private photographs just because someone uploaded them.
If children or family groups are present, check the event's policy and follow parent or guardian preferences. Ask participants before reusing identifiable images in a public report. Keep captions factual and avoid attaching health, contact or location information that could put someone at risk. A closed event audience is still an audience, so the organiser should set clear expectations before sharing the guest link. When the event is over, remove access or stop sharing the link if the collection no longer needs new contributors.
Download and keep the event archive
Choose an archive owner and backup destination before race day. Candid allows the host to download individual files or the collection as one streamed archive. Gather has standard downloads; Celebrate and Keepsake have original-quality downloads. Preview does not include downloads. Check which plan matches the organiser's intended use and whether a high-quality master copy matters. After downloading, open a sample from the beginning, middle and end of the archive. If the files are meant for a club record, keep the original archive separate from any resized or selected images prepared for a newsletter.
Every plan states how long the collection remains online from the event date, and the host receives a warning before deletion. Once the collection is removed, the host's download is the only copy. Set a reminder well before the close date, make the archive and a second backup, and tell the group how to ask for selected pictures. Do not assume an online gallery is permanent storage or that the original contributor will keep a file available. A simple archive plan is part of running the collection, not a task to leave for the next season's committee.
A practical race-day collection checklist
Prepare the photo route
Name one owner
Choose the organiser who will set up the collection, handle questions and download the finished archive.
Write the invitation
Say who may contribute, what kind of photographs are useful and who will receive the collection.
Test from a guest phone
Scan the QR code or open the link, send a sample file and confirm the organiser can retrieve it.
Place signs safely
Put the code at stationary locations away from the course, queues and safety notices.
Set the backup reminder
Download, open and store a second copy before the event's online period ends.
Keep the collection useful after the finish
A good race-day gallery is not measured by the number of files it contains. It is useful when participants can add a few welcome perspectives, the organiser can find them later and people understand the audience. A short request, a tested link and one responsible host are more valuable than signs at every turn or a promise of instant sharing that the network may not support. Let runners and volunteers focus on the event. Make later uploads possible and thank contributors without making the collection a condition of taking part.
Candid Photos gives a club or organiser an event page, QR code and a place to gather guest photographs and supported video. Choose a plan for the expected files and contributors, explain privacy and download the archive before the collection closes. If your event is managed by a race organisation, keep photo sharing separate from official registration, results and safety communication. Run one sample upload before the day, assign a backup owner and the collection can stay a small, useful part of the event rather than a new job for every participant.
Race day photo sharing questions
Can a running club collect race photos with a QR code?
Yes. The organiser can create a named event collection and share its guest link or QR code at a safe, stationary point.
Can runners upload during the race?
They should not use a phone while running or crossing a course. Participants can contribute before, after or later from a safe place with an internet connection.
Can a race organiser create an event in Candid?
Yes. The organiser can name the event and use the guest page for the occasion; race registration, timing and results remain separate systems.
How long will race photos stay online?
The selected Candid plan sets the online period from the event date. The host should download and back up the archive before it ends.
Set up one safe route for race photographs
Create a named collection, test it from a guest phone and choose the organiser who will keep the archive.
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.