The single most common reason same-night photo delivery fails is not the technology. It is the conversation that did not happen between the event organiser and the photographer before the event.
Photographers are extraordinarily skilled at capturing images. They are not trained and have usually never been asked, to operate as part of a live delivery pipeline. The traditional workflow is: shoot, drive home, cull, edit over several days, deliver a Dropbox link. Asking them to contribute to same-night delivery means changing almost every part of that workflow. That change needs to be explicit, agreed in advance and built into the contract, not mentioned on the morning of the event.
This guide covers exactly what to discuss, what to specify and how to handle a photographer who is uncertain or resistant to the new workflow.
Why photographers are not trained for this
The traditional post-production model exists for good reasons. Photographers shoot in RAW format to capture maximum dynamic range. They cull down from hundreds of shots per session to a refined selection. They edit for exposure, colour balance and consistency, a process that takes expertise and time. Delivering 30 unedited RAW files from the first hour of an event is not something any professional photographer wants attached to their name.
Same-night delivery does not require abandoning quality. It requires a different relationship between the shoot and the edit. The brief is not "deliver everything unedited." It is "export a rapid JPEG version of clearly good shots as you go and handle the full edited gallery on your normal timeline."
Understanding this distinction and communicating it clearly, is what makes the photographer relationship work. You are not asking them to compromise their standards. You are asking them to add a parallel fast-track export step to their existing workflow.
File format requirements
AI photo matching platforms, including Eventiere, work with JPEGs, not RAW files. RAW files (CR2, NEF, ARW, etc.) are proprietary formats that vary by camera manufacturer and require dedicated software to render. Processing RAW files on a server is orders of magnitude slower and more resource-intensive than JPEG and the quality difference for face matching is negligible.
The specifications to give your photographer:
- Format: JPEG (.jpg)
- Quality: 85–95% (not maximum, full quality JPEGs are unnecessarily large for upload speed)
- Minimum resolution: 2 megapixels (1920×1080 is sufficient for face detection and gallery display, the AI does not need 24MP files)
- Recommended resolution: 4–6 megapixels for a good balance of quality, detail and upload speed
- Colour space: sRGB (not Adobe RGB or ProPhoto, these need conversion for web display anyway)
- No watermarks on uploads: Watermarks can be applied to the final edited gallery later; the upload version should be clean
Most professional cameras and editing software (Lightroom, Capture One) support a "quick export" or "export as JPEG" workflow that can be configured once and used repeatedly. Help your photographer set this up at the pre-event briefing call, not on the day.
Upload timing targets
For guests to find photos during the event, when they are still at the venue and the excitement is highest, the first upload batch should arrive before the two-hour mark from event start. This is a firm target, not an aspiration.
A practical upload rhythm that works well for most events:
- First batch within 90–120 minutes of event start: 50–100 photos from the arrival, reception and early session coverage. These are the photos where people are most likely to be standing still and identifiable.
- Rolling uploads every 30–45 minutes thereafter: The platform ingests new photos continuously. Guests who check early see an initial gallery; guests who check later see a fuller one.
- Final upload before end of event: A photographer who uploads while guests are still on-site means guests leave with their gallery already populated.
The venue WiFi problem: Upload speed at the event is limited by the venue's internet connection. Many hotels and conference centres have unreliable or bandwidth-throttled WiFi, particularly when hundreds of attendees are simultaneously connected. Discuss this before the event and plan the mitigation: either a dedicated venue data line (available at many venues on request), a 4G/5G mobile hotspot the photographer carries, or both. A mobile hotspot costs under £30/month and eliminates the venue dependency entirely.
Naming conventions and organisation
Naming conventions matter less when the AI is doing the matching, the platform does not rely on filenames to identify who is in a photo. But good naming conventions make your own post-event workflow cleaner and help with troubleshooting if any photos fail to upload or index correctly.
A simple convention that works: EVENTNAME_YYYYMMDD_001.jpg, incrementing sequentially. Some photographers prefer camera-generated sequential numbers with a prefix. Either is fine. What to avoid: spaces in filenames (causes issues with some upload tools) and dates in ambiguous formats like 22-03-25 which can be interpreted differently.
For multi-photographer events, prefix with a photographer identifier: SUMMIT25_P1_001.jpg and SUMMIT25_P2_001.jpg. This prevents filename collisions when two photographers are uploading concurrently to the same event album.
What to do if the photographer is resistant
Some photographers, particularly those who have built their reputation on highly polished final galleries, are uncomfortable with the idea of any unedited or lightly edited photos reaching guests. This concern is understandable and should be taken seriously rather than dismissed.
There are a few framings that tend to resolve the objection:
- Position the quick-export as "BTS" content: Many photographers already post lightly processed "behind the scenes" shots on their own social media on the night of an event. The same workflow, just directed to the event platform instead.
- Clarify that the final edited gallery is separate: The same-night delivery is not a replacement for the full edited gallery. Guests receive both, the quick gallery now, the polished edit later. This is additive to the photographer's value, not a substitute for it.
- Include it in the contract and fee: Photographers who hesitate often soften when the brief is formalised and the additional workflow is compensated appropriately. A same-night delivery brief adds real work. Budget for it.
If a photographer is unwilling to engage with any form of same-night workflow, that is useful information during the selection process, not a conversation to have on the morning of the event.
Sample photographer brief
Photographer brief template - same-night photo delivery
Event: [Event name], [Date], [Venue]
Platform: Eventiere (eventiere.com) - photos will be matched to guests via AI face matching
File format: JPEG, 85–95% quality, minimum 2MP, sRGB colour space, no watermarks on upload files
First upload: By [90 minutes after event start time] - target 50–100 photos from arrival and early programme coverage
Upload rhythm: Every 30–45 minutes thereafter, ideally with a final batch before guest departure
Upload method: [Browser upload via Eventiere dashboard / direct S3 upload link, to be confirmed], we will provide credentials before the event
Internet access: [Venue WiFi SSID and password / 4G hotspot provided, to be confirmed]
Naming convention: [EVENTNAME]_[YYYYMMDD]_[sequential number].jpg
Full edited gallery: Your standard delivery timeline applies, the same-night export is additional, not a replacement for the final edited set
Questions: Contact [organiser name] at [email] or [mobile] for any issues on the day
Ready to run your first same-night delivery?
Eventiere includes a photographer upload portal, real-time indexing dashboard and a pre-event brief template, everything your photographer needs to get started.
Book a free demo