For multi-day weddings
One wedding, three events, one camera QR.
Weekend weddings leak photos across Friday welcome drinks, Saturday, and Sunday brunch. Relatives will ask which album to join. You want one pipeline.
A multi-day wedding is a small festival with better clothes. Attendance splits: some people fly in for Saturday only, some stay through brunch, some skip the welcome party because of kids. If you spawn three photo tools, Monday is a merge. If you spawn three RSVP forms, you will never know who is at brunch.
WedPOV is one wedding object: one public site, one RSVP list, one camera slug, one gallery. That is a product opinion. You can ignore it and create multiple weddings in the dashboard if you truly want isolated rolls — for example a private family dinner you do not want in the same gallery as the public reception. Most couples should not do that. Most couples should write the weekend on one page and reuse /e/{slug} from Friday through Sunday.
Shot caps are per guest on that wedding, not per calendar day. A heavy shooter can empty a Free 5-shot trial on Friday nachos. Tell people, in one sentence on the site, to save frames for Saturday, or pick Pro (25) or Platinum (50) so the weekend has budget. We will not auto-reset limits at midnight. That would be a different product.
What we will not do: hotel blocks, shuttle loops, vendor call sheets, or a timeline OS. Put the schedule in your page copy. Link a PDF if the weekend is genuinely complex. The camera does not need to know about the 10 a.m. brunch to work at 10 a.m.
Not every guest attends every event. You still want one gallery so Monday morning is not a merge of three tools.
What usually breaks
These are the failure modes for this kind of night — not generic SaaS bullets.
Split attendance
Use RSVP copy to ask who is coming to which parts if you need those numbers. The form is not a full event-ticketing system. Extra questions belong in your page text or a linked doc.
QR fatigue
A new code per brunch will be ignored. Same printable at the welcome-party bar, ceremony program, and buffet.
Shot budget across days
Caps do not reset daily. Brief the room once. Upgrade the plan if the weekend is the point of the camera, not a side toy.
Friday photos leaking into Saturday
Host-controlled reveal lets you wait until Sunday night so street-clothes candids are not public during formal portraits.
How WedPOV maps to this
01
Write the weekend as one story
Dates and locations on the site. One slug. Guests bookmark one link.
02
Print once, place many
Same file from /printables in three physical places. Redundancy is how tired guests find it.
03
Choose the cap for Saturday, not Friday
If Friday is optional, do not let it consume the roll. Say so in copy. Pick 25 or 50 shots if you cannot police that socially.
04
Reveal after the last event
Then send one gallery link. That is the thank-you.
What to actually write on the website
Copy only you can write. The product gives you fields; these are the sentences this wedding usually needs.
Friday
Where, when, how dressed, whether kids. State if the camera will be live (usually yes).
Saturday
Ceremony and reception facts. Remind people the QR is the same as last night.
Sunday
Brunch end time. Leftover shots are for this. Then the gallery closes the weekend.
Who is invited to what
A table in text: event / who. Prevents the uncle at the wrong brunch.
Checklist
- Resist creating three WedPOV weddings unless galleries must stay isolated.
- Put the same QR in the welcome bag and on the Saturday tables.
- Tell heavy photographers (the friend with a real camera) that this QR is the guest roll, not their job.
- Do not reset expectations that shots refill each morning — they do not.
- Keep shuttle and hotel info in copy or a linked sheet.
- Decide reveal for after brunch, not after Friday.
- Pack extra prints. Weekends eat paper.
- Confirm Pro/Platinum hosting length if people will share the gallery for a year.
When to do what
When the weekend is locked
Publish the site with all three days visible. Collect RSVPs with enough lead for catering on the biggest day.
Welcome-party morning
Place the first QR. Test upload on venue Wi-Fi.
Saturday
Same URL. Do not reprint a ‘new’ code that is actually a second wedding.
Sunday night
Reveal /g/{slug}. One link in the family chat.
On the day
Friday
Soft launch. Street clothes. Looser frames. Brief people not to dump the whole cap.
Saturday
This is where the cap matters. Disposable-style limits are the reminder.
Sunday
Brunch frames, then reveal. Do not start a second tool because you are tired.
Monday
You already have one URL. That is the win.
Compared with the usual workarounds
Not a feature matrix against every competitor — those live on /compare. This is what this wedding usually tries first.
A new shared album per event
Guests will join the wrong one. You will merge forever. One gallery is the point.
Only Saturday coverage from a photographer
Keep it. Guest camera is how Friday and Sunday exist in the same place.
Event-only camera apps with no wedding site
You will still need RSVP and a page. See /vs/pov-camera.
WedPOV does not run vendor timelines, shuttle lists, or hotel blocks. Link out from your page if those live in a planner spreadsheet.
Product pages for this setup
Related setups
For destination weddings
RSVP, travel details, and a QR guest camera for destination weddings. Guests reply from home, then shoot on the day without an app.
For micro weddings
Small guest lists still need RSVP and photos. WedPOV’s free camera fits 10 guests; Pro and Platinum scale shots, not software complexity.
FAQ
Should I create a new camera per event?
Usually no. One wedding, one camera slug, one gallery. Split only if you truly want isolated rolls.
Do shot limits reset each day?
No. Limits are per guest on that wedding’s camera, not per calendar day.
How long does the gallery stay up after a long weekend?
Hosting is months after the wedding date: 12 on Pro, 24 on Platinum. Free live camera is a limited trial, not long unpaid hosting.
Can RSVP track Friday vs Saturday vs Sunday?
Use your page copy and form fields you actually have. We are not a multi-session ticketing platform. If you need per-event tickets, use a tool built for that and keep WedPOV for photos — or keep it simple and collect one RSVP plus notes.
What if some guests only come Sunday?
They still use the same camera URL. They simply have unused shot budget. That is fine.
Should the camera stay unpublished until Saturday?
You can wait to share the QR. The product still has one camera for the wedding. Hiding the print until Saturday is a placement choice.
Treat the weekend as one wedding.
One site, one RSVP list, one QR from Friday to Sunday.