For elopements with guests
You eloped. A few people still came. They still have phones.
Language is messy: some couples call it an elopement even with a dinner. What you need is low ceremony in the software. No guest accounts. No ‘download our app to celebrate’.
If there are zero guests, close this tab. You do not need a guest camera. This page is for the elopement that still has a table: eight friends, parents, a witness, a dinner you did not want to call a reception.
Bridal-industry software is loud. It assumes registries, parties, and a year of email. You skipped that stack on purpose. The right weight is a page that can stay in draft until the list is final, a form so the restaurant is not guessing, and a QR that does not ask anyone to join a social network to prove they love you.
Close friends over-shoot. They will take 80 frames of the same toast because they are happy. A shot cap is a kindness, not a limitation for its own sake. Free (5 shots, 10 camera guests) can be the whole product if the table is that small. Pro ($49) is the honest unlock if you want in-product RSVP and 25 shots. Platinum ($79) if you want 50 shots, two years of gallery hosting, and a partner on the dashboard.
Privacy is a draft toggle, not a manifesto. Unpublished means guests cannot open the site, camera, or gallery. When you publish, the URLs work. We do not invent a private social graph beyond that. Share /g/{slug} with the people who were there.
The guest list is intimate. The photographer may be a friend. You want the night documented without turning it into a content set.
What usually breaks
These are the failure modes for this kind of night — not generic SaaS bullets.
Tools look too bridal-industry
You do not need 18 features. You need a link and a camera. Compare pages exist so you can leave if you wanted seating and audio guestbooks.
People will over-shoot
Caps exist so the gallery is a point of view, not a dump of the same candle.
The word ‘elopement’ confuses relatives
Your page copy can say ‘a small dinner after we sign the papers.’ The product does not care what you called it.
Someone will still ask for a Facebook album
Send the gallery URL. Do not become the person who downloads everyone’s camera roll.
How WedPOV maps to this
01
Stay in draft until the list is final
Hosts publish when ready. That is a product rule. Use it if you are still deciding who sits at the table.
02
Skip features we do not have
No seating chart, no audio guestbook, no live slideshow. If you wanted those, the compare pages say so. Do not wait for us to become a different company.
03
One QR in a pocket
For eight people, a card you pass around beats a forest of signage.
04
Open the gallery later
Intimate nights often look better after sleep. Host reveal is for that.
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.
What this is
Two sentences. Legal bit if you want. Dinner details. No fake ‘join our wedding community’ language.
Who is invited
Name the rule. Micros and elopements fail when plus-ones are implied. The form collects what you allow.
Phones
If you want vows unfilmed, say so. The camera QR can wait until dinner.
After
Tell people the gallery will arrive as a link. They should not expect a live slideshow we do not sell.
Checklist
- Confirm there are actually guests. Zero-guest elopements do not need this.
- Keep the page in draft until the list is real.
- Do not download-app-pitch anyone. We do not have a guest app.
- Ask the friend-photographer whether guest phones are welcome during portraits.
- Print one card. Put it in a wallet, not a centerpiece.
- Pick a shot cap that matches how chaotic your friends are.
- Reveal when you want, not because a product wants ‘engagement’.
- If you outgrow this and throw a later party, create another wedding or reuse — your choice.
When to do what
When you know the table
Create the wedding. Stay draft. Write copy that sounds like you, not a ballroom template.
A week out
Publish so RSVPs can land. Restaurant headcount is not a group vibe.
The evening
Pass the QR after vows if you wanted the ceremony private.
Later
Reveal the gallery to that table only.
On the day
Pocket QR
Pass it. Do not build a signage plan for eight people.
Portraits
Guest camera is not a replacement for work you paid a photographer for.
The toast
This is where caps save you from 80 identical frames.
Walking out
If there are frames left, they are for the street. Then stop.
Compared with the usual workarounds
Not a feature matrix against every competitor — those live on /compare. This is what this wedding usually tries first.
No documentation except the friend with a camera
Valid. Add guest camera only if you want POV you will not direct.
A full wedding website builder
Usually too much chrome. A single WedPOV page is the smaller object.
Instagram close-friends dump
Not everyone is on it. It is not a gallery you control. It expires socially even when the posts do not.
If there are zero guests, you do not need WedPOV. This page is for the elopement that still has a table.
Product pages for this setup
Related setups
FAQ
Is this for a legal elopement with no guests?
No. This page is for a small gathering that still needs a link and photos.
Will guests be asked to install anything?
No. Mobile web camera and RSVP. Hosts authenticate; guests do not.
Can I keep the gallery private?
You control when it is revealed. Share /g/{slug} with the people who were there. We do not add a private social network on top.
Can I hide the wedding from search engines?
Treat the URL as a secret: do not post it publicly. Draft blocks access until you publish. We do not promise unlisted magic beyond normal URL secrecy.
Do I need RSVP for eight people?
If a restaurant or catering minimum cares, yes. If it is truly drop-in, you may only need the camera. Do not pay Pro only because a landing page looked official.
What if we have a larger party later?
Create another wedding in the dashboard or reuse this one if it is truly the same event. Isolated later parties are usually a second wedding object.
Keep the software as small as the guest list.
Publish when you are ready. Hand them a QR. Open the gallery when it feels right.