This is the single most common upload frustration we see, and almost every time it is not a Capture Club problem, it is iCloud doing its thing in the background.
Why this happens
By default, iPhones have a setting called Optimize iPhone Storage turned on. What that actually means:
- The full-resolution original of every photo you take lives in iCloud
- Your phone keeps a small, lower-resolution "preview" copy on-device
- When you open a photo in the Photos app, it looks normal because you are seeing the preview
- When you export a photo (share, upload, save to Files), iOS has to fetch the full-resolution original from iCloud first
So when you are uploading 30 wedding photos to Capture Club from an iPhone, each photo triggers an iCloud round-trip before it can be sent to us. The actual Capture Club upload is fast, the iCloud fetch is what is slow.
On a weak venue WiFi, an iCloud fetch for a 4K live photo can take 30+ seconds per photo. Then our upload, which would normally take 2 seconds, sits waiting. Multiply that by 30 photos and you are at 15 minutes for what should have taken 60 seconds.
How to tell if this is the problem
Signs it is the iCloud fetch, not Capture Club:
- The upload pauses between photos ("uploading 4 of 30" stays stuck for 20+ seconds before advancing)
- It feels slower on cellular or weak WiFi, faster on strong WiFi
- A progress bar inside Apple's share sheet briefly spins before our upload starts
- The first few photos go fast (they are cached), then it slows down once you hit uncached ones
Fix 1, use a desktop or laptop (best)
The fastest path: export the photos from Photos on a Mac or iPad with iCloud Photos turned on, then upload from that device. Or AirDrop them to a Mac and upload from Finder.
On Mac:
- Open the Photos app on your Mac
- Select the photos (Cmd-click to multi-select)
- File โ Export โ Export Originals
- Save to a folder on your desktop
- In a browser, open your event's upload page and drag the folder in
On desktop, the Capture Club upload is significantly faster because there is no iCloud-fetch-then-upload two-step, the Mac already has the originals on disk, so it is just the upload.
The event dashboard on mobile actually shows a hint suggesting desktop for bulk uploads. That hint exists for this reason.
Fix 2, turn off Optimize Storage (if you have room)
If you have enough free space on your iPhone to store your full photo library at original quality:
- Settings โ [your name at the top] โ iCloud โ Photos
- Switch from Optimize iPhone Storage to Download and Keep Originals
- Wait, this can take hours or overnight. Your phone will download every photo's full-res version.
Once done, uploads from your phone are as fast as they should be because the originals are already local.
Not recommended if: your iPhone is close to full on storage, or you have years of 4K video in your library. You will run out of space.
Fix 3, upload in smaller batches on strong WiFi
If you are stuck on mobile and cannot move to a desktop:
- Pick 10 photos at a time, not 50
- Stand closer to the venue router, or connect to a hotspot from a separate phone
- Upload while plugged in (some iPhones throttle iCloud fetches on low battery)
- Close all other apps, iOS sometimes deprioritizes background iCloud activity
A reception is usually not the right place to upload a huge batch for this reason. Shoot during the event, upload the next morning from your desktop.
Fix 4, if it is your guest having this problem
If guests are complaining to you mid-reception about slow uploads, the usual triage:
- Have them try one or two photos first, those are likely already cached locally
- Suggest they upload from WiFi, not cellular, many venues have "guest WiFi" that is slow but still better than a one-bar cell signal in a stone basement
- Tell them to try again the next morning, by then they have been on home WiFi overnight and iCloud has pre-fetched recent photos
- Remind them the upload is not lost, even if it stalls, the guest can re-open the event URL the next day and pick up
This is also a good argument for leaving Review mode off during a live reception, you do not want the queue to fill with duplicates from guests who thought the first try failed.
What Capture Club can and cannot control
We cannot see or modify what is happening inside iOS. The iCloud fetch is entirely Apple's domain. What we do:
- Use direct-to-storage uploads (so the phone is uploading straight to our CDN, not through a bottleneck server)
- Chunk large files so a dropped connection resumes instead of restarting
- Parallelize up to 3 uploads at once so short photos get through while a long video is still uploading
- Show a clear progress UI so guests can tell it is working and not hung
If you see an upload actually hang, no progress movement for 60+ seconds, see My upload is stuck or failing for next steps.
Android equivalents
Androids do not have the same universal "optimize storage" feature, but similar problems happen with Google Photos' "Storage saver" mode and some manufacturer-specific photo apps. The fix pattern is the same: upload from a desktop, use strong WiFi, smaller batches.
One more: HEVC conversion
iPhones record video in HEVC by default. When you upload a HEVC video to Capture Club, iOS sometimes re-encodes it to H.264 on the fly during the share-sheet export. That re-encode can take 20-60 seconds per minute of source video. It is not an iCloud problem, it is a format-conversion problem, and it happens even if your originals are local.
Workaround: Settings โ Camera โ Formats โ switch to Most Compatible. New videos are recorded in H.264, no re-encode needed at upload time. Existing HEVC videos still need the conversion.