Three thousand runners, six hours and a bib number that disappears the moment someone wears a jacket. Race photo delivery is a volume problem with a matching problem hidden inside it.
Why race photography is its own problem
A marathon is the largest-volume event most photographers will ever shoot. Three thousand runners, six hours, multiple checkpoints, and a bib number that identifies each participant more reliably than their face at kilometre thirty.
The delivery challenge is brutal. Every runner wants photos of themselves, nobody wants the other 2,999, and the photos are spread across a course rather than a single room.
Bib numbers versus faces
The obvious solution is bib-number search — type your number, see your shots. It works, and it is what most race photography platforms do. But it has two failure modes worth knowing.
- Bibs get hidden. Jackets, hydration vests, arm swing and other runners obscure the number in a large share of frames.
- Bibs are not unique across a season. If you shoot multiple races, number collisions become a support problem.
Face recognition handles the cases bib search misses — and works on the finish-line photos where the number is often least visible. The strongest approach uses both, but if you can only have one, face search is more forgiving.
Why selfie search suits runners
A runner already has a selfie on their phone. Asking them to upload one takes ten seconds and requires no bib number, no registration on a results portal, no password.
They scan a QR from the race pack or the results email, upload a selfie, and see every photo they appear in — start line, mid-race, finish, medal. That is a far better experience than typing a number and hoping it was visible.
| Method | Works when bib is hidden | Needs an account | Handles multiple races |
|---|---|---|---|
| Bib search | No | Usually | Collision risk |
| Watermarked gallery + scroll | Manual | No | No |
| QR + selfie search | Yes | No | Yes |
Volume and cost
Race photography is storage-heavy in a way that surprises people. Three thousand runners across six hours can mean 10,000–30,000 frames before culling, and even a tight edit lands at 60–150 GB.
| Plan | Storage | Price | Typical coverage |
|---|---|---|---|
| Free | 1 GB | ₹0 | A small club run |
| Entry | 100 GB | ₹833.25/mo | A mid-size race |
| Mid | 500 GB | ₹1,166.58/mo | A full race season |
| Top | 1 TB | ₹1,666.58/mo | Multiple large races with archives |
Prices exclude 18% GST. Cold storage is bundled equal to your hot allowance.
Cold storage matters more here than in most verticals. Race organisers frequently come back months later for last year's event photos, and being able to keep them archived rather than deleted is the difference between a repeat booking and a lost one.
Frequently asked questions
How do runners find their race photos?
Is face recognition better than bib search?
Do runners need an app?
How many photos does a race produce?
Can I sell race photos to runners?
Do you read bib numbers?
Why was a selfie rejected?
Does it work for team sports?
See the price before you commit
Every Snaptide plan is published in rupees with face search, white-label and full-resolution downloads included. Start free and test the guest flow yourself.
See published pricing →Sources
Race and event photo delivery patterns — event photography platform guides · HEIC web compatibility — phototools.org · Snaptide guest flow and pricing — snaptide.ai/how-it-works.php, snaptide.ai/pricing.php · Accessed October 2026.
Deliver your next event the easy way
One QR code, guest selfie search, WhatsApp notification at ₹0.85 a message, cold storage included and 75% of download sales to you. Start free — paid plans include a 7-day trial.
Start free → See plans & pricing