Wedding 2 GB Gallery: Couple Failed to Download 3 Times — 2026 WeTransfer vs Drive vs Image Host 4-Platform Test
Wedding Photographer Drops a 2 GB Gallery in the Cloud — Couple LINEs 3 Times: "Won't Open"
Lazy version up front.
Don't use one cloud link. Split originals, retouched, and preview into three layers.
I made this mistake first.
Dumped the full 2 GB pack to WeTransfer, sent the link to the couple. Three hours later the chat lit up: "Sorry, this link won't open." Switched to Google Drive. Bride's mom is 60, saw a login wall, gave up. Switched to Dropbox. Download crashed halfway through. Switched to my own image host direct link. Couple downloaded fine, but parents couldn't see thumbnail previews.
Don't waste time. Honestly — one wedding needs three cloud pipelines, not one.
What the Three Tiers Look Like
Key points:
| Tier | Recipient | Size | Purpose |
|---|---|---|---|
| Originals | Couple | 2-5 GB | RAW + all JPGs, permanent backup |
| Retouched | Couple + social share | 200-500 MB | 80 finals, social media use |
| Preview | Both sides' parents / VIP guests | 30-80 MB | Thumbnails + watermark + password protection |
Each tier maps to its own cloud service.
Not one platform doing all three jobs.
Four-Platform Test: Who Handles Which Tier?
Ran the same wedding materials across four platforms. Main metric: can parents on their phones actually open it?
| Platform | Originals tier | Retouched tier | Preview tier | Senior-friendly |
|---|---|---|---|---|
| WeTransfer | OK (7 days) | OK | Not suited | Medium (no login) |
| Google Drive | OK (permanent) | OK | OK but requires login | Low (Google account needed) |
| Dropbox | OK | OK | Same as Drive | Low (login required) |
| Dedicated image host (lpic.cc) | Not suited (file too big) | OK | OK (password protected) | High (direct open) |
Here's the kicker.
WeTransfer permanent version needs Pro subscription ($12/mo). Free tier dies after 7 days. Six months after the wedding when the couple wants originals back? Link already dead.
Google Drive and Dropbox are best for "couple's safekeeping" — permanent storage, ample capacity. But the login requirement kills it for older relatives.
Dedicated image hosts can't handle originals (8 MB single-file cap), but they crush the preview tier — direct open, no registration, password-able.
So.
Different tiers go to different services. Don't cut corners.
The Real Wedding-Day Download Map
I made this mistake first.
Tried to cram everything into one platform. Result: the couple LINE'd me three times complaining "link won't open." Bride's mother asked why she had to install an app to see her own daughter's wedding photos. A colleague asked to peek at the shots, hit the login wall, gave up.
Then I figured it out.
Different recipients, different pipelines.
Couple wants "I can access originals anytime" → give them Google Drive. Parents want "tap to view" → give them image host direct link. Social audience wants "80 finals" → give them a password-protected gallery link, couple decides who gets the password.
Three pipelines, each doing one job. Zero collisions.
Three-Tier SOP
No nonsense.
Tier 1: Originals to the Couple via Google Drive
- Create folder named
[Couple Names]_Wedding_Originals_YYYYMMDD - Upload RAW + all JPGs, sub-foldered (Ceremony / Reception / Speeches / Group Shots)
- Set "Anyone with link can view," ask couple to copy to their own Drive
Once couple has their own copy, your Drive quota isn't locked up.
Tier 2: 80 Retouched Shots to Image Host
- Pick 80 hero shots from originals, export at 1080×1080 + 1080×1920
- Batch upload to dedicated image host (lpic.cc batch upload or equivalent)
- Get permanent hot links, compile a "Retouched Index" PDF with URL + caption per image
- PDF to couple, they post wherever (Instagram / Threads / TikTok)
Critical: permanent URLs. Six months later when couple wants to reshare, the link still works.
Tier 3: Thumbnails + Watermark for Parents
- Batch resize 80 retouched shots to 720×720
- Apply watermark:
[Photographer Name] _ Preview Only _ No Distribution - Upload to password-protected gallery
- Link and password in two separate LINE messages to couple
Parents tap their phone, see a 16-thumbnail grid immediately, no login.
That's it.
lpic.cc's Position in Wedding Workflows
Honestly, lpic.cc can't handle the originals tier — 8 MB single-file cap is too small for RAW.
But Tier 2 + Tier 3? Solid.
Direct URL requires no login, parents tap and see. Password-protected gallery for "limited preview" delivery. 30-day idle auto-recycle — preview content cleans itself up, no permanent quota burn.
Limits up front: free tier 8 MB single-file cap (4K JPEG retouched fits, RAW doesn't). Originals + RAW backup still needs Google Drive or Dropbox.
Don't put all your eggs in one basket.
FAQ
Q1: WeTransfer free dies after 7 days. Any free way to extend?
No. WeTransfer Pro is the only path to permanent links. Cheapest alternative: just give the couple a Google Drive link — permanent, free, couple saves their own copy and decouples from you. Your quota frees up too.
Q2: Couple doesn't want to pay for Google One. 100 GB of originals — what now?
Two paths. One: hand-deliver external drive (common in the wedding industry, 1 TB SSDs run around $80 these days). Two: use lpic.cc / Dropbox / OneDrive for retouched + preview, burn originals to SSD for in-person handoff.
Q3: Will password-protected image host links get indexed by search engines?
No. lpic.cc password-protected links are noindex. Only people with link + password can see. But the link leaking puts the password as the last line of defense. Send link + password in two separate LINE messages, not in the same email.
Q4: Fastest way to batch-watermark?
ImageMagick one-liner: magick mogrify -gravity southeast -draw "fill rgba(255,255,255,0.5) text 30,30 'Photographer Name'" *.jpg. Or Photoshop action with batch processing. 80 photos in under 30 seconds on my machine.
Q5: Five years after the wedding, couple asks for originals again. Is the photographer obligated?
Legally — no, depends on your contract. Industry practice retains originals 1-3 years. Write retention duration into the contract, and tell the couple at handoff to immediately back originals up to their own Drive. Don't be the long-term archivist.
Q6: What about US destination weddings — different cloud rules?
Mostly the same workflow, but check GDPR if the couple or any guest is EU-resident. Image hosting that strips EXIF (like Imgur) actually helps GDPR compliance by removing geo-coordinates. For US couples, CCPA gives them right-to-delete after delivery — set a clear retention policy in writing.